main-push CI is red at d8e3a5a76f00

[ci] red @d8e3a5a76f00f5740900936b53adea797ddfd906 on github-actions

Existing Actions gates for this exact main-push head; no additional test run.

- ci-aggregate.yml: awaiting matching run
- ci-modules.yml: in_progress/None (https://github.com/spec-kitty/spec-kitty/actions/runs/34801248303, attempt 1)
- ci-quality.yml: completed/failure (https://github.com/spec-kitty/spec-kitty/actions/runs/34801248049, attempt 1)
- ci-router.yml: in_progress/None (https://github.com/spec-kitty/spec-kitty/actions/runs/34801248091, attempt 1)
- ci-windows.yml: in_progress/None (https://github.com/spec-kitty/spec-kitty/actions/runs/34801248040, attempt 1)
- packs.yml: in_progress/None (https://github.com/spec-kitty/spec-kitty/actions/runs/34801248074, attempt 1)

Verdict-Role: ci
Verdict-Account-Class: bot
Verdict-Session: github-actions-34801362066
Verdict-Repo: spec-kitty/spec-kitty
Verdict-Head: d8e3a5a76f00f5740900936b53adea797ddfd906
Verdict-Host: github-actions
Verdict-Attempt: 1
Verdict-Contract-Version: 1

This observes the current main head, not nightly/full-suite release acceptance. Path-filtered gates are included when a matching push run exists; absent conditional gates are listed in the evidence.

Red main is P0 under PROGRAM.md section 9 and agents/ci.md step 6. The fleet should investigate the named failing gates; this report does not attribute a culprit PR or test node. A later green observation is recovery evidence for the fleet to assess, not automatic closure.

Start with the ci-quality.yml run linked in the issue for head d8e3a5a76f00f5740900936b53adea797ddfd906, then inspect the other listed workflow runs as they finish. Identify the failing gate and its relevant logs; done means the affected main-push checks recover to green and the cause is documented.

Written by the indexing model from the issue text.