void 0.25.0 → 0.26.1

package/{skills/void/docs → docs}/reference/cli/github.md

@@ -6,6 +6,8 @@ outline: deep
 
 Deploy-on-GitHub works from **any** Void login — Google, GitHub, or other SSO. The first time you connect GitHub, Void links your GitHub identity to your current account (a one-time step, independent of how you logged in); it never creates a second account.
 
+Project-scoped `github` and `build` commands resolve the project in the same order as deploy: the `[project]` argument or `--project`, then `VOID_PROJECT`, then the linked project (`.void/project.json`).
+
 ## `void github link` {#void-github-link}
 
 ```
@@ -78,8 +80,6 @@ void github connect my-app \
   --branch main
 ```
 
-**Project resolution** follows the same order as deploy: positional / `--project`, `VOID_PROJECT`, linked project (`.void/project.json`).
-
 You can connect only repositories your GitHub account can access.
 
 A project has one GitHub connection. Running `void github connect` on a project that is already connected fails. To connect a different repository, run `void github disconnect` first.
@@ -107,8 +107,6 @@ The CLI prompts for new settings using the current values as defaults. In CI, pa
 void github update my-app --executor github_actions
 ```
 
-**Project resolution** follows the same order as deploy: positional / `--project`, `VOID_PROJECT`, linked project (`.void/project.json`).
-
 ## `void github status` {#void-github-status}
 
 ```
@@ -127,15 +125,13 @@ Show the connected repository, branch, executor, and workflow. Container builds
 void github status my-app
 ```
 
-**Project resolution** follows the same order as deploy: positional / `--project`, `VOID_PROJECT`, linked project (`.void/project.json`).
-
 ## `void github disconnect` {#void-github-disconnect}
 
 ```
 void github disconnect [project]
 ```
 
-Disconnect a project from its GitHub repository, stopping automatic deploys. Any in-flight builds for the project are cancelled (their deploy tokens are revoked) before the connection is removed. If the project has no connection, it reports that and exits successfully. To point a project at a different repository, disconnect first, then run `void github connect`.
+Disconnect a project from its GitHub repository, stopping automatic deploys. Any in-flight builds for the project are cancelled before the connection is removed. If the project has no connection, it reports that and exits successfully. To point a project at a different repository, disconnect first, then run `void github connect`.
 
 You are asked to confirm before anything is removed. Pass `--yes` to skip the prompt; `--yes` is **required** in a non-interactive shell (CI), where there is no prompt to answer.
 
@@ -150,8 +146,6 @@ You are asked to confirm before anything is removed. Pass `--yes` to skip the pr
 void github disconnect my-app --yes
 ```
 
-**Project resolution** follows the same order as deploy: positional / `--project`, `VOID_PROJECT`, linked project (`.void/project.json`).
-
 ## Build {#build}
 
 Inspect Deploy-on-GitHub builds.
@@ -171,9 +165,6 @@ Stream, tail, or download the build logs for a **container** build. With no
 | `--output <file>`, `-o`  | Write logs to a file instead of stdout (appends while following).         | stdout  |
 | `--project <slug>`, `-p` | Target project.                                                           | linked  |
 
-**Project resolution** follows the same order as deploy: positional / `--project`,
-`VOID_PROJECT`, linked project (`.void/project.json`).
-
 Builds run on **GitHub Actions** keep their logs on GitHub — the command prints
 the Actions run URL instead of streaming. Only the last 10,000 log lines of a
 container build are retained.

package/{skills/void/docs → docs}/reference/cli/platform-config.md

