Workflows discoverability: one mechanism - the workflows cross-link - #10
Merged
Conversation
Live agent testing showed discoverability spread across prose and structure still fails catalogue-first consumers - and multiple overlapping hints read as a protocol weakness under standards review. 0.9.5 names ONE mechanism and withdraws the rest: - The `workflows` array now rides BOTH surfaces that describe an operation: its catalogue entry (as in 0.9.4) and its schema document as a top-level member (JSON Schema tolerates unknown keywords; BEST names this one). Both must carry the same ids. - Consumers SHOULD fetch the referenced recipe before composing a multi-step sequence themselves. - Prose loses its specced role: the 0.9.4 suggestion that schema-document descriptions additionally name the recipe is withdrawn. One field to emit, one field to audit. Updated: SPEC.md (Workflows, Commands/Queries schema-document sections), workflows.md Discoverability rewrite, queries.json querySchemaDocument +workflows, catalogue-entry field descriptions, composing-processes guide, MIGRATION 0.9.4->0.9.5, v0.9.5 release notes. Validators + strict website prerender green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Follow-up to #7/#9 after live agent testing, and an editorial tightening ahead of standards review: discoverability was spread over four overlapping hints (manifest, catalogue arrays, prose recommendation, client nudges), which both fails catalogue-first consumers and reads as a protocol weakness. 0.9.5 names one mechanism and withdraws the rest:
workflowscross-link array on both operation surfaces: catalogue entry (as in 0.9.4) AND the schema document as a top-level member (JSON Schema tolerates unknown keywords; BEST names this one). Same ids on both - deriving both from the recipe definitions keeps drift impossible.Additive only; 0.9.4 servers remain conformant (the schema-document member is a SHOULD).
Verified: schema + example validators green; strict website prerender green (it caught and I fixed a bad anchor).
Release after merge:
LC_ALL=en_US.UTF-8 ./scripts/release.sh 0.9.5, then best-mcp 2.3.2 (separate PR: deterministic read-the-recipe note when a fetched schema carries the cross-link).🤖 Generated with Claude Code