void 0.20.1 → 0.20.3

package/skills/void/docs/guide/platform/development/runtime.md

@@ -0,0 +1,124 @@
+---
+outline: deep
+---
+
+# Runtime and Source Builds
+
+## Deploying Your Runtime
+
+Build the runtime. From a Git checkout, the build automatically records the current commit in the runtime manifest. An uncommitted checkout is recorded with a `-dirty` suffix:
+
+```sh
+vp run build:core
+```
+
+Build systems may set `VOID_PLATFORM_SOURCE_REVISION` when they need to override automatic detection with another immutable revision. A source archive without Git metadata builds normally but leaves the revision unrecorded.
+
+The runtime is written to `packages/platform/dist/runtime`. Use the built CLI to preview a new installation from those files:
+
+```sh
+void-dev platform install \
+  --name my-team \
+  --application-domain example.app \
+  --zone example.app \
+  --runtime packages/platform/dist/runtime \
+  --plan
+```
+
+Before applying the plan, complete the [installation guides](/guide/self-hosted-platform). Run the command without `--plan` to install. For testing before your domain is ready, replace `--application-domain` and `--zone` with `--workers-dev`; PostgreSQL and the runtime/GitHub/R2 credentials are still needed. Use `void-dev` in place of `void` and keep `--runtime packages/platform/dist/runtime` on install and resume commands. For an interrupted installation, keep that runtime build available until it completes.
+
+Later, run `void-dev platform domain set example.app`. Domain setup uses the existing installed runtime and needs no `--runtime`, rebuild, or app redeploy. It keeps the platform API URL and original workers.dev app URLs available.
+
+For an existing installation, preview an upgrade using its connection ID:
+
+```sh
+void-dev platform upgrade <installation-id> \
+  --runtime packages/platform/dist/runtime --plan
+```
+
+Then run it without `--plan` to apply the upgrade. Source-built runtimes go through the same artifact, database, ownership, and health checks as released runtimes. The CLI preserves a disabled installation's state and records the source revision in its installation checkpoint.
+
+## Optional GitHub Webhook Ingress for Access-Protected APIs
+
+The core installer does not deploy the dashboard, GitHub App, build Containers,
+or webhook ingress. Passing a source build with `--runtime` does not provision
+their infrastructure, bindings, credentials, or platform capabilities. The
+repository's hosted deployment scripts target Void Cloud; they are not a
+general setup procedure for adding these services to a self-hosted platform.
+Use the core CLI deployment workflow unless your fork supplies and maintains
+that optional integration.
+
+If your fork has added managed GitHub builds and Cloudflare Access protects its API hostname, GitHub cannot deliver directly
+to `/webhooks/github`: GitHub does not present your Access credentials. Do not add
+an Everyone or bypass policy to the API application.
+
+The API source package includes an optional, path-isolated Worker for this case.
+It accepts only `POST /github`, validates GitHub's signature over the raw body,
+and forwards one authenticated internal operation over an API service binding.
+The API independently verifies both that internal proof and GitHub's signature
+before running the normal webhook handler. Installations without perimeter
+protection can continue using the API's direct `/webhooks/github` endpoint.
+
+To deploy the optional ingress:
+
+1. Provision the GitHub App, build executors, API bindings, credentials, and
+   managed-build capability in your fork, then deploy its source API runtime
+   with the internal operation. A core install or upgrade alone does not add
+   managed builds.
+2. Edit `platform/packages/api/wrangler.github-webhook-ingress.jsonc`. Give the
+   ingress a name unique to the installation and set its `API` service binding to
+   the exact installed API Worker name. Keep its public hostname separate from
+   every human/API hostname covered by Access.
+3. Deploy it from the repository root:
+
+   ```sh
+   vp run --filter @voidcloud/api deploy:github-webhook-ingress --env production
+   ```
+
+   Use `--env staging` for the staging entries in the same config.
+
+4. In the Cloudflare dashboard, add encrypted Worker secrets. Set the GitHub
+   App's existing `GITHUB_WEBHOOK_SECRET` on both the API and ingress Workers.
+   Generate a separate high-entropy value, such as `openssl rand -base64 32`,
+   and set it as `GITHUB_WEBHOOK_INGRESS_SECRET` on both Workers. Do not reuse a
+   platform management, JWT, Access, or GitHub webhook credential for that value.
+5. In the GitHub App settings, keep **Content type** set to `application/json`,
+   keep the same webhook secret, and change **Webhook URL** to the isolated
+   ingress URL ending in `/github`. Use GitHub's test delivery and confirm a 2xx
+   response before relying on push builds.
+
+The ingress has no login, dashboard, project, operator, proxy, or arbitrary
+forwarding route. It does not make the GitHub integration part of the core
+installer, provision build executors, create a GitHub App, configure Cloudflare
+Access, or manage either Worker's secrets. Its body limit is 25 MiB, based on
+GitHub's [documented 25 MB webhook payload cap](https://docs.github.com/en/webhooks/webhook-events-and-payloads#payload-cap);
+malformed or larger deliveries are rejected before event processing.
+
+## Deploying Source Builds from CI
+
+Build `@void/platform` from your checkout and pass its runtime directory to `install`, `upgrade`, `repair`, `enable`, or `rollback` with `--runtime`. Custom runtimes get the same integrity, migration, health, and rollback checks as packaged releases.
+
+Void records the runtime's manifest digest, whether it was packaged or custom, and its source revision. A build from a Git checkout automatically records `HEAD`, or `<HEAD>-dirty` when the checkout has uncommitted files. Build systems can set `VOID_PLATFORM_SOURCE_REVISION` to override automatic detection.
+
+A fresh CI runner can discover the installation each time. Set `CLOUDFLARE_API_TOKEN` and `VOID_PLATFORM_DATABASE_URL` through its protected environment, then:
+
+::: details CI commands and recovery inputs
+
+```sh
+vp run build:core
+
+export VOID_PLATFORM_REGISTRY_DIR="$RUNNER_TEMP/void-platform-registry"
+export VOID_PLATFORM_RECOVERY_KEY="$(openssl rand -base64 32)"
+node packages/void/dist/cli/cli.mjs platform discover --account "$CLOUDFLARE_ACCOUNT_ID" \
+  --installation "$VOID_PLATFORM_INSTALLATION"
+node packages/void/dist/cli/cli.mjs platform upgrade "$VOID_PLATFORM_INSTALLATION" \
+  --runtime packages/platform/dist/runtime --plan
+node packages/void/dist/cli/cli.mjs platform upgrade "$VOID_PLATFORM_INSTALLATION" \
+  --runtime packages/platform/dist/runtime --yes
+```
+
+Omit the installation selector only if the account has one discoverable installation. Run one deployment per installation at a time, and let it finish before starting the next. Cancelling during migrations or Worker rollout can leave an installation waiting for recovery.
+
+Keep the management token, database URL, JWT signing secret, email signing secret for email-enabled installations, and complete project-encryption keyring in a protected CI environment. Upgrades inherit deployed Worker secrets. The original values are needed when recreating a missing Worker; configuration credentials are also needed when explicitly rotating them.
+
+:::

