Seat the ticket review council on Claude Opus 5.5 and Codex GPT-6.1 Sol

MiMo leaves the council. Codex is now installed and signed in through T3,
so the second model family comes from GPT-6.1 Sol instead.

user/agents/skills/ticket/COUNCIL.md

@@ -14,8 +14,8 @@ final tree.
 
 | Seat | `providerInstanceId` | `model` |
 |---|---|---|
-| Claude | `claudeAgent` | omit it, so the seat runs that provider's default |
-| MiMo | `opencode` | `opencode-go/mimo-v2.6-pro` |
+| Claude | `claudeAgent` | `claude-opus-5-5` |
+| Codex | `codex` | `gpt-6.1-sol` |
 
 Klaude never takes a seat. It is the work account, and its only job is the `pre-mr-review` run
 in Phase 2 step 7, which stays a separate required step after the council.
@@ -92,7 +92,7 @@ Two seats reporting the same thing is one finding with more weight behind it. A
 seat raised is still worth checking, since catching what the others miss is why the seats differ.
 
 Put each on the page as you judge it, with its grade and its seats in the text:
-`finding <KEY> add "[should] <text> (Claude, MiMo)" --severity CONFIRMED --where <file:line>`, then
+`finding <KEY> add "[should] <text> (Claude, Codex)" --severity CONFIRMED --where <file:line>`, then
 `fixed --commit <sha>`, or `rejected --reason "<why>"`.
 
 - **Fix every blocker and should you confirm,** each meaningful fix as its own commit. These do