[Bug]: T3_CODE_ORCHESTRATION_INSTRUCTIONS has no carve-out for user- or repo-mandated CLI review workflows (unlike T3_CODE_BROWSER_TOOL_INSTRUCTIONS)

[AnobleSCM]

Before submitting

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

Area

packages/provider-core, apps/server

Steps to reproduce

1. In a repository whose AGENTS.md (or user prompt) mandates a repository-owned CLI review runner (for example, a read-only shell command that prepares an isolated review packet and runs a cross-provider reviewer CLI with --strict-mcp-config and structured verdict parsing), start a Codex turn in T3 Code with the t3-code MCP server attached.
2. Ask the agent to run the repository's required code review workflow.
3. Observe how strict instruction-hierarchy models (such as Codex) resolve the conflict between the repository workflow / user prompt and t3_code_orchestration (T3_CODE_ORCHESTRATION_INSTRUCTIONS) injected in turn/start.additionalContext.

Expected behavior

When the user or a documented repository workflow/skill explicitly names a dedicated CLI runner or script for a review or check, the agent should follow that workflow rather than refusing it on the ground that T3_CODE_ORCHESTRATION_INSTRUCTIONS requires delegate_task.

T3_CODE_BROWSER_TOOL_INSTRUCTIONS in the same file (packages/provider-core/src/server/orchestrationInstructions.ts L49–54) already includes this exact carve-out for browser tools:

Use another browser system when:
- the T3 preview tools are absent, or `preview_open` returns an explicit unsupported/unavailable error;
- the user asks for another browser, or invokes a skill or documented repository workflow that names one; follow that workflow and report any prerequisite it is missing;

Actual behavior

T3_CODE_ORCHESTRATION_INSTRUCTIONS (packages/provider-core/src/server/orchestrationInstructions.ts L9–11) currently states unconditionally:

• Also use delegate_task for cross-provider or explicitly T3-owned child tasks.
• For every T3 delegated review round, call delegate_task again.

For Codex turns (apps/server/src/orchestration-v2/Adapters/CodexAdapterV2.ts L766–775 → buildCodexAdditionalContext in apps/server/src/provider/CodexDeveloperInstructions.ts L146–164), t3_code_orchestration is injected as { kind: "application", value: T3_CODE_ORCHESTRATION_INSTRUCTIONS }, which Codex renders as a developer-level <t3_code_orchestration> message. Because developer instructions outrank AGENTS.md and user messages in Codex's instruction hierarchy, Codex sessions refuse to run a repository's shell-based review runner even when both AGENTS.md and the user explicitly tell them to use the repository runner instead of delegate_task.

Suggested fix: in T3_CODE_ORCHESTRATION_INSTRUCTIONS (packages/provider-core/src/server/orchestrationInstructions.ts), add a short exception parallel to T3_CODE_BROWSER_TOOL_INSTRUCTIONS—for example, noting that when the user or a documented repository workflow/skill explicitly names a specific CLI runner or script for a review or check, the agent should follow that workflow instead of delegate_task.

Impact

Blocks core workflow

Version or commit

0.0.46-nightly.20261014.3132; still present on main @ 42da166d13

Environment

macOS, Apple Silicon. T3 Code Desktop Nightly 0.0.46-nightly.20261014.3132. Provider: Codex (gpt-5.4 / gpt-6.1-sol).

[nivethass15102007-tech]

Hi! I'd like to work on this issue as one of my first open-source contributions. I understand the proposed fix is to add an exception to T3_CODE_ORCHESTRATION_INSTRUCTIONS for explicitly required CLI review or check workflows, similar to the existing browser-tool exception.

Would you be open to a small, focused PR for this? I will keep the change limited to the intended behavior and verify it before submitting.