void 0.23.0 → 0.25.0

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

@@ -8,32 +8,33 @@ outline: deep
 void platform install [options] [--yes]
 ```
 
-| Option                            | Purpose                                                                              |
-| --------------------------------- | ------------------------------------------------------------------------------------ |
-| `--name <slug>`                   | Installation name used in `void-<name>-<role>` resource names; choose an unused name |
-| `--display-name <name>`           | Human-readable platform name                                                         |
-| `--account <id>`                  | Cloudflare account id                                                                |
-| `--auth-config <path>`            | Login methods, signup policy, and environment references for provider secrets        |
-| `--login-methods <methods>`       | Comma-separated `github`, `google`, `oidc`, or `cloudflare-access` login methods     |
-| `--access-protection`             | Protect the platform UI and APIs with Cloudflare Access                              |
-| `--no-access-protection`          | Skip Cloudflare Access protection                                                    |
-| `--hyperdrive <create\|id>`       | Create Hyperdrive or use the specified existing configuration                        |
-| `--application-domain <domain>`   | Base domain for deployed apps                                                        |
-| `--workers-dev`                   | Explicit testing mode; add an application domain later                               |
-| `--zone <domain>`                 | Cloudflare zone containing the application domain                                    |
-| `--dedicated-zone`                | Add zone-wide catch-all routes; valid only when the app domain is the whole zone     |
-| `--no-dedicated-zone`             | Skip zone-wide application catch-all routes                                          |
-| `--control-plane-domain <domain>` | Optional API custom hostname; defaults to `workers.dev`                              |
-| `--no-control-plane-domain`       | Use the default `workers.dev` API hostname                                           |
-| `--dashboard-url <origin>`        | HTTPS origin of an optional dashboard deployed separately                            |
-| `--plan`                          | Resolve and print a read-only plan                                                   |
-| `--resume`                        | Continue the matching checkpointed installation                                      |
-| `--runtime <path>`                | Deploy a locally built, integrity-checked runtime directory                          |
-| `--yes`                           | Acknowledge Cloudflare changes in non-interactive use                                |
-
-For a first installation, follow [Install a Void Platform](../../guide/self-hosted-platform.md). The interactive installer recommends using a domain and offers **Use workers.dev for testing** as a visible alternative. Void creates the platform infrastructure and tables. External PostgreSQL and a configured login method are required in either mode; GitHub OAuth is the default login choice, not a requirement. `--workers-dev` skips zone/DNS/certificate operations and cannot be combined with `--application-domain`, `--zone`, or `--dedicated-zone`.
-
-Read-only plans, workers.dev installations with the default API hostname, and supported lifecycle operations can use Cloudflare browser login and the system keychain. Installation that writes DNS or creates a zone needs an explicit management token through `CLOUDFLARE_API_TOKEN` or `CF_API_TOKEN`.
+| Option                                    | Purpose                                                                              |
+| ----------------------------------------- | ------------------------------------------------------------------------------------ |
+| `--name <slug>`                           | Installation name used in `void-<name>-<role>` resource names; choose an unused name |
+| `--display-name <name>`                   | Human-readable platform name                                                         |
+| `--account <id>`                          | Cloudflare account id                                                                |
+| `--auth-config <path>`                    | Login methods, signup policy, and environment references for provider secrets        |
+| `--login-methods <methods>`               | Comma-separated `github`, `google`, `oidc`, or `cloudflare-access` login methods     |
+| `--access-protection`                     | Protect the platform UI and APIs with Cloudflare Access                              |
+| `--no-access-protection`                  | Skip Cloudflare Access protection                                                    |
+| `--app-access <public\|platform\|custom>` | Public apps, the platform's Access policy, or separately selected app policies       |
+| `--hyperdrive <create\|id>`               | Create Hyperdrive or use the specified existing configuration                        |
+| `--application-domain <domain>`           | Base domain for deployed apps                                                        |
+| `--workers-dev`                           | Explicit testing mode; add an application domain later                               |
+| `--zone <domain>`                         | Cloudflare zone containing the application domain                                    |
+| `--dedicated-zone`                        | Add zone-wide catch-all routes; valid only when the app domain is the whole zone     |
+| `--no-dedicated-zone`                     | Skip zone-wide application catch-all routes                                          |
+| `--control-plane-domain <domain>`         | Optional API custom hostname; defaults to `workers.dev`                              |
+| `--no-control-plane-domain`               | Use the default `workers.dev` API hostname                                           |
+| `--dashboard-url <origin>`                | HTTPS origin of an optional dashboard deployed separately                            |
+| `--plan`                                  | Preview Cloudflare changes and save installation choices locally                     |
+| `--resume`                                | Continue the matching checkpointed installation                                      |
+| `--runtime <path>`                        | Deploy a locally built, integrity-checked runtime directory                          |
+| `--yes`                                   | Acknowledge Cloudflare changes in non-interactive use                                |
+
+For a first installation, follow [Install a Void Platform](../../guide/self-hosted-platform.md). The interactive installer recommends using a domain and offers **Use workers.dev for testing** as a visible alternative. Void creates the platform infrastructure and tables. External PostgreSQL and a configured login method are required in either mode. Select all login methods you want to enable; none are selected initially. Non-interactive installation defaults to GitHub when no login configuration is supplied. `--workers-dev` skips zone/DNS/certificate operations and cannot be combined with `--application-domain`, `--zone`, or `--dedicated-zone`.
+
+Read-only plans, workers.dev installations with the default API hostname, and supported lifecycle operations can use Cloudflare browser login and the system keychain. Installation that writes DNS or creates a zone needs a management API token. The interactive installer guides you to create one and paste it into a masked prompt; scripts use `CLOUDFLARE_API_TOKEN` or `CF_API_TOKEN`.
 
 The installed platform needs a separate runtime token to provision resources for apps. The interactive installer prompts for it and the other setup values. For non-interactive installs, inject the variables listed in [Install from CI](../../guide/platform/installation/ci.md).
 
@@ -45,10 +46,24 @@ path, query, or fragment. Void permits that origin's login callbacks and saves
 it for later maintenance; it does not deploy a dashboard Worker. Omission keeps
 an existing installation's saved dashboard origin.
 
-`--plan` previews resource names, login methods, callback URLs, and credential requirements. Run the install or resume command printed at the end to continue. For login configuration, use either `--auth-config` or `--login-methods` with the Access protection flags.
+`--plan` previews resource names, login methods, default app access, the login callback URL, database configuration, and credential requirements. An existing Hyperdrive shows its database and configuration name. Setup links are shown during guided credential setup. Completed previews save nonsecret installation choices locally. Rerun `void platform install` to choose a saved plan and review a fresh check of Cloudflare state, or run the install or resume command printed at the end. Started installations use their saved checkpoints; completed installations are excluded from the chooser. For login configuration, use either `--auth-config` or `--login-methods` with the Access protection flags.
+
+App access is configured before traffic opens. With platform protection enabled,
+the installer recommends reusing its company policy; otherwise it defaults to
+public apps. Use `--app-access custom` to select separate hosting-account policies.
+Public apps in a Default-Deny account receive scoped public Access rules. The
+installer explains and collects the encrypted management credential when needed;
+scripts supply `VOID_PLATFORM_APP_ACCESS_TOKEN` or `appAccess.tokenEnv` in the
+authentication file. Upgrades preserve administrator settings.
 
 New resources use `void-<name>-<role>` names; choose an unused installation name. The installer opens setup pages for missing credentials and reuses values already supplied.
 
+During Access setup, choose existing company policies or **Create new** for manual
+setup instructions and an account dashboard link. After you save the policy and
+confirm completion, Void reloads the list so you can select it and continue in the
+same run. **Refresh list** reloads policies created in another window. Your
+identity-provider choice and still-available policy selections are retained.
+
 Installation progress and partial credentials are saved encrypted locally. Rerun the installer to continue unfinished setup, or pass `--resume --name <id>`. Use lifecycle commands for completed installations.
 
 Use an empty PostgreSQL database dedicated to the installation. You can correct a failed initial connection, but after the database is claimed or Hyperdrive is provisioned, commands reject a different URL.

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

@@ -17,11 +17,7 @@ void platform deployment migrate-assets <id> [--cursor <cursor>] [--plan|--yes]
 
 Cancellation applies while a deployment is pending, uploading, migrating, or prerendering, and can be requested again while it is canceling. A deployment that has begun switching traffic, is compensating for a failure, or has finished cannot be canceled through this command.
 
-`migrate-assets` copies legacy assets to scoped R2 storage, verifies their contents, and updates each batch only after all its assets are verified. Original assets remain in place, and application traffic stays on the same deployment. Upgrade the platform runtime before using this command. Migrate both active deployments and retained rollback deployments before removing support for older asset storage.
-
-Use `--plan` to preview the first batch. Applying authorizes all remaining batches for that deployment; the CLI previews each batch and prints its result, including `nextCursor`. With `--json`, results are JSON Lines. If a later batch fails or the command is interrupted, resume with the cursor from the last successful result. An ambiguous request is never retried automatically; inspect the deployment before resuming. A completed migration reports `complete: true` and `nextCursor: null`.
-
-Use [`void platform system asset-migrations`](#operator-system) to find deployments requiring migration. Inspect every inventory page, migrate each deployment with `needsMigration` greater than zero, then inspect every page again. Include retained rollback deployments and stored bundles. Investigate rows marked `invalid` before considering migration complete. Keep the older asset readers until the full inventory is valid and no protected deployment needs migration.
+`migrate-assets` copies a deployment's legacy assets to scoped R2 storage without changing application traffic. Use `--plan` to preview and `--cursor` to resume from a successful batch. Original assets remain in place.
 
 Read its runtime logs with:
 
@@ -44,7 +40,7 @@ void platform build logs <id> [--since <sequence>] [--limit <n>] [--follow]
 
 Build logs start at sequence `0` and return up to 500 lines. Use the returned `lastSeq` as `--since` to continue; `--limit` accepts 1 to 500. Container log retrieval requires managed builds to be enabled. GitHub Actions builds return an external log URL.
 
-Following waits for the final logs after the build becomes terminal. If completion cannot be confirmed within two minutes, the command exits with an error. Older builds without a completion signal may wait for 30 seconds without new lines before following stops.
+Following waits for the final logs after the build becomes terminal. If completion cannot be confirmed within two minutes, the command exits with an error.
 
 ## System {#operator-system}
 
@@ -62,11 +58,11 @@ void platform system sandbox-drain [--cursor <opaque-cursor>]
 
 `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.
 
