🤖 Pin Athanor and Zathras to Opus 5.5 [1m]

Repins both agents to claude-opus-5-5[1m] per user decision (2026-10-05),
bumps Spire to 0.2.0, and resolves the open question in
spawning-claude-code.md about Athanor's context window suffix.
This commit is contained in:
2026-10-05 22:21:45 +02:00
parent 5909221022
commit f40cbf5a2a
5 changed files with 5 additions and 5 deletions
@@ -51,7 +51,7 @@ The harness changes. When a claim fails, fix it here with a new date.
| A 4.6 Igor passing `model: "opus"` to the then 4.6-pinned Athanor got a 4.6 run (the dirigent end review that passed with zero findings). | observed 2026-10-05 (user's attribution; the dirigent report recorded the model as unknown). Consistent with both the alias following the caller and the pin holding, so it is not evidence for alias-over-pin. The 184/184 row and the schema are. |
| What the `opus` alias resolves to (the caller's model, a session default, or the newest Opus). | unknown. Check the stamped id of every plan, attack and review instead of relying on it. |
| Every agent sees its exact model id in its system prompt. | observed 2026-10-05 for general-purpose agents (prompt shows `claude-opus-5-5`); not checked for plugin agents with their own bodies |
| Context window of the bare `claude-opus-5-5` pin versus a `[1m]` suffix (other Spire pins carry `[1m]`). | unknown; the ~600k guesstimate in `models.md` assumes the larger window |
| Context window of the bare `claude-opus-5-5` pin versus a `[1m]` suffix (other Spire pins carry `[1m]`). | resolved 2026-10-05: Athanor and Zathras repinned to `claude-opus-5-5[1m]` (user decision), matching other Spire pins; the ~600k guesstimate in `models.md` assumes the larger window |
## Fork