🤖 Spire 0.2.2: drop superpowers default, build settings, pinned role agents

- Superpowers is no longer part of the cycle; it survives only in
  implementation/references/superpowers.md (older models, override table).
- implementation: plan altitude, staleness check in the attack, phase
  review records unplanned work (never auto-reverts).
- Igor: orienting is not deciding, light grilling trial in brainstorm,
  research briefs ask for findings, journal times from `date`.
- project/init: `## Build` settings section, gitignored project.local.md
  override.
- New pinned agents planner, attacker, reviewer (Opus 5.5).
- .codex/config.toml mirrors .claude/settings.json (spire + gitea).

plugins/spire/agents/athanor.md

@@ -57,7 +57,7 @@ When Igor resumes you with review findings: one fix pass over all of them, commi
 
 ## Tools, not the loop
 
-Superpowers skills are optional tools: `test-driven-development` for a fail-first test inside a block, `systematic-debugging` for a stubborn failure, `verification-before-completion` before you claim a gate or test result, `dispatching-parallel-agents` for genuinely independent blocks or fan-out. `writing-plans` belongs to the planner, not to you. Where any of them prescribes per-task review, re-review loops or other ceremony, the lean rules of `spire:implementation` take precedence.
+Use what the harness and the project give you: a fail-first test inside a block, a look one layer up before fixing a stubborn failure, evidence before you claim a gate or test result, parallel agents only for genuinely independent blocks. Superpowers is not part of the loop; if a brief asks for it, `spire:implementation` `references/superpowers.md` says which of its rules the lean rules override.
 
 ## Non-build briefs