feat(mcp): manage queued thread work

[juliusmarminge]

Problem

Agents could enqueue work but could not inspect or safely manage queued runs through MCP.

Change

• Add bounded t3_queue_list and t3_queue_read tools.
• Add receipt-backed edit, reorder, cancel, and promote-to-steer operations.
• Preserve omitted attachment lists, while an explicit empty list clears attachments.
• Enforce caller runtime and interaction ceilings for prompt-changing operations inside the serialized V2 decision.

Behavior

Fresh mutations validate current project scope and queued-run state. Accepted retries return the original durable result before mutable attachment or lifecycle checks. Reorder results distinguish a replayed request from a newly applied destination, and list previews remain bounded without splitting Unicode surrogate pairs.

Validation

• 87 focused queue service, MCP/V2 integration, Claude capability, and contract tests.
• Scoped @t3tools/contracts and t3 typechecks.
• Formatting and type-aware lint for all changed files.

Base

Standalone PR on t3code/codex-turn-mapping at 415ed0f73b97f1655b6282492f81d0b2bba3a9cc.

Implemented by GPT-5.6-Sol via Codex in T3 Code.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 28d9d494-7e7b-46ba-b3c9-480a53c5d667

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

One convention violation found in the new Effect service module. See inline comment.

^{Posted via Macroscope — Effect Service Conventions}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fd15a16.

This comment will update automatically after the next completed run.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit ebc47f0. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds six production MCP tools that let agents inspect and mutate queued work, including editing prompts, reordering or cancelling runs, and promoting queued messages into active steering. It also changes shared orchestration policy, locking, and durable replay behavior, creating a broad runtime surface that merits human review.

No code changes detected at fd15a16. Prior analysis still applies.

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

[macroscopeapp]

Reviewed the queued-work MCP service, contracts, toolkit, and the orchestrator/thread-management additions against the Effect service conventions. The service definition itself now follows the canonical shape (inline Context.Service interface, real make, exported layer). One small deviation remains in the new orchestrator surface.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI Consistency: environment routing regression in a shared renderer

One concrete violation of the environment-routing rule, plus one dead global CSS rule introduced by this change. Everything else I checked in the web UI scope (MenuPopup width defaulting contract, @variant dark/light usage, the virtualized/topbar scroll-fade masks preserving the scrollbar lane, and the thread details panel rows composing Button/Select/Tooltip primitives) looked consistent.

• apps/web/src/components/ChatMarkdown.tsx — the shared markdown renderer now resolves its server config and "open in editor" RPC from the globally active environment instead of explicit scope.
• apps/web/src/components/pullRequest/PullRequestMarkdown.tsx — the pull request panel no longer passes an explicit environment to that renderer (environmentId is now an accepted-but-unused prop).
• apps/web/src/index.css — the new .surface-subheader rule has no consumers; the four call sites use the data-surface-subheader attribute instead.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding on the new QueueMcpService error translation. Everything else (inline Context.Service interface, make/layer shape, namespace import in McpHttpServer, Foo["Service"] typing in Orchestrator/ThreadManagementService, toolkit wiring) matches the existing worktree/orchestrator MCP conventions.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

One finding on the new queue MCP service: the dispatch-error translation boundary discriminates statically known tagged failures by duck-typing an unknown value instead of the declared OrchestratorV2Error channel.

^{Posted via Macroscope — Effect Service Conventions}

[juliusmarminge]

Superseded as the active MCP proposal by #10555 in the rebuilt MCP stack, following the maintainer request to review thin service wrappers separately from service hardening.

This is not a full feature-parity replacement. Output text is bounded by Unicode code points. Paging is a live offset. Queue ordering, dispatch and replay semantics remain in the existing services.

Closing this mixed proposal without merging. The remote branch agents/mcp-queue-inputs/controls and exact head fd15a16174a8c7f2de6bb735d652c8d172ce9e96 are retained so the service changes can be extracted for separate review later.