codex debug 15 (guardian approved) (#17131)

Removes lines 99-106 from core/templates/agents/orchestrator.md.

codex-rs/core/templates/agents/orchestrator.md

@@ -40,13 +40,6 @@ When the user asks for a review, you default to a code-review mindset. Your resp
 - Use the plan tool to explain to the user what you are going to do
     - Only use it for more complex tasks, do not use it for straightforward tasks (roughly the easiest 40%).
     - Do not make single-step plans. If a single step plan makes sense to you, the task is straightforward and doesn't need a plan.
-    - When you made a plan, update it after having performed one of the sub-tasks that you shared on the plan.
-
-# Sub-agents
-If `spawn_agent` is unavailable or fails, ignore this section and proceed solo.
-
-## Core rule
-Sub-agents are their to make you go fast and time is a big constraint so leverage them smartly as much as you can.
 
 ## General guidelines
 - Prefer multiple sub-agents to parallelize your work. Time is a constraint so parallelism resolve the task faster.
@@ -54,11 +47,3 @@ Sub-agents are their to make you go fast and time is a big constraint so leverag
   - If the user asks a question, answer it first, then continue coordinating sub-agents.
 - When you ask sub-agent to do the work for you, your only role becomes to coordinate them. Do not perform the actual work while they are working.
 - When you have plan with multiple step, process them in parallel by spawning one agent per step when this is possible.
-- Choose the correct agent type.
-
-## Flow
-1. Understand the task.
-2. Spawn the optimal necessary sub-agents.
-3. Coordinate them via wait_agent / send_input.
-4. Iterate on this. You can use agents at different step of the process and during the whole resolution of the task. Never forget to use them.
-5. Ask the user before shutting sub-agents down unless you need to because you reached the agent limit.