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
A sweep of every PR merged into main on 2026-08-24 (UTC), classifying each one's latest review verdict at merge time
(via check-pr-fully-clean.py's classify_verdict, then hand-confirming each flagged comment's last ### Verdict heading),
found that #645 reverted only the #622-#633 batch.
Seven other merges from the same day lacked a clean review verdict and remain on main:
Merged with no review verdict at all
Each of these edits workflow files, so the claude-code-action guard posted
"No review ran --- this PR edits .github/workflows/..." and no reviewer ever produced a verdict.
No self-review fallback (per self-review-fallback.md) was posted on any of them before merge.
Merged over a standing Needs-more-work verdict (borderline)
fix(workflows): remove invalid timeout-minutes on caller jobs (#582) #583 (merged 00:28:35): the last Claude verdict before merge
(comment 5382332775, 2026-08-22)
was Needs more work --- the residual finding being seven other workflows carrying the same pre-existing bug, out of this PR's diff.
A local Antigravity review approved on 08-23 and a local adversarial review filed the remaining findings as issues (a Defer),
but no subsequent clean Claude verdict exists.
The revert PR itself
revert: revert PRs #622 through #633 #645 (merged 23:18:54) also merged with no review (same workflow-edit guard, merged 5 min after opening).
It is the remediation --- a pure revert restoring main to 173e473 --- so its risk profile differs,
but it is noted here for completeness.
Suggested disposition
Either revert these as #645 did for #622-#633, or run a retroactive review round on each
(a workflow_dispatch review, or the self-review fallback that was owed at merge time)
and fix or file whatever it finds.
The workflow-edit guard means these PRs could never get an in-PR Claude review by construction,
which makes the self-review fallback the mandatory step that was skipped.
Sweep performed 2026-08-24 ~16:30 PT; sibling ai-config findings are tracked in Morrison-Lab/ai-config#2174 and a parallel ai-config issue.
A sweep of every PR merged into
mainon 2026-08-24 (UTC), classifying each one's latest review verdict at merge time(via
check-pr-fully-clean.py'sclassify_verdict, then hand-confirming each flagged comment's last### Verdictheading),found that #645 reverted only the #622-#633 batch.
Seven other merges from the same day lacked a clean review verdict and remain on
main:Merged with no review verdict at all
Each of these edits workflow files, so the
claude-code-actionguard posted"No review ran --- this PR edits
.github/workflows/..." and no reviewer ever produced a verdict.No self-review fallback (per
self-review-fallback.md) was posted on any of them before merge.Merged over a standing Needs-more-work verdict (borderline)
(comment 5382332775, 2026-08-22)
was Needs more work --- the residual finding being seven other workflows carrying the same pre-existing bug, out of this PR's diff.
A local Antigravity review approved on 08-23 and a local adversarial review filed the remaining findings as issues (a Defer),
but no subsequent clean Claude verdict exists.
The revert PR itself
It is the remediation --- a pure revert restoring
mainto 173e473 --- so its risk profile differs,but it is noted here for completeness.
Suggested disposition
Either revert these as #645 did for #622-#633, or run a retroactive review round on each
(a
workflow_dispatchreview, or the self-review fallback that was owed at merge time)and fix or file whatever it finds.
The workflow-edit guard means these PRs could never get an in-PR Claude review by construction,
which makes the self-review fallback the mandatory step that was skipped.
Sweep performed 2026-08-24 ~16:30 PT; sibling ai-config findings are tracked in Morrison-Lab/ai-config#2174 and a parallel ai-config issue.