Repository navigation
ci: repair main's failing checks (standards pins, DEED registry, scorecard perms, Hypatia SARIF) - #402
ci: repair main's failing checks (standards pins, DEED registry, scorecard perms, Hypatia SARIF)#402hyperpolymath wants to merge 5 commits into
Conversation
…0604136 governance.yml, scorecard.yml and secret-scanner.yml died on every run with conclusion=failure, 0 jobs and name == path. Two causes, both cured here by the estate's own tooling (standards scripts/propagate-workflow-pins.sh --fix, which calls scripts/relock-standards-pin.sh; no hand edits): 1. At the old pins (da2c748a, 74d2f66f) standards' own actions.lock keyed actions/checkout@3d3c42e5 with ref: '3d3c42e5...' (the SHA repeated). The runner refuses that record ("invalid lockfile pin") in every caller. Standards HEAD records ref: 'v7.0.1'. 2. GitHub does not follow the standards transfer for job-level `uses:`, so hyperpolymath/standards/... never resolves. Moved to the canonical owner metadatastician. actions.lock gains the metadatastician/standards@c0604136 caller-side record (nested uses = the union of the called reusables' actions) and the leaf records it needs, copied from standards' lock at that commit. check-lock-pin-contract.sh exempts that one record as a reusable edge. Needs metadatastician/standards on the Actions allow-list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm
…s deed Dogfood Gate / "Validate DEED manifests" failed on main with audits/assail-classifications.a2ml: Missing required identity field That file was also inert. Its 14 entries used a `- suppression:` YAML dialect, and panic-attack's legacy reader only parses `(classification ...)` s-expressions, so nothing was ever suppressed. Every entry carried the same generic "Automated estate triage" text, not an audit of the file. Replaced with audits/assail-classifications_praxis.deed, the registry path panic-attack reads first (src/assail/classifications.rs DEED_PATH), in the canonical form: SPDX header, :schema-version, :canonical-name, :beholding-chora (hyperpolymath estate chora), :profile assail-classifications, and ZERO classification clauses. Behaviour is unchanged: nothing was suppressed before and nothing is suppressed now. The 14 candidates are kept as comments marked unreviewed and not active. Verified locally: - metadatastician/standards 1-formats/deed/tools/deed_lint.js: OK (the old file's content fails it: no SPDX header) - deed-ecosystem validate-action (fedffb3c, the locked commit): 23 files, 0 errors (was 1) A2ML is retired for new content. This removes one .a2ml and adds no new one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm
The caller job's permissions block replaces the workflow-level read-all. scorecard-reusable.yml at c0604136 has its `scorecard` job request actions: read, which the caller did not grant, so GitHub would reject the workflow at parse time. Checked caller-grants >= callee-requests for all three standards callers. Before this change, scorecard failed the check; after it, all three pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm
On main the scan job failed at erlef/setup-beam (ImageOS ubuntu26 is unknown to v1.24.0), so the converter never ran. The always() upload step then added a second, misleading error: "Path does not exist: hypatia.sarif". With a hashFiles guard the job still fails, now only on its real cause. A broken converter is still a failed step, so no silent pass is possible. This does NOT fix the scan itself. That needs erlef/setup-beam v1.24.1 (maps ubuntu26 -> ubuntu-26.04; hex.pm has OTP-27.3.4.9 and Elixir 1.18.6-otp-27 builds for it) plus a gh actions-lock regeneration, which this session could not run. See the PR's blocker list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
SonarCloud flagged githubactions:S7635 ("Only pass required secrets") on
the scorecard caller in this PR. scorecard-reusable.yml at c0604136
declares no workflow_call secrets and references none (it uses only
github.token), so `secrets: inherit` handed it every repository secret
for nothing. Removing it changes no behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm
|
CI status on
Generated by Claude Code |
|
SonarQube ( That endpoint returns 200 without a token and 403 with an invalid one, so the Generated by Claude Code |
|
|
Governance and Secret Scanner moved from The remaining
Fix: run Generated by Claude Code |



Summary
This fixes the root causes of most of
main's (9ef24aa) red checks. It also lists what this PR cannot make green, and why. Every claim below was reproduced locally againstmain, then shown passing on this branch, wherever it could run outside GitHub.Changes
governance.yml,secret-scanner.yml,scorecard.yml: failure, 0 jobs, name == pathda2c748a,74d2f66f), standards' ownactions.lockkeysactions/checkout@3d3c42e5…withref: '3d3c42e5…'. That is a self-SHA leaf, and the runner refuses it as an "invalid lockfile pin" (the same error the Dependabot PRs show). (2) Job-leveluses:does not follow the standards transfer, sohyperpolymath/standards/…does not resolve.metadatastician/standards@c0604136(standards HEAD, which hasref: 'v7.0.1') using standards' ownpropagate-workflow-pins.sh --fix, which callsrelock-standards-pin.sh. No hand edits toactions.lock.scorecard.ymlafter re-pinscorecard-reusable.yml@c0604136has itsscorecardjob requestactions: read. The caller's job-levelpermissions:replacesread-all, so GitHub would reject the workflow.actions: read. A caller-grants ≥ callee-requests check fails before this change and passes after it.audits/assail-classifications.a2mlhas no identity or version. The file was also inert: panic-attack's legacy reader only parses(classification …)s-expressions, and these 14 entries used a- suppression:YAML form.audits/assail-classifications_praxis.deed, the path panic-attack reads first. It has zero active classifications, so behaviour is unchanged (measured below). The 14 boilerplate candidates are kept as comments marked unreviewed and not active.Path does not exist: hypatia.sarifalways()upload still fired.hashFiles('hypatia.sarif') != ''. The job still fails, now only on its real cause.❌ Blockers this PR does not clear
erlef/setup-beam@v1.24.0cannot mapImageOS=ubuntu26. v1.24.1 adds it (ubuntu26 → ubuntu-26.04), and hex.pm publishes OTP-27.3.4.9 and Elixir v1.18.6-otp-27 builds for 26.04. The lock record must be regenerated bygh actions-lock. This session cannot run it: the tool needs the GitHub REST API forerlef/setup-beamand the other actions in that workflow, and the session's GitHub access only covers repositories with credentials attached. I did not hand-write the record. To finish it: change.github/workflows/hypatia-scan.ymltoerlef/setup-beam@v1.24.1, then rungh actions-lock .github/workflows/hypatia-scan.yml.Actions lockfile verify.check-lock-pin-contract.shreports 42 violations (canon rule 10: lock keys must be SHA-pinned). The count is identical onmainand on this branch, so the change didn't cause it. It was hidden while governance died at startup. The same root cause produces 31 of SonarCloud's 79 new-code vulnerabilities (githubactions:S7637). One fix clears both, and Claude/create claude md 013mf sv2x31y e2 dtls pz no r3 #1 too: inline-SHA-pin everyuses:(@<sha> # vX.Y.Z), then run the estate repair ordergh actions-lock→relock-sha-keys.sh→complete-job-refs.sh→close-lock.sh→prune-stale.sh. This needs the API access described in Claude/create claude md 013mf sv2x31y e2 dtls pz no r3 #1. Other governance jobs (no-new-a2ml,language-policy,deed-conformanceand so on) have never run here, and I have not simulated them.check-lock-sync.shreports orphan dependency recordstrufflehog@v3.93.8andgitleaks/gitleaks-action@v2.3.9, identical onmain.prune-stale.shonly prunes workflow entries. The repair order in chore(deps): Bump tracing-subscriber from 0.3.20 to 0.3.22 in /components/core #2 removes these.metadatastician/standards. If the allow-list only admitshyperpolymath/*, these three workflows willstartup_failure. Fix withwiden-actions-allowlist.sh.SonarCloud / SonarQube (report only, nothing disabled)
build.yml): token or config problem. The scanner dies onGET api.sonarcloud.io/analysis/jres→ HTTP 403. Measured: that endpoint returns 200 anonymously and 403 with an invalid bearer token, so theSONAR_TOKENsecret is invalid, expired or revoked. Regenerate it in SonarCloud and update the repository secret.ERRORonnew_security_rating = 3 > 1(new-code window since 2026-07-01). There are 79 open vulnerabilities on new code: 75 MAJOR and 4 MINOR. 31 aregithubactions:S7637(see blocker chore(deps): Bump tracing-subscriber from 0.3.20 to 0.3.22 in /components/core #2). 13 areshell:S6505/S6506(installs without--ignore-scripts, curl without HTTPS-only redirects). The rest are docker/text/web rules. These need code changes, not configuration.Dependabot
Once
mainis green I will tell you before commenting·@·d·ependabot r·ecreateon PRs #380, #381, #382 and #387. I have not commented yet.RSR Quality Checklist
Required
unsafeblocks.envfilesTesting (each reproduced on
main, then shown passing on this branch)deed-ecosystem/validate-action/validate-deed.shat the lockedfedffb3c: main 1 error (assail-classifications.a2ml: Missing required identity field), branch 0 errors (23 files).metadatastician/standards 1-formats/deed/tools/deed_lint.js(bun): new deedOK. Negative control: the old file's content fails (deed must begin with at least one SPDX header line).--self-testOK.hyperpolymath/panic-attack@7b9f145; it reads the deed registry strictly):assailon this branch exits 0. Negative control: the same tree with:profile wrong-profileexits 1 withmalformed classification registry … invalid :profile. Behaviour unchanged: the weak-point sets (category, location, suppressed) fromassailonmainand on this branch are identical (4 findings, 4 suppressed by the built-in rules, 0 by the registry, before and after).propagate-workflow-pins.shaudit: 3×BEHIND. After--fix:RELOCKED.check-lock-pin-contract.shexempts the new record as a reusable edge.FAILbefore the perms commit, all three pass after.actionlintv1.7.7: clean on all touched workflows.🤖 Generated with Claude Code
https://claude.ai/code/session_01J4QvDjkNc8Zno9wCLe72sm