-`asset-migrations` inventories active deployments, retained rollback deployments, and deployments with stored bundles. It reports their asset counts, `needsMigration`, and an `invalid` flag for unreadable metadata. Read all pages using the response's pagination fields. Migrate each deployment with `needsMigration` greater than zero through [`deployment migrate-assets`](#operator-deployments), then rerun the full inventory. Migration keeps the original assets; removing those assets or their older readers requires separate verification.
+`asset-migrations` inventories stored deployment assets and reports `needsMigration` and `invalid` counts. Use the response's pagination fields to read all entries.
 
 `events` shows the administrator, target, and outcome of changes. A pending event means the outcome has not been recorded. Previews and session login/logout do not create these events. `backfill-queue-tokens` repairs older queue entries that are missing authentication tokens and supports `--plan` before applying the repair.
 
-Use `sandbox-drain` when an upgrade from the legacy tenant-owned Sandbox runtime asks you to finish cleanup. Preview with `--plan`; pass the returned `nextCursor` as `--cursor` to inspect later pages. Apply with `--yes` and rerun until it reports `complete: true`, then rerun the interrupted upgrade. Application traffic stays paused during cleanup, while administrator login remains available. The completed upgrade enables the current managed Sandbox controller automatically.
+`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.
 
 Use the [platform lifecycle commands](./platform-installation.md#lifecycle-commands) to maintain your installation's Workers.
 

package/skills/void/docs/reference/cli/platform-zero-trust.md

@@ -26,6 +26,20 @@ void platform zero-trust project-public <project-id>
 void platform zero-trust project-reconcile <project-id>
 ```
 
