feat(tool): support canonical Veryfront MCP identities - #4469
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
|
|
Closing this draft as superseded by the merged compatibility direction in veryfront/veryfront-api#4752 and #4468. Existing routes now negotiate canonical catalog names, and Code explicitly requests legacy transport names to preserve saved selectors and policy behavior. The full v2-route/trusted-finalizer migration in these parallel drafts is no longer the smallest compatible implementation. The branch and local work remain preserved. This does not close veryfront/veryfront-issue-inbox#1055: canonical public defaults, canonical tool-reference discovery, Studio compatibility, scoped project-identity regressions, and staging invocation/mixed-version evidence remain gates. Narrow missing behavior will be handled against current main instead of merging this entire draft. |



Links veryfront/veryfront-issue-inbox#1055.
This Code-library lane adds typed
tools/listparams with resolver support, preserves them across pagination, exports one trusted Veryfront identity finalizer, enables canonical discovery for the default Veryfront API source, and makes MCP allow/deny policy match authoritative platform aliases with deny precedence. Generic third-party MCP sources retain exact-name behavior and receive no Veryfront metadata.Out of scope: API routes and mutation normalization, Agent wrapper/package adoption, Studio rendering and persistence, package publication, deployment, and issue closure.
Red/green evidence: the new focused tests initially failed because the list-param/finalizer exports and behavior did not exist. After implementation, the focused suite passes 65 assertions.
Verification:
PATH=/tmp/deno-2.7.7:$PATH deno task test:file src/tool/remote-mcp.test.ts src/agent/mcp-tool-policy.test.ts src/agent/service/mcp-server-config.test.tsdeno checkon modified implementation filesStaging plan: after API metadata support and Agent package adoption are merged through their separate lanes, capture canonical
tools/listpackets, verify old-API legacy fallback, and run the persisted/scoped allow/deny compatibility matrix. This PR alone cannot close the inbox issue.