Skip to content

feat(mcp): surface novelty gate in knowledge_create + force bypass (v2.25.0)#223

Merged
mkreyman merged 1 commit into
masterfrom
mcp-novelty-gate-surface
Jun 30, 2026
Merged

feat(mcp): surface novelty gate in knowledge_create + force bypass (v2.25.0)#223
mkreyman merged 1 commit into
masterfrom
mcp-novelty-gate-surface

Conversation

@mkreyman

Copy link
Copy Markdown
Owner

The novelty-gated write-back (#222) is enforced server-side, so MCP clients already get gated behavior. This release makes the agent aware of it:

  • knowledge_create description now explains the gate.verdict outcomes:
    • duplicate → nothing created (HTTP 200, deduplicated: true); read/update data.id
    • gated_to_draft → created as a draft with near-neighbors in metadata.proposal_novelty
    • created → novel, normal path
  • adds a force: true param to bypass the gate.

+2 tests for the force passthrough (50 MCP tests pass). Bumps to 2.25.0mcp-autopublish publishes on the package.json version change.

…s (v2.25.0)

The novelty-gated write-back (#222) is enforced server-side, so MCP clients already
get gated behavior. This makes the agent AWARE of it: knowledge_create's description
now explains the gate.verdict outcomes (duplicate → nothing created, read data.id;
gated_to_draft → created as draft with metadata.proposal_novelty; created → novel),
and adds a force:true param to bypass the gate. +2 tests for the force passthrough.

Bumps to 2.25.0 (mcp-autopublish publishes on package.json version change).
@mkreyman mkreyman merged commit 27edc93 into master Jun 30, 2026
9 checks passed
@mkreyman mkreyman deleted the mcp-novelty-gate-surface branch June 30, 2026 21:35
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