exp(codex): print dispatch tuples from SDD scripts — v2 chokepoint for PRI-2672

Run-2 dispatch-4 autopsy: after compaction, the codex-tools role table
fell out of context and the controller reasoned itself into an inherited
sol@max reviewer — the harness's own 'inherited parent model is preferred'
plus SKILL.md's 'most capable model' outvoted the compaction summary's
distilled 'terra/high' line. Its introspection named the only artifact it
actually consults at the moment of dispatch: the review-package output.

So the role tuple now rides the script output, reprinted fresh every
round, immune to compaction by construction:
- task-brief prints role=implementer terra/high fork_turns=none
- review-package prints per role via a new leading --role flag
  (task-review default | re-review | final-review), and SKILL.md call
  sites pass the flag at the re-review and final-review sites
- SKILL.md Model Selection now defers to platform role tables and the
  printed dispatch hints, closing the 'most capable model' loophole
- codex-tools.md tells the controller to copy the printed tuple verbatim

Harness detection considered and rejected: gating the print on CODEX_CI
risks a silent no-op in exactly the environment that needs it; the line
is labeled '(codex spawn_agent)' instead, and CC controllers — whose
templates carry their own model fields — can ignore it.

Experiment branch for PRI-2672 validation; not for merge without eval
evidence.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

skills/using-superpowers/references/codex-tools.md

@@ -32,6 +32,9 @@ Before Task 1, check your `spawn_agent` tool schema for `model` and
 
 On Codex this table IS the Model Selection mapping — including the final
 review, which stays on terra/high rather than "most capable available."
+The task-brief and review-package scripts reprint the applicable row as a
+`dispatch (codex spawn_agent):` line with their output — copy those values
+onto the spawn_agent call verbatim, every time, even late in a long session.
 Never give a subagent your session's model when you run a frontier config
 (sol at xhigh or max): reviewer tier never exceeds implementer tier, and
 a fix round never gets an effort bump. Rounds 4-5's "more capable model"