Optional GCP adapter prerequisites

The GCP compute adapter is preview. An operator must explicitly enable it and supply an already provisioned project, canonical store, scoped managed identity or Skarbiec service account, quota overlay, network, image, ownership labels, cost policy, and immutable Stado release. Runtime compute and storage operations stay inside the Rust provider adapters; install, bootstrap, release, health, and recovery paths do not invoke a cloud CLI.

The image and the geography are required bindings: GCP_IMAGE and GCP_IMAGE_PROJECT (config keys image and image_project), GCP_ZONES (zones, the zones a machine is created in, in preference order) and GCP_REGIONS (regions, whose quota is read). None is built in: a machine create without them is refused with GCP compute bindings are not declared: … naming the missing ones, and a quota read or request without regions says so. A zone that does not carry the machine type answers GCE's own error and the next declared zone is tried. The Azure provider likewise needs its resource group, locations, vnet, subnet, NSG, image URN and VM user declared, and the AWS provider its region, security group, IAM profile and AMI; each refusal names the bindings that are missing.

Zone candidates and machine compatibility belong to the selected deployment profile. Resource exhaustion may advance to the next allowed candidate; an authorization, ownership, invalid configuration, or ambiguous provider error must not. GCP is not stable until a release-scoped live test creates an owned VM, boots the pinned agent, runs and collects a workload, exercises cancellation and recovery, and reaps all paid resources.

The active deployment workflow publishes immutable native releases and installs the Rust coordinator. It has no Cloud Function scheduler, mutable package upgrade, provider CLI authentication, or ambient credential fallback.