CI gate freshness alert: 4 gate(s) have no recent completed `main` result

[github-actions]

The following post-merge gates have not produced a completed main result within their freshness budget.

This usually means they are starved, not broken — queued behind a merge cadence the runner pool cannot drain (#7856). Check the Actions queue depth before assuming a code failure:

gh api "repos/PerryTS/perry/actions/runs?status=queued&per_page=100" \
  -q '.workflow_runs | length'

gate	detail	why it matters
gc-ratchet.yml	last failure result 264.1h ago (budget 12h)	Primary defence for collector retention/evacuation accounting. Went dark 2026-08-09..08-11 while #7799/#7809/#7812/#7834/#7839 merged; #7843's seven red rows landed in that window.
gc-root-dominance.yml	last failure result 264.1h ago (budget 12h)	Static GC root-dominance checker over emitted LLVM IR. Its allowlist is empty, so every new hit is a red build -- worth nothing if the gate never runs.
llvm-inprocess.yml	last success result 271.2h ago (budget 12h)	In-process LLVM backend arm; the promotion prerequisite.
security-audit.yml	last failure result 259.0h ago (budget 12h)	Dependency, soak and supply-chain audit called from every main sweep. Reusable-workflow jobs live on test.yml's run, so freshness requires all five nested jobs to complete.

Scheduling rationale and the cost it trades away: docs/src/testing/ci-gate-scheduling.md.

This issue is maintained automatically by gate-freshness.yml. It is updated in place, never duplicated, and closes itself once every gate is fresh again.

[github-actions]

All post-merge gates are fresh again; closing automatically.