Delivery
Set the authority, artifact, and evidence boundaries for agent-assisted deployment and operational checks.
Separate preparation, deployment, and observation
Delivery concerns preparing a checked artifact, authorizing external effects, and observing the resulting application. The current smoothie-deployment skill covers the standalone Smoothie Starter's Cloudflare Worker and static assets profile. It does not qualify Interactive Agent, Durable Worker, SSR, databases, queues, additional bindings, or other hosting providers. Follow Build and deployment for the owning command sequence and artifact lifecycle.
Supply the application, exact account ID and Worker name, permission to create or replace that target, and the checks required before and after upload. Provide scoped credentials through the execution environment, never the prompt. Missing device consent, credentials, tools, or required checks must block the affected step; an available account or plan ID is not deployment authorization.
Authorize one deployment target
Use smoothie-deployment for Smoothie Starter at /absolute/my-product.
After its required native/browser checks pass, prepare a new sealed artifact.
Deploy to Cloudflare account <account-id>, Worker <new-worker-name>.
Creating this new Worker is authorized; replacing an existing one is not.
Use the scoped CLOUDFLARE_API_TOKEN already provided in the environment.
Native builds, provider preflight/upload/status reads, and read-only app smoke checks are authorized.
Do not broaden credentials, provision other services, or retry an uncertain upload.
Report the artifact digest, attempt path, version/traffic evidence, URL, and app-check results.Replace every placeholder before use. An update needs explicit replacement authority instead. The agent should review the build and deployment plans against that boundary, upload the same checked artifact, and keep attempt evidence for reconciliation.
Review deployment evidence
Expect separate artifact, submission, active-version/traffic, and application-check outcomes. Submitted is not healthy; an active version is not a passing application test. An unknown upload outcome requires reconciliation of the recorded attempt, not an automatic retry. Restoring a previous artifact is another authorized deployment, not restoration of database state, secrets, or all remote configuration.