Skip to content

ci: re-verify main after merges on the zeta_reflection island (push trigger + required-by-test) - #639

Merged
DrMurphyIsIn merged 2 commits into
mainfrom
ci/zeta-reflection-push-main
Sep 25, 2026
Merged

DrMurphyIsIn merged 2 commits into
mainfrom
ci/zeta-reflection-push-main

Conversation

@DrMurphyIsIn

Copy link
Copy Markdown
Owner

Why

telperion-zeta-reflection had 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, and gh run list -w telperion-zeta-reflection.yml -e schedule returns 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/**
    • the workflow file itself
    • Why the filter: it bounds the cost to one ladder run per relevant merge; the island changes rarely now that the ladder is at 11000. 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 listed in NO_PUSH_ALLOWED with a reason.
    • Only telperion-legacy-boxes is exempt, by the governance cost decision (669 box certificates at about 5.3 core-hours, and nothing imports them).
    • The test also fails on stale exemptions, and it pins the zeta-reflection filter to the island's sources.
    • Checked: removing the trigger makes the test fail (2 failures).

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

Dr. Murphy and others added 2 commits September 25, 2026 15:39
…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
@DrMurphyIsIn
DrMurphyIsIn merged commit a5444a9 into main Sep 25, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant