Repository navigation
fix(ci): admit exact panic-attack subjects to lock recovery - #86
Conversation
Add panic-attack as the fifth explicit repository in both the dispatch and generator admission boundaries. Keep the fixed Hypatia push subject, read-only token, canonical tool/source pins and candidate-only behavior. Extend wrong-owner, suffix, legacy-alias and malformed-revision controls; all 29 local boundary groups and workflow actionlint pass.
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. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 11 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
|
Why
panic-attack PR258 repairs the scanner's input-coverage contract. Its hosted checks also exposed three inherited reusable callers that fail with zero jobs at an old standards owner/ref. Those callers now point to the reviewed canonical source, so their native actions.lock needs the existing official regeneration route.
The recovery runner currently admits four repositories. This adds only
hyperpolymath/panic-attackas the fifth exact subject, following the merged #85 pattern.Changes
panic-attackeralias, and missing/floating/malformed revisions.The default and fixed push subject remain Hypatia. The canonical standards
d3e4b485…regeneration function, verified official v0.2.0 binary identity, read-only token, separated acquisition job and candidate-only output remain unchanged. No subject code is executed and no writeback or Actions-policy permission is added.Validation
From current main
b81ec53c8207bc5b8a8bd8d828834491e36f745a:bash tests/actions-lock-recovery.sh: 29 boundary groups passed (was 27; both the workflow and generator now admit the fifth exact subject).These controls are not evidence that the real generator has run on panic-attack. After review/merge, dispatch against the then-current immutable PR258 head, verify the candidate receipt and digests, apply only with an expected-head check, and require genuine target startup/governance results. The current proposed subject is
ff278a373b523c69f93e99590112f5fac205b083; if it moves, use the newly reviewed exact head.