@@ -20,7 +20,7 @@ void platform config plans default <plan-id>
 void platform config plans sync
 ```
 
-Use `--plan` to preview changes and affected accounts; scripted mutations require `--yes`. Every command supports `--connection <registered-id-or-url>` and `--json`. `show` reports the effective limits, default, assignments, and pending account updates. `reset` restores a built-in plan's original limits and build instance size. Archived plans keep their existing accounts but cannot receive new assignments; change the default before archiving it. `remove` requires a replacement for a plan that has accounts or is the default. Changing the default affects only new accounts.
+Use `--plan` to preview changes and affected accounts; scripted mutations require `--yes`. Every command supports `--connection <slug-or-url>` and `--json`. `show` reports the effective limits, default, assignments, and pending account updates. `reset` restores a built-in plan's original limits and build instance size. Archived plans keep their existing accounts but cannot receive new assignments; change the default before archiving it. `remove` requires a replacement for a plan that has accounts or is the default. Changing the default affects only new accounts.
 
 For `add` and `set`, `--file` reads a JSON object with optional `name`, `limits`, `buildInstanceType`, and boolean `allowShortSlugs`. `limits` is a partial object of nonnegative whole numbers; `0` means unlimited by the plan. Build timeouts remain capped at the platform maximum of 60 minutes; `0` uses that maximum. Omitted settings keep their current values or the copied plan's values. `buildInstanceType` is `standard-3` or `standard-4`. `allowShortSlugs` permits future assignments of project slugs of five characters or fewer; existing URLs remain available. Storage quotas are not editable. See [Plans and Limits](../../guide/platform/administration/plans.md) for supported limits and examples.
 
@@ -60,7 +60,7 @@ alternative; the last method cannot be disabled. Disabling revokes human session
 created through that method, including operator sessions. Scoped deployment tokens
 remain valid; a human login token used as `VOID_TOKEN` is still revoked.
 
-Commands accept `--connection <registered-id-or-url>` and `--json`. Changes accept
+Commands accept `--connection <slug-or-url>` and `--json`. Changes accept
 `--plan` or `--yes`. For scripted configuration, use `--file <path>` for the
 nonsecret fields and `--client-secret-env <name>` for the environment variable
 containing the secret. Omit the secret when editing to retain its saved value.
@@ -89,4 +89,4 @@ when using `--yes`. Recovery requires Cloudflare management/database authority,
 original recovery keys, and a successful browser provider test. Use
 `--client-secret-env <name>` for new or rotated credentials.
 
-For automation, supply `VOID_OPERATOR_TOKEN` with an explicit `VOID_API_URL` or `--connection`. Operator tokens are stored separately from application deployment credentials. The API checks your current administrator access on every request. See [Using Scripts](../../guide/platform/administration/operations.md#using-scripts) for an example.
+For automation, see [operator authentication](./platform.md#operator-authentication).

package/{skills/void/docs → docs}/reference/cli/platform-email.md

@@ -42,9 +42,8 @@ has ended and the operation is at least 24 hours old, inspect the exact resource
 named by the preview and attest whether its write was `applied` or `not-applied`.
 Applied writes continue at the next step; not-applied writes retry the same
 persisted intent. The running platform version must match that intent, so restore
-the matching version before recovering an operation created by older code. The
-preview pins the step, attempt, connection and route generations, resource
-identity, and digest used by the apply request. Time alone never retries a write.
+the matching version before recovering an operation created by older code. Time
+alone never retries a write.
 
 `shared-recipients` discovers shared inbound addresses, provider rule names and
 IDs, and interrupted creation intents, including projects awaiting deletion.

package/{skills/void/docs → docs}/reference/cli/platform-installation.md

@@ -101,29 +101,29 @@ void platform rollback [id] --runtime <earlier-path> [--from-runtime <current-pa
 void platform repair [id] [--runtime <path>] [--dashboard-url <origin>] [--plan] [--yes]
 void platform disable [id] [--plan] [--yes]
 void platform enable [id] [--runtime <path>] [--plan] [--yes]
-void platform uninstall [id] [--plan] [--purge-data] [--keep-zone] [--yes]
+void platform uninstall [id] [--plan] [--purge-data | --purge-resources] [--keep-zone] [--yes]
 ```
 
 `discover --installation` limits recovery and endpoint verification to one installation in a shared Cloudflare account.
 
