fix(docs): document recurring orchestration tasks

[ashx-j]

The orchestrator MCP documentation claimed eleven tools and omitted the four existing recurring-task tools. It also presented t3_thread_launch without identifying its project-toolkit ownership.

Replaces the stale count with a link to the authoritative toolkit, adds concise recurring-task guidance, identifies the project toolkit, and updates the purpose and verification lists. No runtime behavior changes.

Fixes #15670.

Validation: compared the documentation with all fifteen OrchestratorToolkit registrations, scheduling handlers, endpoint registration, and existing scheduling integration-test assertions. Both source links resolve and git diff --check passes. Runtime tests were unnecessary for this documentation-only patch. A separate GPT-6-Astra reviewer at medium reasoning approved the patch with no findings.

Implemented by GPT-6.1-Sol at xhigh reasoning through the Codex harness.

[macroscopeapp]

Approvability

Verdict: Approved at 65ea216

Macroscope's review found this PR approvable — This PR only updates orchestration documentation and links to existing tool contracts and coverage; it does not change executable code, product defaults, configuration, or runtime behavior.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4800223c-15e1-4bda-b854-d45342d3330c

📥 Commits

Reviewing files that changed from the base of the PR and between 4ee6bfd and 65ea216.

📒 Files selected for processing (1)

• docs/orchestration-v2/orchestrator-mcp-server.md

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The Orchestrator MCP documentation now covers recurring scheduled tasks, clarifies which toolkits share the endpoint, and links to current orchestration toolkit registrations.

Changes

Orchestrator MCP documentation

Layer / File(s)	Summary
Document toolkit and recurring-task behavior docs/orchestration-v2/orchestrator-mcp-server.md	The document replaces the fixed orchestration tool count with a link to current registrations. It describes recurring-task creation, thread behavior, inherited settings, project-scoped listing, updates, pausing, resuming, and deletion. It also clarifies toolkit ownership and adds recurring-task checks to the integration-test coverage list.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other · Severity of issue fixed: Low

Suggested reviewers: t3dotgg

Merge Risk: ⚪ Minimal · up to 65ea2

The documentation matches the described recurring-task workflow and toolkit ownership; it is ready to merge after normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the documentation change to recurring orchestration tasks.
Description check	✅ Passed	The description explains the problem, the documentation changes, the linked issue, and the verification performed. It also states that runtime behavior does not change. The content is mostly complete,…
Linked Issues check	✅ Passed	[ #15670 ] The document removes the inaccurate eleven-tool count and links to the authoritative OrchestratorToolkit. It adds guidance for creating, listing, updating, pausing, resuming, and deleting r…
Out of Scope Changes check	✅ Passed	All changes support accurate discovery of the endpoint's capabilities. The endpoint description identifies its other toolkits, and the t3_thread_launch note correctly identifies ProjectToolkit ownersh…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}