Files
pipelines/internal/author/skill/references/delivery.md
T
alan 607356702a web: comfortable phone density and clearer back control
Raise phone body/meta type, controls and dock targets to 44/56px, make the chat
back arrow a visible 44px control, and give the star/menu 44px hit areas without
covering the chat status. Keep the shipped skill free of personal device and
project capture paths.
2026-10-20 03:49:35 +01:00

32 lines
1.7 KiB
Markdown

# 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 device ownership and shared-work boundaries. A test-device
authorization does not authorize installation on a personal device. Delivery to a
personal device needs the user's explicit request; preserve app data and verify the
exact artifact. Use the project's supported capture helper for rendered evidence,
not a raw redirect. Verify the fixture connection before capturing, keep its owned
process alive until the required interactions finish, then stop it and await cleanup.