+New installations configure app access in `void platform install`. Use these
+commands to inspect or change it later. To configure or renew public-only rules
+for a Default-Deny account, omit identity policies and use `--public-apps`:
+
+```sh
+printf '%s' "$ACCESS_API_TOKEN" | void platform zero-trust configure \
+  --public-apps --token-stdin --yes
+```
+
+Add `--existing-projects public` when enabling from a disabled configuration.
+Public-only rules cannot be combined with protected project choices. To switch an
+already protected configuration to public-only rules, first disable it; Access may
+block traffic during that transition in a Default-Deny account.
+
 Mutations support `--plan`, `--yes`, and `--timeout`; use `--plan` instead of
 `--yes` to inspect this change without applying it. The Access management token
 is accepted only on standard input. Zero Trust uses the Cloudflare account that

package/skills/void/docs/reference/cli/platform.md

@@ -16,6 +16,11 @@ 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.
 
+For a self-hosted installation, `status <installation-id>` prints locally saved
+lifecycle progress before checking the live API. The saved checkpoint may be out
+of date. If live discovery fails during maintenance, the command still shows that
+checkpoint and exits with an error; it does not confirm current availability.
+
 ## Operator commands {#operator-commands}
 
 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.

package/skills/void/docs/reference/config.md

@@ -156,7 +156,7 @@ Configuration for the [email integration](../guide/email.md).
 
 During development, `email.from` is the default sender in the local inbox. On a Void platform, use your project's shared sender or registered domain.
 
