[fikaventures]

Why

Pstack's standalone launcher instructions conflict with T3 Code's host-owned delegation. Add a T3 route at the existing dispatch boundary so pstack keeps its role, model and effort choices while the parent uses T3's tools.

Closes #253.

What changed

• Add pstack-t3 to compile capability-backed requests and normalize actual T3 responses. Async completion requires the retained launch identity.
• Add host-specific routing and lifecycle guidance to the shared dispatch reference, with narrow pointers from affected skills and playbooks.
• Add process-boundary checks with replayable artifacts and wire them into the normal test command and verification path map.

Scope

• Local T3 delegation for Claude and Codex, including inherited native eligibility and requests for T3-prepared worktrees.
• Standalone launchers and CLI receipt semantics remain intact. Linked-environment delegation and unavailable providers refuse.
• Source implementation only. Installed-plugin verification, the published live gate, installation and release remain pending.

Tradeoffs

The helper emits tool arguments; the parent makes the actual MCP calls. T3 configuration reports remain distinct from provider-served-model proof. Unattested confinement and recursive-delegation requirements refuse before launch.

Blast Radius

Host detection and the T3-specific path affect agent dispatch. Existing standalone routing retains its implementation and focused regression coverage.

Verification

• Process harness: 48 cases pass, with baseline and focused regression failures recorded before implementation or fixes. Existing CLI and registry checks: 43 pass. Strict typecheck, source static invariants, manifest parsing and skill validation pass.
• Real Codex-parent T3 session: compiled requests launched Claude at high effort and Codex at xhigh. Initial responses normalized to pending; actual terminal responses normalized to complete with matching task identities and expected output. Local inputs, responses and replay assertions are retained.
• Installed Claude-parent and Codex-parent plugin behavior, worktree writes and the repository live gate are not claimed. Unrelated full suites were deferred under the operator's testing instructions. The static check run excluded release and verifier test suites.

[mergify]

Merge Protections

🔴 1 of 2 protections blocking · waiting on 🤖 CI and 🙋 you

	Protection	Waiting on
🔴	Queue ready pull requests	🤖 CI and 🙋 you
🟢	🚦 Auto-queue	—

🔴 Queue ready pull requests

Waiting for

• -draft
• check-success=live-gate
• check-success=verify

This rule is failing.

Automatically queue non-draft pull requests targeting main after verify and live-gate pass on the head and every review thread is resolved.

• -draft
• check-success=live-gate
• check-success=verify
• #review-threads-unresolved = 0

---

Show 1 satisfied protection

🟢 🚦 Auto-queue

When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.

• -files~=^\.github/
• base = main

[greptile-apps]

[Medium impact] No code defect was found that blocks merging; the separately required live gate remains pending as stated in the PR.

Summary

Adds a T3 route at the shared dispatch boundary without changing the standalone runner.

• T3 sessions can keep pstack assignments while T3 launches supported agents.
• T3 results stay pending until matching terminal output is available.

_{Reviews (1) · Last reviewed commit: "Support T3-owned pstack delegation" · Reviewed by Greptile}