Remove Terra from the policy; Codex resume uses the job's active dispatch route #62

Parent

#10

Contribution to the Objective

Keeps one versioned policy as the single source of routes. Luna covers dispatch capably and cheaply; an unused manual route is only a way to land on the wrong model.

Outcome

Terra (gpt-5.6-terra) is gone from the project. Codex resume always uses the job's active dispatch route.

Evidence (planner, 2026-09-23, origin/main 1666b4a)

• User direction 2026-09-23: do not use Terra anywhere in this project.
• Terra appears as route terra/max and in the dispatch stage's manual list (runner/policy.py), in skills/model-routing/references/codex.md, RUNNER.md, and tests/test_policy_v2.py.
• controller.resume_luna resumes with stage_routes("dispatch")[0] and records meta.route = "luna/max" whatever route the job was dispatched on.

Acceptance criteria

• terra/max route and the dispatch stage manual entry are removed; stage notes no longer mention Terra.
• skills/model-routing/references/codex.md is regenerated with python3 -m runner.policy render-skill; RUNNER.md no longer mentions Terra.
• resume_luna builds the resume command and records meta.route from the job's active Codex dispatch route.
• Tests updated: no test depends on Terra; a test proves resume uses the active route's model and route name. git grep -i terra returns nothing.
• python3 -m runner.policy validate passes.

Non-goals

• Any other route or stage change.

Blocked by

• None

Required proof

• Full deterministic suite green on the exact SHA; independent review.