[dependabot]

Bumps WireCatLabs/cli-base/.github/workflows/node-ci.yml from 0.77.0 to 0.93.0.

Changelog

Sourced from WireCatLabs/cli-base/.github/workflows/node-ci.yml's changelog.

Changelog

Notable changes to @wirecat/cli-base (published as @wirecat/cli-core up to 0.20.0), one section per version, newest first. Versions follow semantic versioning; before 1.0.0 a minor release may change the API. Versions before 0.8.0 are in the git tags.

Every entry says what changed as a caller sees it, why, and what to watch for — the rules are docs/dev/CONVENTIONS.md.

0.96.0 — 11.11.2026

Changed — may break callers

• --from takes a person, --from <person>, and is in the flag vocabulary as a target: the one identities leave (people unlink --from, contacts unlink --from) or the one who sent it (bot search messages --from). The unlink commands now require it, and without an entry they failed option-role. To watch for: a command that declares --from with another placeholder, such as --from <who>, now fails flag-two-meanings; rename it to <person>. A baseline entry for --from under option-role turns stale and fails the lint until it is removed.

• A test that still has the owner's real home, or reaches the real keyring, now fails even when the shared test setup did not load. Under vitest (VITEST in the env passed, or in the process when that env names no home), resolvePaths and the skill commands (~/.claude/skills, ~/.agents/skills, Hermes, HERMES_HOME included) throw while HOME or USERPROFILE is the account's own, read from the user database and compared through symlinks; and systemKeyring throws under vitest whenever the shared setup's throwing stand-in is not loaded, whatever HOME says. A probe run as vitest run --root <folder outside the repository> reads no vitest.config.ts, so the sandbox never loaded, and it wrote test accounts and runs into the owner's real data. Inside the sandbox nothing changes. To watch for: a test that builds an env with VITEST and the owner's real HOME now throws, whatever its XDG folders or <PREFIX>_*_DIR overrides say; an env without VITEST, such as { HOME: userInfo().homedir } built to find the owner's folders on purpose, is left alone.

0.95.0 — 09.11.2026

Fixed

• node-ci.yml: re-running a failed test shard can turn coverage green. gh run rerun --failed kept the failed attempt's shard report under the same artifact name, and coverage merged whichever copy it downloaded last, so a flaky test that passed on the re-run still failed coverage on every re-run (cli-core release #2799). The shard and argv artifacts now carry the run attempt, and coverage takes each shard's latest attempt. A caller picks it up by moving its node-ci.yml pin.

0.94.0 — 09.11.2026

Added

• meta.ranking: what a hosted model did to the order of a search's hits. An optional, typed block of the answer envelope's meta: { applied, reason_id?, provider, model, endpoint, sent, cost_usd, usage?, ms }, so a program reads whether memo's search all --harder reordered, why not (harder.timeout…), with which model and at what cost, instead of an English sentence under missing. meta stays strict: any other key is still refused. See WC-OUT-7.

... (truncated)

Commits

• 09918a5 feat(standards): --with-muted, a mode switch to also read muted chats (#554)
• f0aaa51 chore(release): 0.92.0 (#553)
• b7dbc92 feat(ci): node-ci fails on a committed merge conflict marker (#547)
• 00e639c chore(release): 0.91.0 (#552)
• 2e8b14a fix(standards)!: a charge's repeat is --period <count-unit>; --every is <dura...
• 5093d87 chore(release): 0.90.1 (#550)
• f1ca108 fix(audit): same-flag-meaning accepts every kind the vocabulary gives a flag ...
• 3e859ec chore(release): 0.90.0 (#548)
• b223bbe feat(standards): session list needs no query, identity URLs stay inline (#546)
• 965487f chore(release): 0.89.0 (#545)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)