package/skills/void/docs/guide/platform/development/schema-ci.md

@@ -0,0 +1,95 @@
+---
+outline: deep
+---
+
+# Schema and CI
+
+## Changing the Platform Schema
+
+The schema lives in `platform/packages/api/src/schema.ts`. Generate a migration after changing it:
+
+```sh
+vp run --filter @voidcloud/api db:generate
+```
+
+Review the generated SQL and migration journal before committing them. Released migrations are append-only. An upgrade applies new migrations while the previous Workers may still serve requests, so schema changes must remain compatible with that code.
+
+`platform/packages/api/drizzle/compatibility.json` records which earlier runtimes have been verified against the new schema. Add an edge only after testing that compatibility. The runtime build checks that the migration files and recorded schema history agree. See `packages/platform/README.md` for the manifest contract.
+
+## CI in a Fork
+
+The uncredentialed test workflows use GitHub-hosted runners in forks. They build and test the workspace without requiring Void Cloud accounts, tokens, or deployment access.
+
+If your fork has a released platform version, set the repository variable
+`VOID_PLATFORM_PRODUCTION_REF` to its immutable 40-character commit SHA. Platform
+pull requests then create that version's database, seed representative user,
+project, and encrypted-secret records, and apply the proposed migrations. The
+check verifies existing data and runs the previous runtime against the upgraded
+schema. Mutable branch or tag names are rejected.
+
+Without an explicit SHA, required compatibility checks use the latest successful
+GitHub deployment to `Prod` (or `VOID_PLATFORM_PRODUCTION_ENV`). They require
+read access to deployment history and stop if no completed deployment is found.
+Advancing the production branch does not change the selected baseline. Fork
+workflows that call platform CI must grant `deployments: read` alongside
+`contents: read`.
+
+The upstream repository also contains workflows for deploying Void Cloud and publishing the official npm packages. Forks should configure their own release workflow around the built CLI and `platform upgrade --runtime`; the [source-build CI example](/guide/platform/development/runtime#deploying-source-builds-from-ci) shows the required inputs. Keep production credentials in protected environments restricted to the appropriate release refs.
+
+Public releases use matching versions for the CLI, scaffolder, adapters, and
+packaged platform. The publish workflow rejects mismatched versions and previously
+unpublished `void` versions that npm cannot reuse. Stable versions use `latest`;
+prereleases use their named channel, such as `beta` or `rc`. Numeric prereleases
+use `next`. The scaffolder installs its exact matching CLI version, so
+`create-void@beta` cannot silently select the stable CLI. Packaged platform
+runtimes record the release commit as their source revision.
+
+The npm release job uses [trusted publishing](https://docs.npmjs.com/trusted-publishers/)
+from GitHub-hosted runners, with `id-token: write` and no stored npm publishing
+token. Configure a trusted publisher for each public package using this
+repository, `publish.yml`, and the `Release` environment, allowing direct
+`npm publish`. A brand-new package
+needs an initial authenticated publication before its trusted publisher can be
+configured; subsequent releases use OIDC.
+
+The managed build fallback CLI also derives its version from
+`packages/void/package.json`; there are no separate version pins to update.
+Build its image from the repository root with
+`docker build --file platform/packages/api/container/Dockerfile .`.
+The root `.dockerignore` limits that build context to the agent, Dockerfile,
+and public SDK manifest.
+
+Publishing requires both SDK CI and platform CI, including the platform unit and
+API integration suites. Release tags also run the Windows SDK checks; a passing
+SDK-only build cannot publish a changed control plane.
+
+### Retrying a Release
+
+To retry a failed release without moving an existing tag, add `+retry.N` to a
+new Git tag, with `N` starting at `1`. Keep the package versions unchanged:
+
+| Git tag                  | Package version | npm channel |
+| ------------------------ | --------------- | ----------- |
+| `v0.21.0`                | `0.21.0`        | `latest`    |
+| `v0.21.0+retry.1`        | `0.21.0`        | `latest`    |
+| `v0.21.0-beta.1+retry.2` | `0.21.0-beta.1` | `beta`      |
+
+For example, when the packages are at `0.21.0`, commit the release fix and tag
+that commit:
+
+```sh
+git tag -a 'v0.21.0+retry.1' -m 'Retry 0.21.0 publication.'
+git push origin 'refs/tags/v0.21.0+retry.1'
+```
+
+The retry suffix belongs only in the Git tag, not in `package.json`. A `-1`
+suffix is a distinct prerelease version, not a retry. Tag and package versions
+are checked before dependency installation and the full CI jobs; retries still
+run the normal release checks.
+
+Retries publish only package versions that are still missing from npm. They
+cannot replace an already-published version. If an earlier attempt partially
+published the release and you changed its package contents, bump the version
+instead of combining different contents under the same version.
+
+For implementation history, use the design archive at `platform/meta/design-docs/README.md`. Its proposals explain earlier decisions; the source and current guides define the supported behavior.

package/skills/void/docs/guide/platform/installation/ci.md

@@ -0,0 +1,55 @@
+---
+outline: deep
+---
+
+# Install from CI
+
+For your first installation, follow the [interactive setup](/guide/platform/installation/setup). Use this page when automating a configured installation.
+
+::: details Non-interactive inputs
+
+Inject the following values from protected CI secrets. Do not commit them in a workflow or a plaintext secrets file.
+
+| Environment variable                         | Value from the interactive setup                                                            |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| `CLOUDFLARE_API_TOKEN`                       | Management API token                                                                        |
+| `VOID_PLATFORM_RUNTIME_CLOUDFLARE_API_TOKEN` | Runtime API token                                                                           |
+| `VOID_PLATFORM_DATABASE_URL`                 | Dedicated PostgreSQL URL                                                                    |
+| `VOID_PLATFORM_R2_ACCESS_KEY_ID`             | R2 Access Key ID                                                                            |
+| `VOID_PLATFORM_R2_SECRET_ACCESS_KEY`         | R2 Secret Access Key                                                                        |
+| `VOID_PLATFORM_JWT_SECRET`                   | Original JWT signing secret                                                                 |
+| `VOID_PLATFORM_EMAIL_SIGNING_SECRET`         | Dedicated email signing secret when email is enabled                                        |
+| `VOID_PLATFORM_PROJECT_SECRET_KEY`           | Original base64-encoded project-encryption key                                              |
+| `VOID_PLATFORM_RECOVERY_KEY`                 | Base64-encoded 32-byte key for local encrypted recovery state when no keychain is available |
+| `VOID_EMAIL_SENDER_DOMAIN`                   | Optional shared mail domain; requires `VOID_EMAIL_SHARED_ZONE_ID`                           |
+| `VOID_EMAIL_SHARED_ZONE_ID`                  | Cloudflare zone ID for that mail domain; requires `VOID_EMAIL_SENDER_DOMAIN`                |
+
+For the default GitHub-only login, also set `VOID_PLATFORM_GITHUB_CLIENT_ID`,
+`VOID_PLATFORM_GITHUB_CLIENT_SECRET`, and `VOID_PLATFORM_ADMIN_GITHUB_LOGIN`.
+For Google, OIDC, or Access login, pass `--auth-config <path>` using the
+[configuration format](/guide/platform/installation/setup#choose-login-methods).
+Inject each `clientSecretEnv` named in that file from your CI secret manager.
+Automatic Access protection may also need `VOID_PLATFORM_ACCESS_SETUP_TOKEN`
+with the [setup permissions](/guide/platform/installation/setup#cloudflare-access).
+
+Use that installation's saved signing and encryption keys on every resume or repair that needs them. After a keyring rotation, use the [complete keyring recovery inputs](/guide/platform/installation/maintenance#manage-an-installation-from-another-machine). The database claim and tables remain after uninstall; use a fresh database for a different installation.
+
+Set both email values to enable email during install or upgrade. Later upgrades reuse the recorded values. If an email-enabled installation has no recorded values, supply both before upgrading.
+
+```sh
+void platform install \
+  --name team \
+  --display-name "Team Void" \
+  --account <account-id> \
+  --application-domain example.app \
+  --zone example.app \
+  --yes
+```
+
+Mutations require `--yes` in CI; a read-only `--plan` does not. Custom runtimes also require `--runtime <directory>`. For a new installation, run `--plan` with the same account, name, and domain options as the unattended install. If you use `--auth-config`, pass the same file to both commands. Register the printed callback when creating a login provider's OAuth or OIDC client manually; automatic Access setup manages its own application. A custom API hostname is optional.
+
+:::
+
+## Customize the Platform
+
+To change the platform's implementation or deploy your own build, follow [Platform Development](/guide/platform-development). It covers local development, source builds, and CI for a fork.

package/skills/void/docs/guide/platform/installation/credentials.md

@@ -0,0 +1,80 @@
+---
+outline: deep
+---
+
+# Credentials
+
+Keep one password-manager entry for this platform. Paste the saved values into the installer when asked; most do not need shell environment variables.
+
+## Cloudflare API Tokens {#runtime-token-permissions}
+
+For a domain installation, create two custom tokens using Cloudflare's [API token setup](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/). Name them **Void Platform Management** and **Void Platform Runtime**. Scope them to your selected account and application zone.
+
+For workers.dev testing with the default API hostname, browser login can authorize installation: you only need to create the runtime token and R2 credentials below. Skip the zone permissions until you add a domain.
+
+Browser login does not grant AI Gateway access. A preview can therefore show **inspect ai-gateway**: Void verifies that resource with the runtime token after you confirm installation, before creating any resources. Include **Account → AI Gateway → Edit** on that token. Other infrastructure continues using your browser login, and a normal API-token installation keeps using its management token when that token already has access.
+
+The management token lets your CLI install and maintain the platform. The runtime token is stored as a Worker secret so the platform can deploy apps after you close your terminal. They are separate credentials.
+
+The runtime-token link preselects all required account permissions, including Workers Tail, Hyperdrive, and AI Gateway when needed. Review them against the short summary beside the link before creating the token. If the form differs, use that summary to correct it. For a domain installation, also select the indicated zone. See [Cloudflare's token template documentation](https://developers.cloudflare.com/fundamentals/api/how-to/account-owned-token-template/).
+
+::: details Permissions to select for each token
+
+Use the following permissions for the core platform. Cloudflare may label write access as **Edit** or **Write**, depending on the token screen; see its [permission reference](https://developers.cloudflare.com/fundamentals/api/reference/permissions/).
+
+| Scope   | Permission         | Management | Runtime                                 |
+| ------- | ------------------ | ---------- | --------------------------------------- |
+| Account | Account Settings   | Read       | Read                                    |
+| Account | Workers Scripts    | Edit       | Edit                                    |
+| Account | Workers Tail       | Read       | Read                                    |
+| Account | D1                 | Edit       | Edit                                    |
+| Account | Workers KV Storage | Edit       | Edit                                    |
+| Account | Workers R2 Storage | Edit       | Edit                                    |
+| Account | Queues             | Edit       | Edit                                    |
+| Account | Hyperdrive         | Write      | Write                                   |
+| Account | Account Analytics  | Read       | Read                                    |
+| Account | AI Gateway         | Edit       | Edit when installing with browser login |
+| Zone    | Zone               | Read       | —                                       |
+| Zone    | DNS                | Edit       | —                                       |
+| Zone    | Workers Routes     | Edit       | —                                       |
+| Zone    | Cache Purge        | —          | Purge                                   |
+
+The management token also needs **Zone Edit** with authority to create zones if you ask Void to create the zone. If it already exists, use the selected zone with Zone Read and DNS Edit. Nested application domains additionally need **SSL and Certificates: Read** on the management token. A custom runtime that enables custom project domains needs **SSL and Certificates: Edit** on the runtime token; the core runtime does not enable that feature.
+
+Enabling email lets administrators [register email domains for projects](/guide/platform/administration/email#registering-email-domains-for-projects) and lets projects register destination addresses through the runtime token. That needs **Email Routing Addresses: Edit** and **Email Sending: Edit** on the account, plus **Zone: Read**, **Zone Settings: Edit** and **Email Routing Rules: Edit** on the zones that will carry mail; the token link preselects them when email is enabled. Email Sending onboarding itself needs Workers Paid on the account.
+
+To enable email, set `VOID_EMAIL_SENDER_DOMAIN` to the shared sender domain and `VOID_EMAIL_SHARED_ZONE_ID` to its Cloudflare zone ID when installing or upgrading. Void records both values for later upgrades and rejects attempts to replace them during an ordinary upgrade. The mail zone can differ from the application zone, but it must belong to the selected platform Cloudflare account; without an explicit mail-zone identity, shared inbound delivery stays unavailable. The dedicated email gateway is deployed in the platform account. Each customer zone uses its own ingress Worker to forward mail to that gateway.
+
+The installer prepares the shared mail route and verifies inbound readiness before it opens platform traffic. If that setup fails, the installation remains disabled. Correct the reported Cloudflare permission, mail-zone configuration, or routing conflict, then rerun the same install or upgrade command; a fresh install resumes with `void platform install --resume --name <installation-id>`.
+
+Void checks access before provisioning. If it reports a missing permission, update the token's permissions for the selected account or zone and retry.
+
+:::
+
+## R2 Upload Credentials
+
+The installer opens the **R2 token creation** form directly, requesting an account token (or a user token if your role cannot create account tokens). Select **Object Read & Write**—the form starts with read-only access—and keep **Apply to all buckets in this account (including newly created buckets)** selected. This lets the token access the buckets Void creates afterward. Create the token and save its **Access Key ID** and **Secret Access Key**. These are different from the management/runtime tokens above. See [R2's token instructions](https://developers.cloudflare.com/r2/api/tokens/).
+
+## Signing and Encryption Keys {#signing-and-encryption-keys}
+
+The **JWT signing key** signs platform login tokens. The **Project encryption key** encrypts app secrets stored by your platform. Generate a separate key for each by running this command twice:
+
+```sh
+openssl rand -base64 32
+```
+
+Save each result in your password manager, then paste it into the corresponding installer prompt. The command generates 32 random bytes encoded as base64, suitable for either field. Keep the two original keys for recovery; do not regenerate them when resuming or upgrading.
+
+::: details Generate the keys without printing them to your terminal
+
+On macOS, this copies a suitable random value to the clipboard:
+
+```sh
+openssl rand -base64 32 | pbcopy
+```
+
+Paste it into your password manager as **JWT signing key**. Run the command again and save the second value as **Project encryption key**. On PowerShell, use `Set-Clipboard` instead of `pbcopy`. If OpenSSL is unavailable, use your secret manager's secure generator for 32 random bytes in base64, or `node -e 'process.stdout.write(require("node:crypto").randomBytes(32).toString("base64"))'`.
+
+:::
+
+When email is enabled, Void also creates an independent **Email signing key** for confirmation links and service-to-service email requests. The installer keeps it in encrypted recovery state. Set `VOID_PLATFORM_EMAIL_SIGNING_SECRET` to a separate value of at least 32 random bytes when you need an externally custodied copy, including a headless installation whose local recovery files will not persist.

package/skills/void/docs/guide/platform/installation/domains.md

@@ -0,0 +1,68 @@
+---
+outline: deep
+---
+
+# Domains and Resources
+
+## Adding a Domain
+
+When your domain is ready, run:
+
+```sh
+void platform domain set example.app --plan
+void platform domain set example.app
+```
+
+The command selects your installed platform (or offers a picker), finds or creates its zone, sets up DNS and routing, and verifies HTTPS before publishing the new application URLs. Set the management token as described in [installation setup](/guide/platform/installation/setup) when creating DNS or a zone. Grant the existing runtime token **Cache Purge: Purge** on the new zone; Void checks that permission through the running platform without asking you to paste its token again.
+
+If nameservers or certificates are pending, follow the printed guidance and rerun the same command. Your workers.dev app URLs continue working during and after setup. Projects, deployments, secrets, and the platform API URL stay the same, so developers do not reconnect and configured login callbacks do not change. DNS and configuration changes may take time to propagate.
+
+Use `--installation <id>` to select an installation explicitly, `--zone example.com` for an app domain such as `apps.example.com`, or `--dedicated-zone` for catch-all routing on a dedicated zone. Nested domains still need the wildcard certificate described below. This command adds the first domain; replacing an existing application domain is not currently supported. It uses the installed runtime and does not require `--runtime` or an app redeploy.
+
+Browser login sessions are specific to each origin. Apps using their own OAuth providers may need to register their new callback URLs. Void's built-in auth uses the request origin automatically unless the app overrides that configuration.
+
+### What Changes in Testing Mode?
+
+Each deployed app gets a small forwarding Worker and its own `workers.dev` origin. It forwards requests, including WebSockets and SSE, through the same platform router. Names include installation and project IDs; a later project with the same slug cannot inherit a deleted project's test URL.
+
+Testing origins use shared ISR storage but bypass the extra edge response cache because you cannot use your zone's purge API for `workers.dev`. Custom-domain requests use the normal edge cache after activation. Existing test URLs and forwarding Workers are retained when you add a domain; new apps then use the domain without creating more forwarding Workers. Like other platform Workers, forwarders are retained for manual cleanup on uninstall; platform disablement and project suspension still apply to their traffic.
+
+## Other Domain Options
+
+::: details Custom API hostname
+
+Pass `--control-plane-domain platform.example.net` during installation. The hostname must belong to a zone the selected account and management token can manage. Omitting it keeps the API on `workers.dev`.
+
+:::
+
+### Using a Nested Application Domain
+
+::: details Use apps.example.com within an existing company zone
+
+An app at `my-app.apps.example.com` needs a certificate for `*.apps.example.com`. Universal SSL for `example.com` only covers first-level hostnames. Configure an active wildcard certificate with [Advanced Certificate Manager](https://developers.cloudflare.com/ssl/edge-certificates/advanced-certificate-manager/), a paid add-on, or use an existing custom wildcard certificate before installation:
+
+```sh
+void platform install --application-domain apps.example.com --zone example.com --plan
+```
+
+The management token needs **SSL and Certificates: Read** (or Edit) on that zone for the certificate check. Void does not order certificates or enable paid products automatically. Leave `--dedicated-zone` off: that flag is only for installations whose application domain is the entire zone and adds catch-all routes for otherwise unmatched traffic.
+
+:::
+
+## Cloudflare footprint
+
+New platform resources use deterministic `void-<installation-name>-<role>` names where Cloudflare allows them, such as `void-team-api`. Choose an unused installation name in the account; Void stops on an unowned name conflict instead of replacing that resource. Existing installations keep their recorded names, including older names with suffixes.
+
+| Resource                                  |                                 Count | Purpose                                                                                       |
+| ----------------------------------------- | ------------------------------------: | --------------------------------------------------------------------------------------------- |
+| Workers                                   | 5, plus one per app using workers.dev | API/control plane, proxy, tail ingestion, dispatch, email gateway, and test-origin forwarders |
+| KV namespaces                             |                                     3 | Routing, ISR cache, and static asset storage                                                  |
+| R2 buckets                                |                                     1 | Static and deployment assets                                                                  |
+| Queues                                    |                                     2 | Usage events and cron firing                                                                  |
+| Workers for Platforms dispatch namespaces |                                     1 | User application Workers                                                                      |
+| Hyperdrive configurations                 |                                     1 | External platform PostgreSQL                                                                  |
+| AI Gateways                               |                                     1 | Installation-isolated AI routing and metering                                                 |
+| Proxied wildcard DNS records              |                                0 or 1 | Created only when an application domain is configured                                         |
+| Zones                                     |                                0 or 1 | Created only when the requested application zone is absent                                    |
+
+The API Worker uses four Durable Object classes for usage, cron scheduling, error monitoring, and concurrency. Worker bindings create the request and log datasets in Analytics Engine. The core installation doesn't create Container applications, a GitHub App, a dashboard Worker, or build Workers.

package/skills/void/docs/guide/platform/installation/first-deployment.md

@@ -0,0 +1,82 @@
+---
+outline: deep
+---
+
+# First Deployment
+
+First verify the new platform and sign in with the administrator login method selected during setup:
+
+```sh
+void platform status
+void platform auth login
+void platform system health
+```
+
+Administrator login is separate from the credentials used to deploy apps. In a new or unlinked Void app directory, connect using the installed API URL and deploy your first project:
+
+```sh
+void connect https://void-company-api.example.workers.dev
+void deploy --platform void --project my-first-app
+```
+
+`void connect` validates the platform and signs you in when needed. Confirm project creation when deploy asks. To use a project that already exists, run `void project link` instead. An app already linked to another platform keeps its existing destination; use a fresh app directory for your first test.
+
+The CLI stores login credentials in your system keychain, separately for each platform URL. With no URL, `void connect` offers Cloudflare or a Void platform; `void connect --platform void` offers saved platforms and an option to enter another URL.
+
+For CI, create a bounded, project-scoped deploy credential while signed in as
+the project owner:
+
+```sh
+void project token create --name ci --expires-in 30
+```
+
+Store the printed `VOID_TOKEN` and `VOID_API_URL` in the CI secret manager, then
+use `void connect <url> --no-login` in a fresh checkout if connection metadata
+is not committed. Rotate with `void project token renew <id>` and revoke with
+`void project token revoke <id>`. A human login token is not a CI credential.
+
+If Cloudflare Access protects the platform, Access proof and the project
+credential are both required; the service token does not grant Void user or
+operator authority. A deploy that uses prerendering or remote bindings calls
+both the API and proxy, so store `VOID_ACCESS_CREDENTIALS` in the CI secret
+manager with entries for both exact HTTPS origins. Include both entries even
+when the same admitted service-token pair is used for both origins:
+
+```json
+{
+  "https://void-company-api.example.workers.dev": {
+    "CF_ACCESS_CLIENT_ID": "<service-token client ID>",
+    "CF_ACCESS_CLIENT_SECRET": "<service-token client secret>"
+  },
+  "https://void-company-proxy.example.workers.dev": {
+    "CF_ACCESS_CLIENT_ID": "<service-token client ID>",
+    "CF_ACCESS_CLIENT_SECRET": "<service-token client secret>"
+  }
+}
+```
+
+`VOID_ACCESS_ORIGIN` can scope credentials to one origin only; setting it to
+the API origin does not authorize proxy requests.
+
+Use these commands to inspect connections and installations:
+
+```sh
+void platform list
+void platform use [id]
+void platform status [id]
+```
+
+## Managing Access
+
+After installation, sign in as the first administrator. For a teammate who uses GitHub, add their login to the signup allowlist:
+
+```sh
+void platform auth login
+void platform signup allow github teammate
+```
+
+Void shows the proposed access change and asks you to confirm it. Once approved, `teammate` can connect to the platform's API URL and sign in with GitHub.
+
+To see who can join, run `void platform signup show`. You can also allow an email address or a domain such as `*@example.com`. For an OIDC user without verified email, use `void platform signup allow identity <connection-id> <subject>`; the subject match is exact and the provider's domain or group restrictions still apply. Remove that grant with `void platform signup disallow identity <connection-id> <subject>`. `void platform signup open` permits public signup; `void platform signup restrict` requires an allowlist match again.
+
+Your administrator session lasts for one hour. Use it to inspect users, projects, logs, and platform health. The [Platform Administration guide](/guide/platform-administration) walks through those workflows, previews, and automation. You can also open `<API origin>/admin/login` to use the browser admin UI.