Repository navigation
One monitor, slice 2: one self-closing alert issue per failing gate, labelled with its owners (SCN-2026-008) - #570
Merged
Merged
Conversation
…labelled with its owners The deploy and the nightly each keep one issue per gate command, from the results the gates recorded: a failure opens or reopens it, a pass closes it. A run that failed outside any gate keeps one fallback issue per workflow. Replaces the deployment-failure and stale-evidence issues. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
SCN-Type: adaptive
SCN-Rationale: One monitor, slice 2: the deploy and the nightly keep one self-closing alert issue per failing gate, labelled with the owners the gate register names, in place of one deployment-failure issue and one stale-evidence issue.
SCN-Record: SCN-2026-008
SIA:
issues: writeandcontents: read, and the nightly alert dropspull-requests: read)Changed
scripts/gate-alerts.py(new). Reads the results the gates recorded (GATE_RESULTS_FILE) and, through_gates.stage_results, every gate the register lists for the given stages. One issue per gate command:[deploy|nightly] gate failing: <command>and comment with the run, its checks and their owners;Checks that share one command (the
reconcile.*invariants) pass or fail together, so they share one issue labelled with every owner they name. A run that failed while no gate failed opens[<context>] run failed outside any gate; the next successful run closes it. Issues carrygate-alertplus arole:*label per owner and are assigned to the repository owner.--dry-runprints the actions without calling GitHub..github/workflows/deploy-with-opa.yml.gate-results-pr,gate-results-deploy) even when it fails.notifybecomes Gate alerts: needs the test job too, runs on every main run that was not cancelled (pull requests never touch the issues), and calls the script over stages pr, pre-apply, post-apply and pre-publish. The queue watchdog's dependent-job list follows the rename..github/workflows/evidence-nightly.yml.gate-results-nightly).alertbecomes Gate alerts: it runs on every run that was not deliberately dropped, so passing gates close their issues. The published-evidence age report stays.docs/runbooks/evidence-sla-alarm.md. Points to the per-gate issues.tests/test_gate_alerts.py(new). A failing gate opens one issue with every owner; a pass closes it and unreported gates are left alone; a run that failed outside any gate opens the fallback and success closes it; each workflow keeps its own issues; a dry run calls nothing.Effect
After deploy, each deploy run on main and each nightly run opens, updates or closes
gate-alertissues. With today's results nothing opens: the post-deploy nightly's gates are all passing (21 checks under 5 commands), so the first runs only close. The old single "Deployment failing" and "Evidence nightly failed" issues are no longer updated.Verified
make checkpasses.ghis called with an argument list and no shell; issue titles come from the register'srunvalues, which its loader restricts toscripts/<name> [subcommand]; job results reach the step through the environment; actions pinned by SHA; the token is the job's own, with no new permission. No findings.Residual / needs human
Couldn't verify
Follow-ups noticed
🤖 Generated with Claude Code