ci: re-verify main after merges on the zeta_reflection island (push trigger + required-by-test) - #639
Merged
Merged
Conversation
…rigger with paths filter); require push triggers by test telperion-zeta-reflection had no push trigger, so main was re-verified only by its weekly cron, and that cron never fired (GitHub dropped the 2026-09-23 04:41 UTC slot; gh run list -e schedule returns 0). Add push: branches: [main] with a paths filter scoped to the island (zeta_reflection/**, zero_free_bridge/lean/**, zeta_zero_localization/lean/zzl_core/**, the workflow itself). The weekly cron stays as a backstop. test_ci_push_triggers.py now REQUIRES a push-on-main trigger for every workflow unless it is in NO_PUSH_ALLOWED with a reason (only telperion-legacy-boxes, by the governance cost decision), fails on stale exemptions, and pins the zeta-reflection filter to the island. Checked: removing the trigger makes the test fail (2 failures). Governance decision by the peer session (owner of CI governance). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LMeoWeTz2Q3iSeLfqxfYo6
…les + RHInBoxT box glob); test checks coverage both ways (peer skeptic finding) The first cut covered 4 of RELEVANT's 5 alternatives: a merge touching e.g. zeta_zero_localization/lean/TuringBand.lean would not have re-verified main. The filter now lists the named top-level zzl modules and the RHInBoxT_1d4000000_3999999d4000000_* box family, and it is deliberately NOT a blanket lean/*.lean (27k AllZeros_h* band files there). The test derives the module list from RELEVANT (and asserts its three copies agree), requires every RELEVANT path to be covered by a push glob, and requires no push glob to admit a RELEVANT-rejected path. Negative checks: dropping TuringBand fails the coverage test, and adding lean/*.lean fails the not-broader test. NO_PUSH_ALLOWED now cites the ci-schedule-health watch (#640). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LMeoWeTz2Q3iSeLfqxfYo6
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.
Why
telperion-zeta-reflectionhad no push trigger (pull_request / workflow_dispatch / schedule only). So main was re-verified after merges only by its weekly cron, and that cron never fired: GitHub dropped the 2026-09-23 04:41 UTC slot, andgh run list -w telperion-zeta-reflection.yml -e schedulereturns 0. A cron can silently not run at all, which is worse than failing because it leaves no red mark.Change
push: branches: [main], with a paths filter scoped to the island:telperion/examples/zeta_reflection/**zero_free_bridge/lean/**zeta_zero_localization/lean/zzl_core/**test_ci_push_triggers.pynow requires a push-on-main trigger for every workflow unless it is listed inNO_PUSH_ALLOWEDwith a reason.telperion-legacy-boxesis exempt, by the governance cost decision (669 box certificates at about 5.3 core-hours, and nothing imports them).Decision by the CI-governance owner (peer session). The companion "schedule-only watch" lands in telperion-audit on their side. No Lean changes.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LMeoWeTz2Q3iSeLfqxfYo6