You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: six checks red on main (validate/deno, K9, gitleaks .adoc, rust-ci, governance linter, estate-audit) #137
Each gitleaks AsciiDoc finding is triaged in the fixing PR. A real secret is rotated and removed. A false positive is allowlisted by an exact fingerprint, not by a path glob.
Cargo check + clippy + fmt passes on main, and the fixing PR names the failing step.
The Governance linter finds its parser and duplicate-key checker at the pinned Standards revision.
estate-audit is green on main.
Each item is proven on a real main head SHA, with the conclusion success, not skipped.
Found while landing #136. #136 inherits these reds and does not cause them.
K9: the 98 clade configs and 4 layouts now carry magic_number = "K9!".
gitleaks .adoc: Secret Scanner is green.
rust-ci: the gossamer dependency is now feature-gated, and the fmt and clippy failures are fixed.
governance linter: green.
estate-audit: now a thin caller of the cicd-suite reusable.
All six were green on main at 9961333.
Hypatia and Scorecards later failed at job setup with invalid lockfile pin. That is a separate problem: GitHub's runner now enforces lockfiles inside the shared standards workflows. It is being fixed in #156.
Activity
fix(launcher): regenerate panll launcher with the XDG pid/log ladder (#…
ci: remove the gates #107/#108 left with nothing to test (owner decis…
ci: fix the root causes of main's red checks (stacked on #147) (#150)
hyperpolymath commentedon Oct 19, 2026
Fixed by #150, merged 2026-10-14 as
96a24db. Here is what happened to each of the six checks this issue listed:magic_number = "K9!".All six were green on
mainat9961333.Hypatia and Scorecards later failed at job setup with
invalid lockfile pin. That is a separate problem: GitHub's runner now enforces lockfiles inside the shared standards workflows. It is being fixed in #156.Generated by Claude Code