1.7 KiB
Delivery
The manager may build, verify, merge, deploy and install within the user's request. Do not repeatedly ask for steps already authorized. A draft-only or read-only request does not authorize publication, execution or deployment.
Source and evidence
Inspect actual source and diffs, run relevant tests and record exact results. A model summary, committed branch or successful merge is not proof of runtime behavior. Missing or partial diff capture must be reported as incomplete. With delivery=true, the stage returns a clean candidate and the server checks and lands it; direct recovery can complete a reviewed merge without another pipeline.
Keep artifacts under the supplied run/stage artifact directory. Mark unverified builds as WIP. Verify any download URL serves the real bytes before reporting it. Do not imply that mocked fixtures or resized-device captures prove live-provider behavior or a real foldable's posture behavior.
Runtime and devices
Wait for shared work to quiesce before restarting its service. Back up durable state, preserve endpoint/configuration, verify the new runtime identity and keep a rollback path. Do not wipe data or remove credentials to repair deployment.
Respect target leases and the user's device boundaries. A test-device authorization
does not authorize use of the personal phone. Installation on the personal Fold
requires the user's delivery request; preserve app data and verify the exact APK.
Use android/scripts/capture_png.sh -s SERIAL PATH for app captures, not a raw
binary exec-out redirect. Verify the fixture connection before capturing and keep
its owned process alive until all required interactions finish; then stop and await it.