fix(skill-repair): close systemic zero-token outage

[Svector-anu]

Symptom

Five sampled fleet runs failed before inference with the same zero-token envelope. Representative failure: https://github.com/Svector-anu/svectors-lab/actions/runs/32785060442.

Diagnosis

The signature was consistent in 5/5 recent failures: Claude returned HTTP 429 because its weekly allowance was exhausted, then the configured Bankr fallback returned HTTP 402 because gateway credits were exhausted. Each run consequently recorded zero input/output tokens, empty iterations, and empty model usage. This is a systemic config fault, not a skill prompt or implementation regression.

Root cause

The fleet depended on two simultaneously exhausted inference paths. Commit 2958e51 had already switched the shared harness to Codex using provisioned native CODEX_AUTH, which bypasses both failed providers.

Fix

Close ISS-001 with the corrected root cause and affected-skill set, record the shared fix and full verification evidence, move the issue to the resolved index, persist the 24-hour repair cooldown, and append the required repair log.

Risk

LOW — tracker and repair-state records only; the shared harness fix is already on main and no runtime configuration changes are introduced by this PR.

Verification

Manual triggers:

• https://github.com/Svector-anu/svectors-lab/actions/runs/32793905964 (defi-overview)
• https://github.com/Svector-anu/svectors-lab/actions/runs/32794496219 (token-pick)
• https://github.com/Svector-anu/svectors-lab/actions/runs/32795173291 (narrative-tracker)
• https://github.com/Svector-anu/svectors-lab/actions/runs/32796244458 (fear-divergence)
• https://github.com/Svector-anu/svectors-lab/actions/runs/32796246156 (skill-health)

Expected result:

• Workflow conclusion: success
• memory/logs/2026-08-25.md mentions skill-repair
• Every affected skill uses Codex native OAuth, records non-zero token usage, and has no Claude 429 or Bankr 402 zero-token error

All five expectations passed. If the signature recurs, delete memory/state/skill-repair-history.json["systemic-zero-token"], then re-dispatch skill-repair for a second pass.

Source status

cron_state=ok | issues_index=ok | gh_runs=ok | gh_logs=ok | git_log=ok | check_runs=fail

The check-runs REST lookup returned 404; equivalent workflow annotations were obtained from gh run watch for both fresh verification runs.