CI gate freshness alert: 2 gate(s) have no recent successful `main` run

[github-actions]

The following post-merge gates have not produced a successful main run 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 success 54.4h 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.
npm-publish-freshness.yml	NO successful post-merge run in the sampled window	Daily comparison of npm's latest against this tree (#7491: users installed a month-old build and hit a linker bug fixed weeks earlier). Its own cron going dark would restore exactly the blind spot it was built to close. Note the overlap by design: while the registry is genuinely behind, this workflow fails, produces no successful run, and therefore also appears HERE -- one alarm is the release being overdue, the other is nobody watching.

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.