-For direct Cloudflare deployment, this address selects the mail domain and default sender. Use a zone or subdomain in your account; an existing mail provider's MX records are preserved. See [Email setup](../guide/email/domains.md#your-own-cloudflare-account).
+For direct Cloudflare deployment, this address selects the mail domain and default sender. Use a zone or subdomain in your account; an existing mail provider's MX records are preserved. Without `email.from`, Void skips automatic setup and preserves authored `cloudflare.send_email` bindings and `cloudflare.addresses`; check their readiness yourself. `--require-email` still refuses deployment when automatic setup cannot be verified. See [Email setup](../guide/email/domains.md#your-own-cloudflare-account).
 
 ### `head`
 

package/skills/void/docs/reference/resource-inference.md

@@ -27,7 +27,7 @@ Durable state is inferred from files in `durable-objects/`. For example, `durabl
 
 ### Standard mode
 
-When using Void's built-in routing (no meta-framework), these directories are scanned:
+Native Void apps scan these directories by default. With [`sourceDir`](./config.md#sourcedir) configured, Void scans that source tree instead:
 
 | Directory     | Contains                                    |
 | ------------- | ------------------------------------------- |
@@ -36,10 +36,12 @@ When using Void's built-in routing (no meta-framework), these directories are sc
 | `queues/`     | Queue consumers                             |
 | `pages/`      | Page components and `.server.ts` companions |
 | `crons/`      | Scheduled job handlers                      |
+| `email/`      | Inbound email handlers                      |
+| `src/`        | Application source                          |
 
 ### Framework mode
 
-When a meta-framework is detected (TanStack Start, React Router, SvelteKit, Nuxt, or Astro), a broader set of directories is scanned instead:
+For [supported meta frameworks](../integrations/frameworks/overview.md), Void scans these directories:
 
 | Directory | Contains                |
 | --------- | ----------------------- |
@@ -47,17 +49,18 @@ When a meta-framework is detected (TanStack Start, React Router, SvelteKit, Nuxt
 | `app/`    | Framework app directory |
 | `routes/` | Framework routes        |
 | `server/` | Server-side code        |
+| `pages/`  | Framework pages         |
+| `crons/`  | Scheduled job handlers  |
+| `queues/` | Queue consumers         |
 
-Framework detection checks `package.json` for `@tanstack/react-start`, `@react-router/dev`, `@sveltejs/kit`, `nuxt`, or `astro` in dependencies.
-
-For SvelteKit, Nuxt, and Astro, add `voidPlugin()` to the framework's Vite config to enable inference during dev. See [Frameworks Integration](../integrations/frameworks/overview.md) for setup details.
+Framework detection uses `package.json` dependencies and dev dependencies. Add `voidPlugin()` to your framework's Vite config to enable inference during development. The integration guides show the setup for each framework.
 
 ### Always scanned
 
 Regardless of mode, these are always checked:
 
 - **SSR entry** such as `src/main.ssr.ts`, for SSR apps that access bindings during rendering
-- **`src/`**, which is always scanned for auth imports unless it is already in the scan list for framework mode
+- **Application source** in `src/` or your configured `sourceDir`, including resource and auth imports
 - **`durable-objects/`**, which is scanned for typed Durable Object state modules in native Void apps
 
 ## Custom Scan Directories
@@ -72,7 +75,7 @@ If your project organizes code in non-standard directories, you can override whi
 }
 ```
 
