Skip to content

Main's publish run reuses the merged pull request's proof again - #183

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

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

Conversation

@afflom

@afflom afflom commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Why

Main's publish run for #162 (run 43914340317 on da96880) was cancelled at the job's 75-minute limit with nothing failing, so nothing was published. Thirty of those minutes were "Build and verify the holo through the locked SDK", proving in full, and the step "On main, the proof the merged pull request's page build kept" was skipped.

That step and the proof reuse behind it are written for a push to main. Since the merge train merges with the workflow's own token, no push run starts; deploy-watch.yml dispatches pages.yml on main instead, so main's publish runs as workflow_dispatch. The step's condition names only push, and the Justfile's app recipe reuses a kept proof only for pull_request:*, merge_group:* and push:refs/heads/main. So since the train took over, every publish has proved in full.

What changes

In the model app/specs/pipeline/workflows/pages.yml.json, rendered again to .github/workflows/pages.yml:

  • The step that fetches the merged pull request's kept proof also runs on a dispatched run on main.
  • PRISM_PROOF_EVENT names a dispatch started by the pipeline (github.actor == 'github-actions[bot]') as the push it stands for. A run a person starts by hand is still workflow_dispatch and still proves in full, as the Justfile says a manual run must.

What is not changed: the Justfile, and the read-time check. xtask proof-reuse still reuses a proof only if its attestation binds this checkout's model, the SDK image, Lean and every input file; anything else proves in full. A batch that merges two pull requests which both change proof inputs will still prove in full on main, since neither pull request's proof binds the merged tree.

This touches a deliberate guard (a manual run proves in full), so it wants an owner's eye: the reading here is that the guard is about runs a person starts, and the pipeline's dispatch is the push event the train's token cannot produce.

Checks

  • tools/generators/run.sh --check (GN-01); the rendered workflow parses as YAML.
  • No audit pins this text: xtask and the conformance tests read pages.yml for other needles only (checked by search). cargo test -p repo-conformance was still running here when this was opened.

Not run: the change itself. It only takes effect on main's own publish run, so the first publish after it merges is the test; I will read that run's proof step and say what it did.


Generated by Claude Code

…equest's proof

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

Copy link
Copy Markdown
Contributor

Merge train notice: the merge train merges this pull request once it is green on current main; don't enable auto-merge.


Generated by Claude Code

@github-actions
github-actions Bot merged commit 0c2b4e9 into main Nov 16, 2026
7 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

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/43977249372

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