-Omit `id` when only one installation is configured, or choose from the interactive picker. Non-interactive commands need an ID when several installations exist. Commands that make changes also require `--yes`; `--plan` only previews changes.
+Use the installation slug shown beside its name in `void platform list`. Installation IDs and saved connection IDs also work. Lifecycle commands require local installation records; use `discover` to restore them on another machine. Omit `id` when only one installation is configured, or choose from the interactive picker. Non-interactive commands need a slug or ID when several installations exist. Commands that make changes also require `--yes`; `--plan` only previews changes.
 
 To add or explicitly change a separately deployed dashboard after installation,
 use `repair --dashboard-url <origin>` or `upgrade --dashboard-url <origin>`.
 Preview with `--plan` first. Existing Access protection must cover the configured
 dashboard origin before maintenance can proceed. See [Optional Dashboard](../../guide/platform/installation/domains.md#optional-dashboard).
 
-After discovery on another machine, set `VOID_PLATFORM_DATABASE_URL`. An upgrade that preserves every deployed Worker also preserves its secrets. For an email-enabled installation without its encrypted recovery file, restore `VOID_PLATFORM_EMAIL_SIGNING_SECRET`; recreating only the email gateway needs that key and does not need the Cloudflare runtime token or JWT signing key. Recreating the API or proxy also requires the email key when email is enabled, in addition to their normal secrets. Recreating the API requires its original runtime-token, GitHub, R2, JWT, and project-encryption values; recreating the proxy requires the runtime token and JWT signing key.
+After discovery on another machine, set `VOID_PLATFORM_DATABASE_URL`. See [Manage an installation from another machine](../../guide/platform/installation/maintenance.md#manage-an-installation-from-another-machine) for the secrets needed to recreate a missing Worker.
 
-| Command     | Behavior                                                                                      |
-| ----------- | --------------------------------------------------------------------------------------------- |
-| `discover`  | Verifies remote ownership and restores local installation records without downloading secrets |
-| `repair`    | Recreates missing resources owned by the installer                                            |
-| `upgrade`   | Deploys the selected runtime and supported pending migrations                                 |
-| `rollback`  | Restores a declared-compatible earlier runtime without reversing PostgreSQL migrations        |
-| `disable`   | Blocks platform traffic through routing storage without removing data                         |
-| `enable`    | Restores traffic after checking the platform                                                  |
-| `uninstall` | Blocks traffic and removes eligible resources, retaining data by default                      |
+| Command     | Behavior                                                                                                    |
+| ----------- | ----------------------------------------------------------------------------------------------------------- |
+| `discover`  | Verifies remote ownership and restores local installation records without downloading secrets               |
+| `repair`    | Recreates missing resources owned by the installer                                                          |
+| `upgrade`   | Deploys the selected runtime and supported pending migrations                                               |
+| `rollback`  | Restores a declared-compatible earlier runtime without reversing PostgreSQL migrations                      |
+| `disable`   | Blocks app traffic and the platform API without removing data; only admin status and sign-in stay available |
+| `enable`    | Redeploys and verifies the platform Workers, then restores traffic                                          |
+| `uninstall` | Blocks traffic and removes eligible resources, retaining data by default                                    |
 
 Repair and upgrade preserve disabled state. New, resumed, and previously disabled installations block user traffic until all target Workers pass verification; the installer's health probes can still run. Routes and custom domains remain attached.
 
@@ -137,6 +137,8 @@ An upgrade completes after the new Workers pass health checks. If rollout fails,
 
 `platform rollback` restores a compatible earlier runtime without reversing database migrations. Pass its files with `--runtime`; if the installed version is custom, also supply that version with `--from-runtime`. Void refuses incompatible targets.
 
-Uninstall verifies remote ownership before removing anything. Data resources are retained unless you pass `--purge-data`. Workers, the Queues they use, R2, AI Gateway, DNS records, routes, custom domains, adopted resources, external PostgreSQL, and zones are always retained for manual review.
+Uninstall verifies remote ownership before removing anything. Data resources are retained unless you pass `--purge-data`. Workers, the Queues they use, R2, AI Gateway, DNS records, routes, custom domains, adopted resources, external PostgreSQL, and zones are retained for manual review.
+
+`--purge-resources` includes `--purge-data` and also deletes every other resource the installation created, including Workers, Queues, R2, AI Gateway, the platform DNS record, routes, custom domains, and installer-created Access resources. It removes only the Email Routing rules that send mail to the platform email gateway, and keeps zones, adopted resources, external PostgreSQL, other Email Routing settings, and API tokens. A route, custom domain, DNS record, or Access resource that no longer matches the installation's record is kept and listed. It refuses before any change while projects remain or resource reads are denied. Use the Edit permissions listed by `--plan`; read checks cannot verify them, so a denied deletion can stop uninstall after changes have begun. Rerun the same command to continue after an interruption, or after a plain or `--purge-data` uninstall stopped.
 
 See [Disable and Uninstall](../../guide/platform/installation/uninstall.md#remove-retained-resources) for the full removal policy and the cleanup order.

package/{skills/void/docs → docs}/reference/cli/platform-operations.md

@@ -54,6 +54,7 @@ void platform system asset-migrations [--page <n>] [--limit <n>]
 void platform system events [--page <n>] [--limit <n>]
 void platform system backfill-queue-tokens
 void platform system sandbox-drain [--cursor <opaque-cursor>]
+void platform system rotate-proxy-tokens [--project <id> | --all]
 ```
 
 `overview` shows platform totals and recent activity. `health` checks the configured services and database, and exits with a nonzero status if a check fails. `cli-versions` reports the CLI versions used by deployments.
@@ -64,6 +65,8 @@ void platform system sandbox-drain [--cursor <opaque-cursor>]
 
 `sandbox-drain` removes legacy tenant-owned Sandbox resources. Use `--plan` to preview and `--yes` to apply, then pass `nextCursor` as `--cursor` to continue. Application traffic stays paused during cleanup.
 
+`rotate-proxy-tokens` gives projects new platform credentials on their live Worker and the Workers kept for rollback, without a redeploy. Workers kept for rollback whose author can no longer deploy keep the old credentials. Use `--project <id>` for one project or `--all` for every project, with `--plan` to preview and `--yes` to apply. `--plan` alone shows every rotation that is still running. Each run does a bounded batch and the platform finishes the rest in the background; a rotation takes about 6 minutes per project, longer while a deploy is running. Use `--plan` to check progress until nothing is pending or failed. Running `--yes` again with `--project` or `--all` while a rotation is still running starts one more rotation for that project. When a rotation is finished, the previous credentials no longer work. Each rotation starts a new version of the project's live Worker, so WebSocket connections reconnect once.
+
 Use the [platform lifecycle commands](./platform-installation.md#lifecycle-commands) to maintain your installation's Workers.
 
 ## Hosted Workers {#operator-workers}

package/{skills/void/docs → docs}/reference/cli/platform-users.md

@@ -16,13 +16,13 @@ void platform user show <id>
 Use the same ID to change a plan, suspend or restore the account, or delete it:
 
 ```sh
-void platform user plan <id> <free|solo|pro|sponsored|custom>
+void platform user plan <id> <plan-id>
 void platform user suspend <id> [--reason <text>]
 void platform user restore <id>
 void platform user delete <id>
 ```
 
-Suspending a user blocks their applications. Deleting a user also deletes their project resources. A plan change updates resource limits while preserving any administrator suspension.
+Suspending a user blocks their applications, including scheduled jobs and queue consumers. While the account is suspended, each queue message is retried about once an hour, and each retry uses one of its queue's retries. Messages that run out of retries are dropped: after about 3 hours with the default of 3 retries, and at once for a queue with `maxRetries: 0`. Restore an account suspended by mistake promptly; queue delivery resumes within about an hour. Deleting a user also deletes their project resources. A plan change updates resource limits while preserving any administrator suspension.
 
 The last active administrator cannot be deleted or suspended. Both previews and
 actual mutations enforce this rule, including in the browser admin UI. Allowed

package/{skills/void/docs → docs}/reference/cli/platform.md

@@ -14,7 +14,9 @@ void platform use [id]
 void platform status [id]
 ```
 
-`use` and `status` auto-select the only configured platform; with multiple platforms they show a picker interactively and require an id or URL in non-interactive use. A project with a recorded platform URL keeps using that platform when the global default changes.
+`list` shows the currently selected platform first, followed by other saved platforms. For a platform with local installation records, its installation slug appears beside its name, such as `Cloudflare Void (cloudflare)`. Select it with `void platform use cloudflare`. For a connected platform without a local installation slug, use its printed API URL.
+
+`use` and `status` accept an installation slug, display name, saved ID, or API URL. If a slug or name matches several platforms, use the API URL to choose one. They auto-select the only configured platform; with multiple platforms they show a picker interactively and require an explicit selector in non-interactive use. A project with a recorded platform URL keeps using that platform when the global default changes.
 
 For a self-hosted installation, `status <installation-id>` prints locally saved
 lifecycle progress before checking the live API. The saved checkpoint may be out
@@ -25,7 +27,7 @@ checkpoint and exits with an error; it does not confirm current availability.
 
 Use `void platform` to administer the users and apps on your selected platform. Start with the [Platform Administration guide](../../guide/platform-administration.md) for signing in, giving people access, and investigating deployments.
 
-Every command below accepts `--connection <registered-id-or-url>` to select a platform and `--json` for structured output. Without `--connection`, Void uses `VOID_API_URL` if set, then the active platform connection. Application project files do not change this selection.
+Every command below accepts `--connection <slug-or-url>` to select a registered platform and `--json` for structured output. Display names and saved IDs also work. Without `--connection`, Void uses `VOID_API_URL` if set, then the active platform connection. Application project files do not change this selection.
 
 ### Making Changes {#making-changes}
 

package/{skills/void/docs → docs}/reference/cli/project.md

@@ -10,6 +10,7 @@ Show deployments for the configured target.
 
 - Void targets show recent hosted deployments; `[name]` looks up a project by slug and otherwise the linked project is used.
 - Cloudflare targets list Worker Versions, identify the active version, and show the recorded migration count. A project name is not accepted because the Worker name comes from `cloudflare.name` in `void.config.ts`.
+- Owners and admins also see a warning when the platform cannot finish [replacing the project's credentials](../../guide/project-collaboration.md#change-or-remove-access).
 
 ## `void project link [name]` {#void-project-link-name}
 
@@ -36,7 +37,7 @@ void project team accept <invitation-id>
 void project team decline <invitation-id>
 ```
 
-Project-scoped commands use `--project`, then `VOID_PROJECT`, then the linked project. Invitations can target only an email address already registered to a user on that platform; they do not create accounts or grant signup access. Only the invited account can accept or decline its invitation.
+Project-scoped commands use `--project`, then `VOID_PROJECT`, then the linked project. Invitations can target only an email address already registered to a user on that platform; they do not create accounts or grant signup access. Only the invited account can accept or decline its invitation. `list` shows the same credential warning as `void project status`.
 
 Readers can view the project but cannot deploy. Collaborators can deploy and manage deploy prerequisites. Project administrators can additionally manage domains, email destinations, GitHub configuration, and the project team. The owner alone can delete the project. See [Project Collaboration](../../guide/project-collaboration.md) for the full role boundaries.
 
@@ -137,7 +138,7 @@ void project logs --level error --range 12h
 void project logs --level error --filter websocket
 ```
 
-Logs include top-level `console.*` calls and uncaught errors captured by Cloudflare Tail. If you catch an error and save it only to your database, it won't appear here. Also log it with `console.error()` or `logger.error()` from `void/log`.
+Logs include top-level `console.*` calls and uncaught errors captured by Cloudflare Tail. If you catch an error and save it only to your database, it won't appear here. Also log it with `console.error()` or `logger.error()` from `void/log`. On hosted Void targets, pass the `Error` object itself to `console.error()`, as in `console.error('Save failed:', error)`, to see its stack trace under the log line. Logging only `error.message` shows no stack.
 
 For errors that never reach your Worker, such as edge routing errors or static site requests, use `void project requests --status 5xx`.
 
@@ -195,7 +196,7 @@ This command is hosted-only. Direct Cloudflare deploys are local operations and
 
 ## `void project delete [name]` {#void-project-delete-name}
 
-Permanently delete a hosted Void project and all its resources (databases, KV namespaces, R2 buckets, deployments). Requires typing the project slug to confirm.
+Permanently delete a hosted Void project and all its resources (databases, KV namespaces, R2 buckets, deployments). Requires typing the project slug to confirm; `--force` (`-f`) skips the prompt.
 
 If `[name]` is omitted, uses the linked project.
 
@@ -211,4 +212,4 @@ Purge all cached pages for the linked project. The edge cache will clear within
 
 If `--project` is provided, purges that project's cache instead of the linked project.
 
-This command is currently hosted-only. Direct Cloudflare cache purge fails closed with guidance.
+This command is hosted-only. For direct Cloudflare targets, redeploy or purge the configured ISR KV namespace yourself.

package/{skills/void/docs → docs}/reference/cli/secrets.md

@@ -14,8 +14,6 @@ List production secret names for the saved target. Secret values are never print
 
 ## `void secret put` {#void-secret-put}
 
-On hosted projects, secret writes and deletes return a retryable conflict while a deployment or rollback is in progress. Wait for that operation to finish and retry; the rejected operation leaves the stored secret unchanged.
-
 ```
 void secret put <name> [--project <name>]
 void secret put <name=value> [--project <name>]
@@ -27,7 +25,7 @@ Value input modes:
 - prompt (TTY): `void secret put API_KEY` (masked input)
 - stdin: `echo -n "abcd" | void secret put API_KEY`
 
-On a direct Cloudflare target, the value is sent to Cloudflare over stdin and stored as an encrypted Worker secret.
+On a direct Cloudflare target, the value is stored as an encrypted Worker secret.
 
 ## `void secret sync` {#void-secret-sync}
 
@@ -51,6 +49,8 @@ void secret delete <name> [--project <name>]
 
 Secret commands use the platform saved in `.void/project.json`. Hosted project resolution follows the same order as deploy (`--project`, env var, linked project). Direct Cloudflare targets reject `--project` and use the pinned root Cloudflare config.
 
+On hosted projects, secret writes and deletes return a retryable conflict while a deployment or rollback is in progress. Wait for that operation to finish and retry; the rejected operation leaves the stored secret unchanged.
+
 ## Env Schema {#env-schema}
 
 ### `void env check` {#void-env-check}

package/{skills/void/docs → docs}/reference/cli/setup.md

@@ -28,7 +28,7 @@ Resources recorded in `void.lock.json` without a matching definition appear sepa
 ## `void init` {#void-init}
 
 ```sh
-void init [--tsconfig] [--github] [--agents] [--git | --no-git]
+void init [--tsconfig] [--github] [--git | --no-git]
 ```
 
 Set up a new or existing Void project. In an empty directory, choose Vite+ or Vite, a framework, and a D1, PostgreSQL, MySQL, or Static Pages starter.
@@ -37,6 +37,12 @@ In an existing app, Void adds missing dependencies and scripts and updates the V
 
 The wizard also sets up TypeScript, agent instructions, environment declarations, and a deployment target. Choose Cloudflare, a Void platform, or skip deployment setup. If you skip sign-in, run `void connect` when you're ready. See [Quick Start](../../guide/quickstart.md).
 
+Every init run sets up coding agents. New projects get a minimal `AGENTS.md`
+pointing to `node_modules/void/docs/`. Existing projects prompt before the file
+is created, appended to, or updated; CI and non-interactive runs leave existing
+projects' instructions unchanged. Skills are linked for detected agents. See
+[Coding Agents](../../integrations/agents.md).
+
 Outside an existing repository or workspace package, Void offers to initialize Git. Use `--git` to initialize without a prompt or `--no-git` to skip it. CI requires `--git` to initialize. Workspace packages do not accept these flags.
 
 Run selected setup steps with:
@@ -44,10 +50,10 @@ Run selected setup steps with:
 | Flag         | Purpose                                                        |
 | ------------ | -------------------------------------------------------------- |
 | `--tsconfig` | Update TypeScript configuration, preserving existing settings. |
-| `--agents`   | Set up agent instructions and skills for detected agents.      |
 | `--github`   | Create the GitHub Actions deployment workflow.                 |
 
-These flags can be combined and skip the other wizard steps. Add `--git` if you also want Git initialization.
+These flags can be combined and skip the other wizard steps. Coding agent setup
+still runs. Add `--git` if you also want Git initialization.
 
 For Cloudflare workflows, add a `CLOUDFLARE_API_TOKEN` repository secret. PostgreSQL and MySQL apps also need `DATABASE_URL`.
 
@@ -60,11 +66,3 @@ void prepare
 ```
 
 Generates Void’s types and TypeScript configuration without starting the dev server or building the app. Run it after a fresh clone or before typechecking in CI.
-
-## Agent {#agent}
-
-### `void init --agents` {#void-init-agents}
-
-Adds Void instructions to `AGENTS.md` and links skills for detected coding agents. Existing instructions outside the Void block are preserved.
-
-If no supported agent is detected, `AGENTS.md` links to the bundled docs. See [Coding Agents](../../integrations/agents.md).

package/{skills/void/docs → docs}/reference/cli.md

@@ -56,7 +56,7 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void account login`              | Authenticate with a Void platform                                             |
 | `void cloudflare login`           | Authenticate with Cloudflare through Void                                     |
 | `void platform install`           | Install a company Void platform in Cloudflare                                 |
-| `void connect <url>`              | Connect the CLI to a Void platform                                            |
+| `void connect <url>`              | Connect the CLI to a Void platform; hostnames default to HTTPS                |
 | `void project link`               | Link directory to a project                                                   |
 | `void project logs`               | Show runtime logs from deployed project                                       |
 | `void project requests`           | Show request-level traffic (status, method, timing)                           |
@@ -73,7 +73,7 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void email allow <address>`      | Add a recipient and send a verification email                                 |
 | `void email disallow <address>`   | Remove a recipient from the allowlist                                         |
 | `void email domain`               | Send and receive at your own domain on a Cloudflare zone                      |
-| `void init`                       | Setup wizard for new or existing projects                                     |
+| `void init`                       | Set up a new or existing project, including coding agents                     |
 | `void migrate`                    | Convert legacy `void.json` and root Wrangler JSON/JSONC into `void.config.ts` |
 
 ## Binary Invocation {#binary-invocation}

package/{skills/void/docs → docs}/reference/config.md

@@ -297,6 +297,18 @@ Curated Cloudflare Workers configuration. `void init` pins `compatibility_date`
 
 `worker.vars` values must be strings. Root `.env` values override them during local development only. Production builds do not load `.env`, and reject any `worker.vars` name declared as a server key in `env.ts`. Use `void secret put` for production server values.
 
+`worker.limits.cpu_ms` sets the CPU time limit per request, from 1 to 300000 ms. On a Void platform, deploy fails if the limit exceeds the account plan; lower it in `void.config.ts` before retrying. Rollback instead caps the old limit at the current plan ceiling. On direct deploys, [Cloudflare enforces the value](https://developers.cloudflare.com/workers/platform/limits/#cpu-time): Workers Free allows up to 10 ms and Workers Paid up to 300000 ms per request.
+
+```json
+{
+  "worker": {
+    "limits": {
+      "cpu_ms": 30000
+    }
+  }
+}
+```
+
 ### `cloudflare`
 
 The complete Cloudflare Worker configuration for direct Cloudflare builds and deployment. Put custom bindings, `name`, `account_id`, routes, services, vars, migrations, and any other Cloudflare fields here. Void passes these fields through to the generated Cloudflare build configuration. Settings you edit here take precedence over values Void previously recorded in `void.lock.json`.
@@ -325,18 +337,6 @@ deploy: { cloudflare: { mode: 'atomic' } },
 
 This choice applies to subsequent `void deploy` runs. Atomic deployment sends traffic to the new Worker before Void checks readiness; a Durable Object class migration cannot be rolled back across its migration boundary. Use `--atomic` for a single deployment instead. `deploy` is a Void setting and is not passed to Cloudflare's Worker config.
 
-`worker.limits.cpu_ms` sets the CPU time limit per request, from 1 to 300000 ms. On a Void platform, deploy fails if the limit exceeds the account plan; lower it in `void.config.ts` before retrying. Rollback instead caps the old limit at the current plan ceiling. On direct deploys, [Cloudflare enforces the value](https://developers.cloudflare.com/workers/platform/limits/#cpu-time): Workers Free allows up to 10 ms and Workers Paid up to 300000 ms per request.
-
-```json
-{
-  "worker": {
-    "limits": {
-      "cpu_ms": 30000
-    }
-  }
-}
-```
-
 ### `routing`
 
 Routing and edge configuration for headers, redirects, rewrites, and caching.
@@ -434,7 +434,7 @@ ISR revalidation TTL in seconds, either globally or per path. See [Revalidation]
 
 #### `routing.revalidateQueryAllowlist`
 
-Query parameters that participate in ISR variant keys for dispatch rewrites. Keys are source URL patterns, values are query parameter names to keep. When omitted, rewritten ISR cache keys drop every incoming query parameter to avoid unbounded cache fanout.
+Query parameters to keep in ISR cache keys. Keys are source URL patterns, values are query parameter names to keep. The listed parameters are part of the cache key for every request to a matching path; all other query parameters are left out of the key. When omitted, ISR cache keys drop every incoming query parameter to avoid unbounded cache fanout.
 
 ```json
 {

package/{skills/void/docs → docs}/reference/resource-inference.md

@@ -17,6 +17,7 @@ Void automatically detects which Cloudflare resources your project uses by scann
 | `SANDBOX`        | Managed Sandbox capability | `import { getSandbox } from "void/sandbox"`                                                                                                                      | `getSandbox()`; native Cloudflare also exposes `env.SANDBOX` / `c.env.SANDBOX` |
 | Auth             | none                       | `import { ... } from "void/auth"` or `import { auth } from "void/client"` / `void/client/react` / `void/client/vue` / `void/client/svelte` / `void/client/solid` | none                                                                           |
 | `QUEUE_*`        | `Queue`                    | `import { queues } from "void/queues"`                                                                                                                           | `env.QUEUE_*`                                                                  |
+| `VOID_LIVE`      | `DurableObjectNamespace`   | `import { defineLiveStream } from "void/live"`                                                                                                                   | n/a                                                                            |
 | filename-derived | `DurableObjectNamespace`   | A default-exported `defineDurableState()` module in `durable-objects/`                                                                                           | n/a                                                                            |
 
 Auth detection also triggers when importing the `auth` specifier from `void/client` or a framework-specific client subpath such as `void/client/react` (but not when importing only `fetch`).
@@ -79,22 +80,7 @@ Paths are relative to the project root. When `inference.scanDirs` is set, it rep
 
 ## Explicit Binding Overrides
 
-Override individual bindings when inference does not match your setup:
-
-```json
-{
-  "inference": {
-    "bindings": {
-      "db": true,
-      "kv": true,
-      "storage": false,
-      "ai": false
-    }
-  }
-}
-```
-
-Explicit values override only their named bindings. Omitted bindings continue to be inferred, so setting `kv` does not disable storage, auth, or other features. Auth and checked-in migrations still require a database even when `db` is `false`.
+Use [`inference.bindings`](./config.md#inference-bindings) to enable, disable, or rename a binding when inference does not match your setup. It overrides only the bindings you name; the rest are still inferred.
 
 ## File Types
 

package/package.json

@@ -1,6 +1,12 @@
 {
   "name": "void",
-  "version": "0.25.0",
+  "version": "0.26.1",
+  "description": "Full-stack framework and deployment CLI for Cloudflare Workers, powered by Vite.",
+  "homepage": "https://void.cloud",
+  "bugs": {
+    "url": "https://github.com/voidzero-dev/void/issues"
+  },
+  "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/voidzero-dev/void.git",
@@ -11,6 +17,7 @@
   },
   "files": [
     "dist",
+    "docs",
     "schema.json",
     "skills",
     "AGENTS_TEMPLATE.md",
@@ -331,43 +338,40 @@
     }
   },
   "dependencies": {
-    "@cloudflare/build-output-utils": "0.8.5",
-    "@cloudflare/codemods": "0.4.0",
-    "@cloudflare/config": "0.23.0",
+    "@cloudflare/build-output-utils": "^0.9.0",
+    "@cloudflare/codemods": "^0.4.2",
+    "@cloudflare/config": "^0.24.1",
     "@cloudflare/sandbox": "1.0.0",
-    "@cloudflare/vite-plugin": "1.62.5",
-    "@cloudflare/workers-auth": "0.12.0",
-    "@cloudflare/workers-types": "^4.20260702.1",
-    "@napi-rs/keyring": "2.1.0",
-    "@void/deploy-cloudflare": "0.25.0",
-    "@void/deploy-core": "0.25.0",
-    "@void/edge": "0.25.0",
-    "@void/isr": "0.25.0",
-    "@void/platform": "0.25.0",
-    "acorn": "^8.18.0",
+    "@cloudflare/vite-plugin": "^1.63.1",
+    "@cloudflare/workers-auth": "^0.13.1",
+    "@cloudflare/workers-types": "^5.20261009.1",
+    "@napi-rs/keyring": "^2.1.0",
+    "@void/deploy-cloudflare": "0.26.1",
+    "@void/deploy-core": "0.26.1",
+    "@void/edge": "0.26.1",
+    "@void/isr": "0.26.1",
+    "@void/platform": "0.26.1",
     "better-auth": "^1.7.7",
     "better-sqlite3": "^13.0.3",
     "blake3-jit": "^1.1.0",
-    "cf": "1.0.0-beta.12",
+    "cf": "^1.0.0-beta.13",
     "drizzle-arktype": "^0.1.3",
     "drizzle-kit": "^0.31.11",
     "drizzle-orm": "^0.45.3",
     "drizzle-valibot": "^0.4.2",
     "drizzle-zod": "^0.8.3",
     "email-validator": "^2.0.4",
-    "es-module-lexer": "^3.0.2",
     "hono": "^4.13.13",
     "ignore": "^7.0.12",
     "jiti": "^2.7.0",
-    "jsonc-parser": "3.3.1",
-    "mime": "4.1.0",
-    "miniflare": "5.20261001.0-alpha",
+    "jsonc-parser": "^3.3.1",
+    "mime": "^4.1.0",
+    "miniflare": "5.20261006.1-alpha",
     "minimatch": "^10.2.6",
-    "mysql2": "3.24.5",
-    "pg": "8.23.1",
-    "postal-mime": "^4.0.4",
-    "proper-lockfile": "^4.1.2",
-    "undici": "8.11.2"
+    "mysql2": "^3.24.5",
+    "pg": "^8.23.1",
+    "postal-mime": "^4.0.5",
+    "proper-lockfile": "^4.1.2"
   },
   "devDependencies": {
     "@electric-sql/pglite": "0.5.8",
@@ -375,12 +379,12 @@
     "@types/node": "^26.6.4",
     "@types/pg": "^8.23.1",
     "@types/proper-lockfile": "^4.1.4",
-    "@voidzero-dev/vite-plus-prompts": "0.0.0",
+    "@voidzero-dev/vite-plus-prompts": "1.1.0",
     "arktype": "^2.2.7",
     "ci-info": "^4.4.0",
     "estree-walker": "^3.0.3",
     "fast-wrap-ansi": "^0.2.2",
-    "magic-string": "^1.4.2",
+    "magic-string": "^1.4.3",
     "ofetch": "2.0.0-alpha.3",
     "pathslash": "^0.1.0",
     "pglite-server": "0.1.5",
@@ -388,12 +392,12 @@
     "tinyglobby": "^0.2.17",
     "typescript": "7.0.2",
     "valibot": "^1.5.0",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0",
-    "vite-plus": "1.0.0",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.1.0",
+    "vite-plus": "1.1.0",
     "zod": "^4.6.5"
   },
   "peerDependencies": {
-    "@void/md": "0.25.0",
+    "@void/md": "0.26.1",
     "arktype": ">=2.0.0",
     "valibot": ">=1.0.0-beta.7",
     "vite": "^8.0.0",
@@ -417,7 +421,7 @@
     "node": ">=24.21.0"
   },
   "scripts": {
-    "build": "node scripts/sync-skill-docs.mjs && vp pack",
+    "build": "node scripts/sync-docs.mjs && vp pack",
     "dev": "vp pack --watch",
     "typecheck": "tsc --noEmit --rootDir ../.."
   }

package/schema.json

@@ -212,7 +212,7 @@
         },
         "revalidateQueryAllowlist": {
           "type": "object",
-          "description": "Query parameters that participate in ISR variant keys for dispatch rewrites. Keys are source URL patterns; values are arrays of query parameter names. When omitted, rewritten ISR drops every query parameter from the variant key.",
+          "description": "Query parameters that are part of the ISR cache key for every request to a matching path. Keys are source URL patterns; values are arrays of query parameter names. All other query parameters are left out of the key. When omitted, ISR drops every query parameter from the cache key.",
           "patternProperties": {
             "^(\\/|\\*$)": {
               "type": "array",

package/skills/migrate-vite-cloudflare-to-void/SKILL.md

@@ -9,7 +9,10 @@ Read the app's package manifest, Vite config, Worker entry, Cloudflare config,
 and migrations. Identify its framework, endpoints, bindings, and deployed Worker
 before changing them.
 
-Use the bundled guides under `../void/docs/`:
+Use the bundled guides under `node_modules/void/docs/`. Without a local Void
+installation, use `../../docs/` relative to this skill's real directory in the
+Void package, following any symlink. If the skill was copied without the package,
+use the guides at [https://void.cloud](https://void.cloud) instead:
 
 - `integrations/cloudflare.md` for existing Worker handoff and configuration.
 - `integrations/frameworks/overview.md` and the matching framework guide when