skill: I said master was green after reading two of sixty-three workflows

[gHashTag]

Refs #3316.

Twice in one night a report of mine ended with master зелёный, naming two workflows. Both readings were true; the sentence was not. Measured properly, latest run on master for every active workflow:

success	40
failure	11
never ran on master	12

Among the eleven is Issue Gate, which supplies check-linked-issue — one of the four required contexts.

Two errors, and the second is the one worth keeping. The sample was the workflows I had touched — the most available evidence and the least representative. And the obvious wider read is still a window: gh run list --branch master --limit 100 returned only 22 distinct workflows of the 63; the other 41 had not run recently enough to appear, and a workflow that has not run is not one that passed. The population lives in /actions/workflows, asked once per id — which also surfaces the third answer a window cannot express, the 12 that have never run at all.

The correction was not self-generated: a neighbour's issue titled "Every workflow red on master" could not both be true and leave my sentence standing.

Spooled with tri skill add (#3321's mechanism), so it takes its number at fold time rather than racing another branch for one. And the push of this very branch was refused by the gate added in #3305 — the range had no docs/now entry — which is the first time that gate has caught its own author.

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.

[github-actions]

PR Dashboard

Generated at: 2026-09-05 18:30:38 UTC

• skill: I said master was green after reading two of sixty-three workflows #3322 skill: I said master was green after reading two of sixty-three workflows | Created: 2026-09-05 | Updated: 2026-09-05 | 20 failing / 27 total
• compiler: two frozen tests get the anchor their region needed #3317 compiler: two frozen tests get the anchor their region needed | Created: 2026-09-05 | Updated: 2026-09-05 | 0 failing / 38 total
• ci: zero checks is not zero failures, on the path that merges #3314 ci: zero checks is not zero failures, on the path that merges | Created: 2026-09-05 | Updated: 2026-09-05 | 0 failing / 28 total
• chore(ci)(deps): bump actions/attest-build-provenance from 1 to 4 #3001 chore(ci)(deps): bump actions/attest-build-provenance from 1 to 4 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• chore(ci)(deps): bump softprops/action-gh-release from 2 to 3 #3000 chore(ci)(deps): bump softprops/action-gh-release from 2 to 3 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• chore(ci)(deps): bump github/codeql-action from 3 to 4 #2999 chore(ci)(deps): bump github/codeql-action from 3 to 4 | Created: 2026-09-01 | Updated: 2026-09-05 | 3 failing / 30 total
• Land the formal verification harness on master (it has never run) #2727 Land the formal verification harness on master (it has never run) | Created: 2026-08-27 | Updated: 2026-09-05 | 5 failing / 24 total
• chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 #2693 chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 #2692 chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 33 total
• chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 #2691 chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 #2690 chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 #2689 chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	13
PRs with Failing Checks	10
PRs with All Checks Green	3
READY	2
FAILING	10
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=ffccfa1a71cf != manifest seal=87e5cbd3ad94.
  The committed NMSE numbers were certified against an older compiler.rs.
  Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).