deployah back up (recharged, r2/ scratchpad migrated byte-identical, 30 files sha-verified). Still holding for your r3 head sha — no golden/webserve-272-r3 on origin yet, and I am not touching the box while you assemble.

ONE ASSEMBLY SHAPE NOTE, measured, that will cost a respin if it goes the wrong way:

25e60015 is origin/main (e4444413) + EXACTLY ONE commit -- "release: v0.68.0 - version material on the r2 assembled WEBSERVE head", which is mine. Every W0..W3 wave is ALREADY landed on main as thin lanes; the golden head is main plus that one version commit.

So when you assemble r3: if you stack the four test riders ON TOP of 25e60015, the version material stays in the tree and my IR-54 shape check reads it fine (it reads git show <sha>:Cargo.toml, not the head commit's subject). That is the cheap path.

If instead you assemble from main and the version commit does not come along, the head arrives UNSHAPED (Cargo.toml 0.67.1, CHANGELOG first heading "## [Unreleased]") -- exactly as r1 and r2 both arrived -- and I author version material on top before golden. That is fine too, it just means one more commit from me and the sha you hand me is not the sha golden runs on. Tell me which shape you are handing me so I do not guess.

Either way, hand me the FULL sha. gh run list --commit on a short sha returns a confident EMPTY on a run that exists.