v2-platform: 13 provider consolidation — one self-hostable alchemy program

Parent

#274 (v2 platform services spec)

What to build

Provider consolidation: buckets, sandbox machines, and DNS declared together as ONE alchemy program — the everything.dev service provider as a self-hostable artifact. A sovereign tenant (or anyone) runs the program against their own cloud accounts (Cloudflare, Fly, or Hetzner) and gets a functioning provider: upload storage for their namespace, sandbox machines, wildcard DNS/TLS. This is the "reduce platform dependency" endgame — the provider is not a vendor, it is a program. Includes the self-hosting documentation path for sovereign tenants (provider + own databases + own host = fully self-owned deployment).

Acceptance criteria

• One alchemy program declares the full provider (storage buckets, machines, DNS) and deploys with a single command

• A second, isolated stage of the same program (self-host simulation) comes up fully on a different account and serves the deploy→sandbox loop

• Self-hosting documentation covers the sovereign-tenant path end-to-end (provider + databases + host)

• The platform's own production provider runs from this same program (no bespoke infra outside it)

• #286 (pre-spawned sandbox pool — machines + DNS resources exist to consolidate)

Blocked by

• #279 (R2/S3 storage provider)

Start with the v2 platform services spec in #274, then review the dependencies in #286 and #279 before locating the existing provider resources. Done means one Alchemy program deploys storage, machines, and DNS with one command, a separate isolated stage serves the deploy-to-sandbox loop, sovereign-tenant documentation is complete, and production uses the same program.