ci: GitHub Actions has not run since 2026-06-01 — 54 commits have landed on main unverified

Evidence

No workflow run of any kind has executed in this repository since 2026-06-01, while main has advanced by 54 commits (git rev-list --count --since=2026-06-02 origin/main).

The three most recent ci.yml runs on main are all from that day, and all three concluded cancelled rather than success or failure:

Pushes to main on 2026-09-17 (7503300c, 5d7c9be4, 135ce6c0, 5bd2e852) triggered no run either, so this is not a stale-listing artifact.

All 13 workflows report state: active, so they have not been individually disabled. A newly added workflow registers normally (Toolchain, id 360886058) but likewise does not fire — which points at the repository- or org-level Actions switch rather than at any one workflow file.

Impact

Everything the pipeline is supposed to gate has been unenforced for three and a half months:

• zig build and zig build test --summary all across the Linux/macOS/Windows matrix
• zig build test-diagnostics snapshot tests
• the TS conformance delta gate
• lint and typecheck

Note the last conformance-gate runs before the outage were already failure, so the most recent known state of that gate is red.

This also removes the fallback for contributors who cannot install the toolchain locally: with both a restricted local network and a dead CI, a change to the Zig sources currently cannot be verified anywhere.

What to check

Not diagnosable through the Actions API — it needs repository/organization settings:

1. Settings → Actions → General: is "Allow all actions" still selected, or has Actions been disabled for the repository?
2. Organization settings → Actions: an org-level policy can disable Actions for every repository at once.
3. Billing → spending limit: a exhausted included-minutes balance with a $0 spending limit stops GitHub-hosted runners from picking anything up, and it is silent.

Acceptance

• A push to main produces a workflow run again.
• ci.yml is run against current main and its result recorded — if it is red, that is triaged as its own issue.
• The conformance gate's red state as of 85fab4a9 is re-evaluated against current main.
• Something surfaces a prolonged absence of runs, so a silent three-month outage is not discovered by accident again.

Fresh evidence from the direct push of 0ae8024 to main on 2026-09-29: gh run list filtered to that exact commit returned an empty result, even though the commit adds a new dependency-manifests job to active ci.yml. The local acceptance checks passed, but GitHub created no workflow run at all. This further isolates the outage to repository or organization Actions settings/billing rather than a workflow trigger or YAML change.

Current API audit on 2026-10-19: repository Actions permissions report enabled=true and allowed_actions=all; the default workflow permission is read; ci.yml and conformance-gate.yml are registered active. gh run list still reports the newest workflow run at 2026-06-01T14:27:58Z, so pushes through current main have not restored execution. The organization Actions-policy endpoint returned HTTP 403 (requires org admin/actions-policy permission), so org policy/billing cannot be verified from this account. No CI run was started and no settings were changed; the issue remains open for an org/repo administrator to diagnose the external gate.