[Bug]: t3_thread_update lists unsupported pull request actions #26118

Summary

The t3_thread_update section in docs/orchestration-v2/orchestrator-mcp-server.md lists link_pull_request and unlink_pull_request as accepted actions. Its registered input schema accepts only rename and regenerate_title; PR links use separate tools. A reader using the documented actions would construct an input outside the registered schema.

Steps to reproduce

1. In a checkout of each baseline under Version or commit, read the t3_thread_update section of the document.
2. Compare its four named actions with ThreadMetadataMcpAction in packages/contracts/src/threadMetadataMcp.ts and the ThreadUpdateTool parameters in apps/server/src/mcp/toolkits/orchestrator/tools.ts.
3. Find LinkPullRequestTool and UnlinkPullRequestTool in apps/server/src/mcp/toolkits/pullRequests/tools.ts. These are separate named tools, rather than actions on the metadata tool.

These read-only source/document comparisons were executed for all three baselines. No invalid MCP call was sent.

Expected behavior

The existing repository documentation policy says to rewrite or remove affected text when a documented decision or constraint changes. The metadata-tool description should agree with the input schema currently registered for it, or point readers to that authoritative schema.

Actual behavior

All three inspected baselines have the same mismatch:

Documentation actions: rename, regenerate_title, link_pull_request, unlink_pull_request
ThreadMetadataMcpAction: rename, regenerate_title
Separate Tool.make names: link_pull_request, unlink_pull_request

ThreadUpdateTool uses ThreadMetadataMcpUpdateInput, whose action is ThreadMetadataMcpAction. Thus the two PR actions are outside this tool’s accepted input domain. This is a documentation bug; no runtime PR-link failure was measured.

Evidence

• Expected source: metadata-tool prose and the repository documentation policy cited above.
• Failure source: action/input schema, registered metadata parameters, and separate PR-link tools; the same relevant clauses and source branches were read at both release tags.
• Evidence provenance: observed
• Local verification: reproduced
• Reproduction completeness: complete

The reproduced failure is the documentation/source mismatch. The source branches explain the mismatch; runtime operations and project tests were not executed.

The orchestration-v2 document-set README describes target architecture. This report is limited to this page’s concrete present-tense description of implemented MCP behavior, and does not ask to implement the obsolete description. The repository documentation policy permits rewriting or removing stale guidance and linking to authoritative source.

Restoration check

Repeat the comparison on the revision being reviewed. Passing documentation no longer directs readers to submit PR-link actions to t3_thread_update; any retained PR-link guidance identifies the actual tools or their authoritative reference. Keep supported rename and title-regeneration behavior accurately described. No runtime API change is needed to restore this documentation contract.

Version or commit

Inspected repository source at current main 4914cdd98f3d15ab2ddef34f0af70d3d68a2d8e5, latest published nightly v0.1.4-nightly.20261027.3783 (dc84b0962efa4f4e05ef392c08986a9cd7c994d1), and latest stable v0.1.3 (d2c440312e5f39d59827ed466838a623516454d6). This is a platform-independent documentation/source comparison. No T3 server, provider session, live MCP mutation, or test suite was run.

Area

Docs

Impact

Minor bug or occasional failure.

Workaround

Compare the metadata input schema and use the separate link/unlink tools already registered in source. Their availability was verified statically, not through a live call.

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

References

Open report #15670 and open PR #23199 cover the tool count and recurring-task discoverability. They do not correct this contract. No comment is requested on either thread.

Triage assessment

• Impact level: P2
• Assessment status: supported
• Impact basis: The page gives concrete API inputs outside the registered schema. This can misdirect integrations or agents following the developer reference; no live failure or frequency is claimed.
• Workaround status: available
• Workaround basis: Compare the metadata input schema and use the separate link/unlink tools already registered in source. Their availability was verified statically, not through a live call.