chore: persist NightOwl ruleset rollout artifacts - #81
Merged
Conversation
Adds postscript to the required-workflows plan documenting the 2026-04-30 attempt: paused after multiple failure modes the original plan didn't anticipate (Team-plan downgrades evaluate; cleanup-PR chicken-and-egg; --admin doesn't bypass rulesets; scope expansion doesn't fire workflows on existing PRs). Captures empirical findings and open questions. Persists three operational scripts from /tmp: - nightowl-ruleset-setup.sh: Phase 1+2 setup (works) - nightowl-restore-blocking-review.sh: emergency restore that put per-repo files back after the cleanup attempt left repos uncovered (works) - nightowl-ruleset-rollout.sh.broken: Phase 4 rollout script with known re-arm bug (step 1 unconditionally sets enforcement=active, overrides intentional disables). Saved with .broken suffix so it cannot be accidentally re-run and so shell-lint hooks ignore it. Header inside documents the bug and the fix needed before reuse. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
<!-- claude-blocking-review sha=aebf48469e2bb3da5f136050ac36a737d15b1cd2 run=25198930138 --> No changes to workflow files, verdict parsing, allowed-tools, or the escape-hatch path. The diff is limited to a documentation postscript and two operational bash scripts (nightowl-restore-blocking-review.sh and nightowl-ruleset-rollout.sh.broken). The .broken file is intentionally non-executable. No shell-injection vectors, no hardcoded credentials, no reliability regression to the CI pipeline. VERDICT: PASS |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/plans/2026-04-30-required-workflows-nightowlstudiollc.mddocumenting today's rollout attempt and why it was paused. Captures empirical findings (Team-plan downgrades evaluate; cleanup-PR chicken-and-egg; --admin doesn't bypass rulesets; scope expansion doesn't fire workflows on existing PRs) and the open questions to answer before any future re-attempt./tmpso they survive next reboot:nightowl-ruleset-setup.sh— Phase 1+2 setup (works)nightowl-restore-blocking-review.sh— emergency restore (works)nightowl-ruleset-rollout.sh.broken— Phase 4 rollout with known re-arm bug. The.brokensuffix means it can't be accidentally executed and shell-lint hooks ignore it. Header inside documents the bug and the fix needed before reuse.Test plan
shellcheck -S info🤖 Generated with Claude Code