Fix 4 MCP registration-coverage test failures#404
Merged
Conversation
…han OCS atoms The registration-coverage snapshot test had drifted: atoms were added to the connect, ocs, and google-drive MCP servers without updating the expected-count snapshots, and 5 newer OCS authoring atoms (create_chatbot, link_action_to_node, add_custom_action, add_chatbot_event, add_pipeline_node) were registered on the server but missing from mcp/ocs/capability-map.ts, breaking the "every prefixed server tool has a capability-map entry (no orphan atoms)" invariant. Snapshot bumps: connect 30 -> 47, ocs 27 -> 32, google-drive 31 -> 32. Added the 5 orphan atoms to the OCS capability-map under the Authoring section with PLAYWRIGHT backend annotations describing their CSRF-protected form views (none yet exposed as first-class REST endpoints). Suite now 1314/1314 passing. VERSION jumps 0.13.328 -> 0.13.330 to resolve a bookkeeping race: PR #402's CHANGELOG section header announced 0.13.329 but its merged commit retained VERSION=0.13.328 (the rebased pre-amend version), leaving main with CHANGELOG and VERSION out of sync. This PR realigns them. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
Clean up pre-existing failures in
test/mcp/registration-coverage.test.ts. Snapshot counts had drifted as atoms were added to connect/ocs/google-drive servers, and 5 OCS authoring atoms were registered on the server but missing frommcp/ocs/capability-map.ts— breaking the orphan-atom invariant.What changed
Snapshot bumps in
test/mcp/registration-coverage.test.ts:5 orphan OCS atoms added to capability-map under Authoring (all PLAYWRIGHT backend):
create_chatbot— CSRF-protected ChatbotFormlink_action_to_node— appends to pipeline node's data.params.custom_actionsadd_custom_action— CSRF-protected CustomActionFormadd_chatbot_event— CSRF-protected combined-form view for timeout triggersadd_pipeline_node— GET-mutate-POST pipeline JSONVersion bookkeeping.
VERSIONjumps0.13.328 → 0.13.330to resolve a race from PR #402: that PR's CHANGELOG header announced 0.13.329 but its merged commit retainedVERSION=0.13.328(a rebased pre-amend version), leaving main with the two out of sync. This PR realigns them and adds the## 0.13.330MCP-fix section.Test plan
npm test— 1314/1314 passing locally (was 1310/1314).clean-installcheck🤖 Generated with Claude Code