Skip to content

Rehearse main's reused-proof build on every pull request - #102

Merged
github-actions[bot] merged 1 commit into
mainfrom
claude/project-thread-jbqzew
Nov 15, 2026
Merged

github-actions[bot] merged 1 commit into
mainfrom
claude/project-thread-jbqzew

Conversation

@afflom

@afflom afflom commented Nov 15, 2026

Copy link
Copy Markdown
Owner

A pull request always proves in full, so the holo build that main runs when it reuses the PR's proof never ran before merge. That is how #94 passed its gates and then blocked main's deploy (PP3018, fixed in #101).

The page step now defines one build_holo function, used both by main's reuse branch and by a rehearsal. On a pull request, the rehearsal runs that build on a copy of the tree in the background while the proof runs, and the step fails if it fails. Locally in the locked SDK, the rehearsal took 4.4 minutes, against a proof of 16 to 25, so it adds no wall time.


Generated by Claude Code

A pull request proves in full, so the holo build main runs when it reuses
that proof never ran before merge: #94 passed its gates and then blocked
main's deploy (PP3018). The page step now runs that same build (one
build_holo function for both) on a copy of the tree alongside the proof,
and fails the pull request if it fails. It runs in parallel, so it adds no
wall time (about 4 minutes against a 20-minute proof).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@github-actions
github-actions Bot enabled auto-merge November 15, 2026 06:00
@github-actions
github-actions Bot merged commit b0fe814 into main Nov 15, 2026
7 checks passed
afflom pushed a commit that referenced this pull request Nov 15, 2026
Since #89 a main run published only if its commit was still main's head.
When merges come faster than a run, every run finds main moved on and none
publishes: nothing deployed from #93 at 04:58Z through #102 at 06:25Z
although five runs passed their gates. tools/pages/newer.sh instead asks
whether the live page already holds this commit. The build job asks it to
decide whether to publish, and the publish job, one at a time, asks again
before it deploys, so an older run never replaces a newer page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3LuNYtPDBa4FbSEQUZ
@github-actions

Copy link
Copy Markdown
Contributor

Live: this change is on the published page, as main 83d079ddd8f9a3c2b0bce781cfab3c21b0053ef1.

The publish job opened the published page in a fresh Chromium and its live checks passed (PG-01, PD-01, PD-02): https://github.com/afflom/me/actions/runs/43687588120

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.

2 participants