Release-shape check c9663459: mechanical version/artifact legs PASS; release-notes standard needs correction before I can call the shape right. Please do not push on this receipt.
Measured: workspace version 0.70.0; first CHANGELOG heading [0.70.0] - 2026-09-13; previous 0.69.0-and-older body byte-identical; Cargo.lock diff exactly 14 first-party version pairs, no third-party changes. Worktree HEAD equals candidate. Executed its release spt.exe: spt 0.70.0. SHA256 spt 68d9f9312368e042c2bdb066a0815a72fac669ac2571c5e5de9aa64b521ae887, xtask de215d4a24ec0ee5a4a2e5057bc89c5605806d725efe10d9fac56f34486f7f41, both match. Candidate traceable check exit 0, 918/918, zero findings.
Two binding step-2 corrections, mirrored by regeneration in docs-site: (1) first Added bullet says 'your machine'; use 'the controller node' (impersonal voice). (2) Diagnostics is two mechanism-heavy bullets; collapse to one plain line under Internal, e.g. 'Improved diagnostic logging for attached sessions; refresh freezes and console pauses remain unresolved.' Retain appropriate evidence tags near that real section.
Range audit also surfaced 63cf4acd 'fix(io): observe successful hosted message injection'; please account for this rider in the notes or explicitly classify it internal/no end-user change, rather than silently omit it. The other fix/feat subjects map to the existing release bullets or diagnostics.
Separate full-handoff concern spotted in draft: shared-seam section says consumers 'to run in the golden', but runbook requires full affected consumer-crate execution on both OSes BEFORE handoff with last-run sha/receipts. A list of future golden consumers is not that artifact. No full intake/golden authorization; #297 and board dispositions remain separate holds.
Evidence: .spt/preserved/deployah-304-shape-c9663459/ (shape.diff, traceability.json). No source edits, rebuild, or push by me.