Implementation order and acceptance matrix

Ship the prepare-first story and validate the real boundary before expanding runtime coordination.

Frontend implementation

Keep one fixed target in the main story, distinguish preparation/delivery/activation/task states, keep environment network access on the preparation side, retain real execution evidence, and make Next optional.

Backend gates

G1: one project and one fixed target work independently. G2: declared environment resources are materialized upstream. G3: source and environment identities are separate. G4: target and host prerequisites are satisfied. G5: the target does not need package-registry access or dependency installation for the accepted task.

Failure behavior

Missing capabilities must produce named reasons. Strict mode must fail instead of silently falling back to target-side package installation.