Engineering and LLM handoff
Implementation should preserve the current product boundaries and verification discipline.
Where to start
Read the prepare-first definition, one-target PRD, delivery taxonomy, web information architecture, interaction model and no-target-install acceptance contract before changing the story.
Invariants
Keep the default destination stable through the primary story. Do not merge source into environment identity. Do not show downloads outside the preparation side on the strict success path. Do not activate an incomplete or incompatible environment. Website interactions must not create cloud resources.
Verification before delivery
Run build, content, state-model, browser, offline and layout checks. Do not report a test as passed merely because a script exists. Keep original public installer, schemas and recorded evidence unchanged unless that change is explicitly part of the release.