Board: claiming the site for one publish that carries a three-day-old wrong picture off the front page - #504
Merged
Merged
Conversation
… wrong picture off the front page Tony, told that the live front page draws the raw-brightness bypass THROUGH the difference-of-Gaussian bank: *"then do the 5 minute deploy"*. The claim records both authorities the previous deployer said were needed -- his words in session, and DEPLOY_HOLD.md re-read at claim time rather than trusted from earlier in the session, because that deployer found `held: no` alone was refused and thought the refusal right. Publishing `caeef0c`, 111 commits past the live build. The figure fix (#480, draughtsman re-vendored at 3762f4b) is verified in the BUILT payload rather than the source: the `mean -> concat` edge runs below the bank's box, and `mean -> dog` is separate. The other 16 commits touching served bytes are all one file -- the viewer -- and they are the MAHICE build-out, so what is live today is the viewer whose judging step cannot be opened. Written from a worktree that is not the build, per the trap this board already records: merge_when_green reaps the claim's worktree and would take a built site/ with it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
syncytium2
added a commit
that referenced
this pull request
Sep 9, 2026
Releases the claim #504 took. A claim cannot retire itself in the PR it rides in, which is why this is a second commit and not an edit to that one. Published `3cb89fd`, Version ID ab3cc81d-1ed5-415b-ada8-14deb77574ce, 7 of 8 assets changed. Verified against the live edge rather than the build, including reading the corrected figure off the served HTML with curl: the bypass runs below the difference-of-Gaussian bank instead of through it, for the first time since 2026-09-02. Two things recorded because a later deployer needs them and neither is flattering. The claim PR was pushed and open but had NOT merged to main when the deploy ran -- CI is about thirteen minutes and the instruction was a five-minute deploy. Nothing collided and no other session was deploying, but for that window the claim lived on origin and not in the file a starting session reads. Written down rather than smoothed over; if it recurs, landing a claim should not have to wait on a full CI matrix. And main moved under the preflight: #503 merged between the claim and the build, so the HEAD == origin/main check failed, the checkout was fast-forwarded and the build re-run. The published stamp is therefore 3cb89fd and not the caeef0c the claim block named. That check exists for exactly this and it earned its keep today. Co-authored-by: richard defazio <defazio@umich.edu> Co-authored-by: Claude Opus 5 (1M context) <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
2 participants
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.
Tony, told that the live front page draws the raw-brightness bypass through the
difference-of-Gaussian bank: "then do the 5 minute deploy".
Publishing
caeef0c, 111 commits past the live build at7208e44(2026-09-02). Two thingsa reader sees:
3762f4b.Verified in the built payload rather than the source: in
site/index.htmlthemean → concatedge runs at y=196, below the bank's y=16–164 box, andmean → dogis aseparate edge at y=90.
raster_viewer.html. What is live today is the viewer whose judging step cannot be openedat all, whose confirm tool and raster show different recordings, and whose review does not
survive a reload.
Checked first:
build_site.pyclean at 3426 KB / 8 assets;test_site_coherence,test_site_staleness,test_architecture_diagram_is_current,test_svg_labels— 70 passed.Claim written from a worktree that is not the build, per the trap this board already
records:
merge_when_green.shreaps the claim's worktree and would take a builtsite/with it. Release is a separate commit.
🤖 Generated with Claude Code