release: v4.5.0 — elicitation confirm, dispute-aware ask, MCP ambient recall - #128
Merged
Conversation
… recall Bump 4.4.6 → 4.5.0 across the 12 release manifests + CHANGELOG. Minor bump: elicitation confirm (MEMO_ELICIT_CONFIRM) and dispute-aware ask (MEMO_ASK_DISPUTES) are new user-visible features.
Minor bump requires what patch bumps didn't: uv lock refresh, rebuilt deterministic .mcpb archives, and SECURITY.md supported-line update (4.4.x → 4.5.x).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Minor release 4.4.6 → 4.5.0.
Highlights
MEMO_ELICIT_CONFIRM), fail-open on non-capable clients, fail-closed mid-elicit; decline-as-signal persisted as feedback memory (feat(mcp): elicitation confirm on irreversible tools (MEMO_ELICIT_CONFIRM) #127)MEMO_ASK_DISPUTES): disputed evidence marked in context/sources, deterministic abstention when answer rests only on disputed memories (feat: dispute-aware ask (MEMO_ASK_DISPUTES) — contradiction-blindness closed #122)briefing/recall <topic>prompts + memory-first server instructions (refactor: shared unified-briefing composer + dispute-ask MLX integration test #123/docs: close MCP gap #4 (resource subscriptions) as investigated/not-planned #124)Bump touches the 12 release manifests + CHANGELOG. Commit/tag/push manual per release flow.
🤖 Generated with Claude Code