Repository navigation
ci(estate-audit): call cicd-suite's reusable audit; skip panic-attack's registry - #158
Conversation
…'s registry Replace the 26-step copy of the estate audit with a thin caller of hyperpolymath/cicd-suite's reusable workflow, pinned at b17ec1a (#55). The copy froze at cicd-suite@5a10b72 through actions.lock, so upstream gate fixes never arrived here. The caller passes manifest-deed-paths-ignore (cicd-suite #51): the DEED validator's defaults plus audits/assail-classifications.a2ml. panic-attack reads that suppression registry from the fixed path. It is not a DEED manifest, and it kept the manifests check red. Triggers stay PERIODIC (push to main, weekly, dispatch; never on pull_request). The caller is de-onboarded from actions.lock with cicd-suite/scripts/deonboard-estate-audit.sh. An onboarded cross-repo reusable call startup-fails with zero jobs. The script pruned only what the old copy reached: cicd-suite@main, deed-ecosystem@f9d999b and k9-ecosystem@2155aa2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Kjdf4Mf4Z41bNQh2TrsEp9
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This failure isn't caused by this PR.
No fix exists yet. It looks like a change in how GitHub verifies lock entries at run time, possibly tied to gh-actions-lock v0.2.0 (released 2026-10-12). It is being investigated separately, and the fix most likely belongs in Generated by Claude Code |
|
Add Carrot credits or activate Agent usage billing to use Autofix |
|
✅ Coding Agent task started: View task and status The task will inspect the CI failures, validate its fix, and commit the fix to this branch automatically.
⏭️ Checks skipped: 2 · already failing on `main` (not caused by this PR)
|
|
@coderabbitai please don't push a CI fix to this branch. These 44 failures aren't caused by this PR. Every one of them dies in "Set up job" before any step runs, with Most of these checks don't show as red on
The cause is upstream: a change in GitHub's runtime lockfile verification, probably related to gh-actions-lock v0.2.0. That's being investigated separately. Editing Generated by Claude Code |
|
Tip For best results, initiate chat on the files or code changes. @hyperpolymath Understood. I will not initiate another CI fix for this branch. Thanks for the clarification. I cannot cancel the already-started coding task from this chat. That task is not confirmed stopped. Please check the task page for a cancellation control. Your evidence distinguishes these setup failures from regressions in ✏️ Learnings added
You are interacting with an AI system. |
Rate Limit Exceeded
|
Why
Central Estate CI/CD Audithas been red on main. There were two causes:manifestsfails onaudits/assail-classifications.a2ml. That file is panic-attack's suppression registry, which panic-attack reads from that fixed path. It is not a DEED manifest, and the validator had no way to skip it. feat(manifest-check): per-validator ignore lists, forwarded by the reusable audit cicd-suite#51 added that way, and chore(ci): repin estate audit composites to #54 (follow-up to #51) cicd-suite#55 made it live.cicd-suite@5a10b72throughactions.lock, so gate fixes made upstream never arrived here.What
.github/workflows/main-estate-audit.ymlhyperpolymath/cicd-suite/.github/workflows/main-estate-audit.yml@b17ec1a…(chore(governance): adopt estate-standardization wave + 2026-06-12 checkpoint #55's merge commit), fromtemplates/estate-audit-caller.yml.manifest-deed-paths-ignore: the DEED validator's seven defaults, thenaudits/assail-classifications.a2ml. A list replaces the defaults, so they have to be repeated.pull_request, so this PR's own checks don't run it..github/workflows/actions.lockcicd-suite/scripts/deonboard-estate-audit.sh. An onboarded cross-repo reusable call startup-fails with zero jobs.cicd-suite@main,deed-ecosystem@f9d999bandk9-ecosystem@2155aa2.Verification
workflows:ref and nesteduses:resolves to a record.b17ec1af1bbf097d77a58ac3363c4cf5db4d7f4ais on cicd-suite main.Not in this PR
From 18 Oct, scheduled runs of Rust CI, Squabble, Scorecards and Hypatia fail before any step runs, with
invalid lockfile pin. That is unrelated to this change and is being looked at separately.Generated by Claude Code