Skip to content

chore(deps): build on cli-core 0.664.0 - #892

Open
leemour wants to merge 1 commit into
mainfrom
chore/cli-core-0.664.0
Open

leemour wants to merge 1 commit into
mainfrom
chore/cli-core-0.664.0

Conversation

@leemour

@leemour leemour commented Nov 14, 2026

Copy link
Copy Markdown
Member

What

  • @wirecat/cli-core 0.664.0 (was 0.662.0) and @wirecat/cli-base 0.101.0 (core's peer floor).
  • tg has no chats delete/chats clear, so the MCP chat-deletion change does not reach it; store clear --allow-dangerous stays the owner's (0.663.0).
  • Also from 0.663.0–0.664.0: list default defaults.limit (20), one time grammar, models chats show|set, own --yes on conversations embed/links rebuild.
  • search messages --discover regression in cli-core (messages-discovery.ts:140 passes the whole query, filters too, to joinedHyphens, so date:2026-10-08 adds the missing term 20261008): the adoption test keeps its other checks, and an it.fails case holds the full-coverage expectation until core is fixed. Test matrix: 3 new shared options listed as covered by cli-core.
  • Regenerated docs/contracts; changes/chore-cli-core-0.664.0.md.

Testing

Locally: typecheck, lint, the full suite, test matrix check, docs:check.

🤖 Generated with Claude Code

cli-core 0.664.0 offers no MCP tool for chats delete or chats clear: over
MCP an ask level went ahead without a question, so an agent could delete a
chat silently. It also carries 0.663.0's review follow-ups (one time
grammar, configured list limits, store clear --allow-dangerous kept to the
owner) and the models chats setting.

The new shared options join the test matrix's untested list, covered by
cli-core's tests. search messages --discover now counts a hyphenated filter
value (date:2026-10-08) as a missing question word, a cli-core regression
(messages-discovery.ts:140); the adoption test keeps every other check and
an it.fails case holds the expected coverage until core is fixed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant