Security, privacy, cost and observability
Preparation and future coordination must treat project content, third-party code and cloud operations as untrusted and auditable.
Trust boundary
Browser demos are static. Real preparation must isolate code that can execute package scripts and must not run arbitrary project code on a privileged host.
Credentials and data
Use least-privilege, revocable credentials. Do not place tokens in locks, materialization manifests, cache keys, logs, screenshots or reusable image layers. Private datasets remain private inputs and are not cross-tenant deduplicated solely by hash.
Destructive and paid operations
Hover, focus and scroll never create resources. Explicit execution must enforce authorization, budget, TTL, concurrency, allowlists and cleanup ownership.
Observability
Keep environment, workspace and run events distinct. Record stale/unknown observation separately from confirmed failure. Task timeout and API-request timeout are not the same event.