-Paths are relative to the project root. When `inference.scanDirs` is set, it replaces the default directories entirely. Defaults for the current mode are not merged in. The SSR entry and `src/` auth scan still apply either way.
+Paths are relative to the project root. When `inference.scanDirs` is set, it replaces the default directories entirely. The SSR entry and application source scan still apply.
 
 ## Explicit Binding Overrides
 
@@ -95,4 +98,4 @@ Explicit values override only their named bindings. Omitted bindings continue to
 
 ## File Types
 
-Inference scans files matching `**/*.{ts,tsx,mts,js,jsx,mjs}` within each directory. Non-JS files (CSS, HTML, images) are ignored.
+Inference scans `.ts`, `.tsx`, `.mts`, `.js`, `.jsx`, `.mjs`, and Astro frontmatter. Put server resource imports in these files or a page's `.server.ts` companion; Vue and Svelte component files are not scanned directly.

package/dist/auth-CCjt0hcq.mjs

@@ -1,2 +0,0 @@
-import { a as getApiUrl, h as runPlatformLogin, s as getSiteDomain } from "./auth-CSkdO2Bb.mjs";
-export { getApiUrl, getSiteDomain, runPlatformLogin };

package/dist/cf-build-output-_0HNWysu.mjs

@@ -1,2 +0,0 @@
-import { t as prepareCfBuildOutput } from "./cf-build-output-BPqOT964.mjs";
-export { prepareCfBuildOutput };

package/dist/client-Cu7jWiF1.mjs

@@ -1,2 +0,0 @@
-import { n as PlatformClient } from "./client-RV8NVeB8.mjs";
-export { PlatformClient };

package/dist/deploy-bjXdFCtn.mjs

@@ -1,2 +0,0 @@
-import { A as parseRootWranglerConfig, J as runDeploy, f as checkWranglerMigrationApplySet } from "./deploy-DzAIwqNU.mjs";
-export { checkWranglerMigrationApplySet, parseRootWranglerConfig, runDeploy };

package/dist/dist-BuDuKZJv.mjs

@@ -1,2 +0,0 @@
-import { B as text, I as select, W as isCancel, j as log } from "./dist-CTBk70IR.mjs";
-export { isCancel, log, select, text };