CI gate freshness alert: 7 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-root-dominance.yml	last failure result 30.0h 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.
tls-budget.yml	last success result 23.5h ago (budget 12h)	_tlv_get_addr call-count ratchet. macOS-only by nature; cannot be relieved by moving pools.
gc-native-roots.yml	last failure result 28.1h ago (budget 12h)	RS4GC native-roots arm.
gc-moving-witnesses.yml	last success result 29.5h ago (budget 12h)	Asserts the copying minor actually moved objects -- the 'gate must assert its subject was live' arm (#7024/#7025).
auto-opt-app-patterns.yml	last success result 29.2h ago (budget 12h)	Auto-optimize app-pattern regression sweep.
eh-transport.yml	last success result 23.5h ago (budget 12h)	Owned unwinder transport on arm64 macOS.
llvm-inprocess.yml	last success result 28.1h ago (budget 12h)	In-process LLVM backend arm; the promotion prerequisite.

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.