launch's artefact declaration reserves an inert opt-in for the release-rendered site; site describes a shipped setup that already writes a workflow rendering the site from each published release

launch's artefact declaration reserves an inert opt-in for the release-rendered site; site describes a shipped setup that already writes a workflow rendering the site from each published release

A scope leakage (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/04-launch.md:35 — "reserves the release-rendered site's opt-in, read and not yet acted on"
• End B: .abcd/development/brief/04-surfaces/22-site.md:55 — "a workflow that renders the site from each published release with abcd's checksum- and attestation-verified binary"

04-launch.md says the artefact declaration's site key reserves the release-rendered site's opt-in, read and not yet acted on. 22-site.md describes a shipped setup verb that writes the composition declaration and a workflow rendering the site from each published release. The release-rendered site is therefore already acted on, and it is opted into through the site verb, not artefact.json. Two declarations claim the same opt-in, and the one launch names does nothing.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 280.