void 1.1.0 → 1.1.11

package/docs/guide/remote-dev.md

@@ -59,6 +59,8 @@ When the dev server starts with remote mode active, it prints:
 
 - **Network latency:** each binding call makes a network request, so responses may be slower than local development.
 - **R2 multipart uploads:** `createMultipartUpload()` and `resumeMultipartUpload()` are not supported in remote mode.
+- **R2 range and conditional reads:** in remote mode, `get()` ignores request headers passed as `range` or `onlyIf` and returns the whole object. For example, `get(key, { range: request.headers, onlyIf: request.headers })` returns the whole object when the request has a `Range` or `If-None-Match` header. `get()` throws when `range` or `onlyIf` is an object that asks for a byte range or a condition, such as `{ offset: 0, length: 100 }` or `{ etagMatches: etag }`.
 - **R2 conditional writes:** `put(..., { onlyIf })` requires an updated platform and project deployment. Failed preconditions return `null`.
+- **R2 metadata and list options:** custom metadata, HTTP metadata, and `list()` with `delimiter`, `startAfter`, or `include` require an updated project deployment. Without one, `list()` with these options and `put()` with metadata other than `contentType` throw an error.
 - **D1 dump:** `db.dump()` is not supported in remote mode.
 - **D1 batches:** `db.batch()` requires an updated platform and project deployment.

package/docs/guide/websockets.md

@@ -151,7 +151,7 @@ Messages are JSON events. Raw string and binary messages are not supported.
 
 When Void auth is enabled, every WebSocket hook receives the current user as `ctx.user`, or `null` for an anonymous connection. Use `onBeforeConnect` to reject unauthenticated clients.
 
-Connections from another origin are anonymous unless that origin is in your auth `trustedOrigins`. If you read your own cookies from `ctx.request`, check its `Origin` header yourself.
+Connections from another origin are anonymous unless that origin is in your auth `trustedOrigins`. If you read your own cookies from `ctx.request` in `onBeforeConnect`, check its `Origin` header yourself.
 
 `ctx.user` is resolved when the socket connects and stays the same for that connection, even if the user later signs out or the session is revoked. For actions that must respect a ban or role change, re-check your own records in `onMessage` and close the connection with `ctx.connection.close()` in rooms or `ctx.socket.close()` in `defineWebSocket()`.
 
@@ -173,7 +173,7 @@ Every hook receives a context with:
 - `ctx.id`: deterministic route instance id
 - `ctx.params`: matched route params
 - `ctx.user`: resolved auth user or `null`
-- `ctx.request`
+- `ctx.request`: the HTTP request in `onBeforeConnect`, `onConnect`, and `onRequest`. In `onMessage` and `onClose`, it is a placeholder without headers, cookies, or query. To keep request data, save it in `onConnect` with `ctx.connection.setState()` in rooms or `ctx.socket.setState()` in `defineWebSocket()`. Read it later from `ctx.connection.state` or `ctx.socket.state`.
 - `ctx.env`
 - `ctx.storage`
 

package/docs/index.md

@@ -4,36 +4,92 @@ theme: dark
 
 hero:
   name: Void
-  text: Full-stack apps with Vite
-  tagline: Add server routes, data, and Cloudflare resources to your app. Deploy with one command.
+  text: Build with Vite. Deploy with Void.
+  tagline: Void is a CLI, platform, and full-stack SDK that unifies building & deploying apps.
   actions:
     - theme: brand
       text: Get Started
       link: ./guide/
-  image:
-    src: /hero.svg
-    alt: Void deployment platform
-
+    - theme: alt
+      text: View on GitHub
+      link: https://github.com/voidzero-dev/void
+    - theme: alt
+      text: Read the Announcement
+      link: https://blog.cloudflare.com/deploy-with-void
 features:
-  - iconify: lucide:terminal
-    title: Deploy with One Command
-    details: '`void deploy` builds your app, provisions resources, applies migrations, and deploys it.'
   - iconify: lucide:layers
-    title: Full-Stack Features
-    details: Use a database, KV, object storage, AI, authentication, queues, and cron jobs as your app needs them.
+    visual: stack
+    title: Full-Stack, Inferred
+    details: Import what you need. Void provides local resources and provisions them on deploy.
+    highlights:
+      - Server routes and authentication
+      - Databases, storage, and AI
+      - Queues and scheduled jobs
+    guide:
+      text: Explore the SDK
+      link: /guide/
   - iconify: lucide:wand-sparkles
-    title: Resources from Your Code
-    details: Void detects supported resources from your imports and provisions them on deploy. Configure existing resources explicitly.
-  - iconify: lucide:shield-check
-    title: Deploy with Confidence
-    details: Run on Cloudflare Workers with checked migrations, versioned deployments, logs, and rollback.
+    visual: resources
+    title: Typed from Database to UI
+    details: Share types across your database, server loaders, and page components.
+    highlights:
+      - Types from your database schema
+      - Typed loaders, actions, and APIs
+      - Server code stays on the server
+    guide:
+      text: Explore Type Safety
+      link: /guide/type-safety
   - iconify: lucide:blocks
-    title: Choose Your Framework
-    details: Use React, Vue, Svelte, Solid, or a supported Vite framework with SSR, SSG, ISR, and islands.
-  - iconify: lucide:bot
-    title: Work with Coding Agents
-    details: Void provides project instructions and skills to help coding agents build and deploy your app.
-
+    visual: frameworks
+    title: Use Your Favorite Framework
+    details: Build with Void's adapters or keep your existing Vite framework.
+    highlights:
+      - Ships with adapters for Async React, Vue, Svelte, and Solid
+      - Supports TanStack Start, SvelteKit, Nuxt, and more
+      - Build APIs, SPAs, or server-rendered pages
+    guide:
+      text: Explore Frameworks
+      link: /integrations/frameworks/overview
+platform_features:
+  - id: platform-ai-coding
+    iconify: lucide:bot
+    title: Secure Vibe Coding for Your Team
+    details: Let your team build and deploy with coding agents while admins retain control of Cloudflare access.
+    highlights:
+      - Enable non-technical teammates to build their own apps
+      - Keep Cloudflare credentials with your admin team
+      - Deploy prototypes fast and share apps for feedback
+    guide:
+      text: Explore team deployments
+      link: /guide/self-hosted-platform
+    visual: rive
+    image_alt: Animated illustration of apps being built for a team
+  - id: platform-control-plane
+    iconify: lucide:panels-top-left
+    visual: resources
+    title: Control Plane for Managing Apps
+    details: Manage users, projects, deployments, and platform health from the admin UI or CLI.
+    highlights:
+      - Manage users and project access & resources
+      - Inspect deployments, logs, and rollbacks
+      - Monitor platform health and usage
+    guide:
+      text: Platform administration
+      link: /guide/platform-administration
+    image_alt: List of Void platform commands for access, builds, invitations, and administration
+  - id: platform-security
+    iconify: lucide:shield-check
+    title: Bring your Own Security
+    details: Fork and customize your own Void platform based on your team's security standards.
+    highlights:
+      - Manage access through Cloudflare Access, Google, GitHub, or OIDC
+      - Control who can sign in and deploy
+      - Protect projects with your access policies
+    guide:
+      text: Configure platform access
+      link: /guide/platform/administration/access
+    visual: rive
+    image_alt: Animated illustration of self-hosted platform security
 footer_heading: Build with Vite. Deploy with Void.
 footer_subheading: Server code, resources, and deployment in one workflow.
 ---

package/docs/reference/api/pages.md

@@ -50,7 +50,7 @@ Imported from `"@void/vue"`.
 | `useParams()`                      | Returns dynamic route params for the page currently being rendered.                                                                                                                                                                               |
 | `useNavigation()`                  | Returns pending navigation state: `{ state, location, method }`, where `state` is `"idle"`, `"loading"`, or `"submitting"` and `location` is the pending destination.                                                                             |
 | `useForm(url, defaults, options?)` | Typed reactive form helper bound to a page action URL. Returns `{ data, post, put, patch, delete, pending, errors, error, hasChanges, wasSuccessful, recentlySuccessful, reset, clearErrors, clearError }`.                                       |
-| `useIslandForm(defaults)`          | Form helper for island components where the action URL is inferred from the current island request. Returns the same form state and submit helpers as `useForm()`.                                                                                |
+| `useIslandForm(defaults)`          | Form helper for island components. Same form state as `useForm()`, plus `submit(url, method)`. `post(url)`, `put(url)`, `patch(url)`, and `delete(url)` take the action URL and submit with `fetch()`.                                            |
 | `action(url, options?)`            | Awaitable one-shot page action helper. Uses `POST` by default and accepts `{ data, method, params }`, where `method` can be `"PUT"`, `"PATCH"`, or `"DELETE"`. Returns an `ActionResult`.                                                         |
 | `useShared()`                      | Returns shared data injected by middleware via `c.set("shared", {...})`.                                                                                                                                                                          |
 
@@ -102,7 +102,7 @@ Imported from `"@void/react"`.
 | `useParams()`                      | Returns dynamic route params for the page currently being rendered.                                                                                                                                                                                 |
 | `useNavigation()`                  | Returns pending navigation state: `{ state, location, method }`, where `state` is `"idle"`, `"loading"`, or `"submitting"` and `location` is the pending destination.                                                                               |
 | `useForm(url, defaults, options?)` | Form helper hook. Returns `{ data, setData, post, put, patch, delete, pending, errors, error, hasChanges, wasSuccessful, recentlySuccessful, reset, clearErrors, clearError }`.                                                                     |
-| `useIslandForm(defaults)`          | Form helper hook for island components where the action URL is inferred from the current island request. Returns the same form state and submit helpers as `useForm()`.                                                                             |
+| `useIslandForm(defaults)`          | Form helper hook for island components. Same form state as `useForm()`. `post(url)`, `put(url)`, `patch(url)`, and `delete(url)` take the action URL and submit with `fetch()`.                                                                     |
 | `action(url, options?)`            | Awaitable one-shot page action helper. Uses `POST` by default and accepts `{ data, method, params }`, where `method` can be `"PUT"`, `"PATCH"`, or `"DELETE"`. Returns an `ActionResult`.                                                           |
 | `useShared()`                      | Returns shared data injected by middleware via `c.set("shared", {...})`.                                                                                                                                                                            |
 | `Deferred<T>`                      | React-only prop type for `defer()` results. It is `Promise<T>` and is consumed with React `use()`.                                                                                                                                                  |
@@ -159,7 +159,7 @@ Imported from `"@void/svelte"`.
 | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `Link`                             | Svelte component for SPA navigation. Renders `<a>` for GET, `<button>` for non-GET methods. Props: `href`, `method`, `data`, `prefetch`, `cacheFor`, `preserveScroll`, `preserveState`, `replace`, `reloadDocument`, `viewTransition`, `onNavigate`. |
 | `useForm(url, defaults, options?)` | Form helper using Svelte 5 runes. Returns `{ data, post, put, patch, delete, pending, errors, error, hasChanges, wasSuccessful, recentlySuccessful, reset, clearErrors, clearError }`.                                                               |
-| `useIslandForm(defaults)`          | Form helper for island components where the action URL is inferred from the current island request. Returns the same form state and submit helpers as `useForm()`.                                                                                   |
+| `useIslandForm(defaults)`          | Form helper for island components. Same form state as `useForm()`, plus `submit(url, method)`. `post(url)`, `put(url)`, `patch(url)`, and `delete(url)` take the action URL and submit with `fetch()`.                                               |
 | `action(url, options?)`            | Awaitable one-shot page action helper. Uses `POST` by default and accepts `{ data, method, params }`, where `method` can be `"PUT"`, `"PATCH"`, or `"DELETE"`. Returns an `ActionResult`.                                                            |
 | `useShared()`                      | Returns shared data injected by middleware via `c.set("shared", {...})`.                                                                                                                                                                             |
 | `useRouter()`                      | Returns the Void Router with current route state (`url`, `path`, `query`, `params`) and navigation methods: `visit`, `refresh`, awaitable `prefetch`, `flush`, `flushAll`.                                                                           |
@@ -209,7 +209,7 @@ Imported from `"@void/solid"`.
 | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `Link`                             | Solid component for SPA navigation. Renders `<a>` for GET, `<button>` for non-GET methods. Props: `href`, `method`, `data`, `prefetch`, `cacheFor`, `preserveScroll`, `preserveState`, `replace`, `reloadDocument`, `viewTransition`, `onNavigate`. |
 | `useForm(url, defaults, options?)` | Form helper using Solid stores. Returns `{ data, setData, post, put, patch, delete, pending, errors, error, hasChanges, wasSuccessful, recentlySuccessful, reset, clearErrors, clearError }`.                                                       |
-| `useIslandForm(defaults)`          | Form helper for island components where the action URL is inferred from the current island request. Returns the same form state and submit helpers as `useForm()`.                                                                                  |
+| `useIslandForm(defaults)`          | Form helper for island components. Same form state as `useForm()`. `post(url)`, `put(url)`, `patch(url)`, and `delete(url)` take the action URL and submit with `fetch()`.                                                                          |
 | `action(url, options?)`            | Awaitable one-shot page action helper. Uses `POST` by default and accepts `{ data, method, params }`, where `method` can be `"PUT"`, `"PATCH"`, or `"DELETE"`. Returns an `ActionResult`.                                                           |
 | `useShared()`                      | Returns shared data injected by middleware via `c.set("shared", {...})`.                                                                                                                                                                            |
 | `useRouter()`                      | Returns the Void Router with current route state (`url`, `path`, `query`, `params`) and navigation methods: `visit`, `refresh`, awaitable `prefetch`, `flush`, `flushAll`.                                                                          |
@@ -235,11 +235,13 @@ export default defineConfig({
 | Import path                  | Contents                                                                                 |
 | ---------------------------- | ---------------------------------------------------------------------------------------- |
 | `@void/md/plugin`            | `voidMarkdown(options?)`, `MarkdownOptions`, `MdPage`                                    |
-| `@void/md`                   | `useFrontmatter()`, `FrontmatterContext`, `setFrontmatter()`, `MdPage`                   |
+| `@void/md`                   | `useFrontmatter()`, `MdPage`                                                             |
 | `@void/md/pages`             | Generated metadata for Markdown pages, used for navigation, sidebars, and search indexes |
 | `@void/md/theme.css`         | Full Markdown theme styles                                                               |
 | `@void/md/theme-content.css` | Content-only Markdown styles for apps that provide their own shell/layout                |
 
+`FrontmatterContext` and `setFrontmatter()` are deprecated. Use `useFrontmatter()`.
+
 See [Markdown Pages](../../guide/pages-routing/markdown.md) for setup and framework-specific examples.
 
 ## Form

package/docs/reference/api.md

@@ -66,6 +66,8 @@ Import Void's app-facing APIs from these paths:
 | `void/log`                | `logger` structured logging helper                                                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `void/routes`             | `RouteMap` and `WebSocketRouteMap` stubs (types only)                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | `void/queues`             | `queues` proxy for sending messages to typed queues                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `void/email`              | `sendEmail`, `createEmail`, `defineEmail`, `parseEmail`, `replyEmail`, `MimeError`, `ParseEmailError`, and address, attachment, result, and handler types. See [Email](../guide/email.md).                                                                                                                                                                                                                                                                                     |
+| `void/email/testing`      | `createEmailTestHarness` and `createInboundTestHarness` to capture sends and deliver test messages to `email/` handlers.                                                                                                                                                                                                                                                                                                                                                       |
 | `void/sandbox`            | `getSandbox`, `sandbox`, `SandboxLimitError`, `SandboxUnavailableError`, and the SDK 1.0 file, backup, and mount helpers. `getSandbox(id)` resolves a client. Commands, files, port requests, and process completion return promises; limits reject with `SandboxLimitError`, which extends `UsageLimit`. Container state lasts until inactivity (default ten minutes), a crash, or a restart. See [Sandboxes](../guide/sandboxes.md) for the API and deployment requirements. |
 | `void/env`                | `defineEnv`, `env`, schema helpers (`string`, `number`, `boolean`, `url`, `email`, `oneOf`, `json`), and global Cloudflare env types                                                                                                                                                                                                                                                                                                                                           |
 | `void/nitro`              | Nitro module for Nuxt and Analog. Add `'void/nitro'` to the Nitro `modules` so server routes get the app's `void/db` and `@schema`                                                                                                                                                                                                                                                                                                                                             |

package/docs/reference/cli/database.md

@@ -20,7 +20,7 @@ For SQLite, Void checks that the migration history applies to a fresh database.
 
 ## `void db status` {#void-db-status}
 
-Show migration status. Displays which migrations are applied or pending locally, then uses the saved deployment target for remote status: the hosted API for Void projects, the pinned D1 database and its configured migration table for direct Cloudflare SQLite projects, or the shell `DATABASE_URL` for direct Cloudflare PostgreSQL/MySQL projects. If the remote credential or service is unavailable, local status is still shown.
+Show migration status. Displays which migrations are applied or pending locally, then uses the saved deployment target for remote status: the hosted API for Void projects, the pinned D1 database and its configured migration table for direct Cloudflare SQLite projects, or the shell `DATABASE_URL` for direct Cloudflare PostgreSQL/MySQL projects. If the remote credential or service is unavailable, local status is still shown. If the local PostgreSQL or MySQL database cannot be read, local status shows `unknown`; the command fails when remote status is not available either.
 
 ## `void db reset` {#void-db-reset}
 
@@ -28,7 +28,7 @@ Show migration status. Displays which migrations are applied or pending locally,
 void db reset [--yes]
 ```
 
-Drop the development database and re-apply all migrations. D1 resets the local database; PostgreSQL and MySQL drop all tables in the `DATABASE_URL` database from `.env`.
+Drop the development database and re-apply all migrations. D1 resets the local database. PostgreSQL drops the tables, views, sequences, and custom types in the `public` schema of the `DATABASE_URL` database from `.env` and keeps installed extensions. If a table, view, or function in another schema uses one of those views, sequences, or types, reset stops before it drops anything and lists those objects. MySQL drops every table and view in that database.
 
 When that `DATABASE_URL` points to a host other than `localhost`, Void names the database and asks before dropping its tables. Pass `--yes` to skip the prompt in scripts and CI; without a terminal, the command stops unless `--yes` is set. If `.env` uses the same URL as your deployment (for example after `void db connect`), reset drops the deployed tables.
 
@@ -73,7 +73,7 @@ void db migrate [--remote]
 
 Apply pending migrations to the local database without resetting. Unlike `void db reset`, this preserves existing data and only runs migrations that haven't been applied yet.
 
-Pass `--remote` to apply pending migrations to the saved target. Hosted projects require a Void login and link. Direct Cloudflare D1 projects use the binding's configured migration directory, table, and pattern; direct PostgreSQL and MySQL projects use the shell `DATABASE_URL`.
+Pass `--remote` to apply pending migrations to the saved target. Hosted projects require a Void login and link. Direct Cloudflare D1 projects use the binding's configured migration directory, table, and pattern. The D1 binding must set `migrations_dir`. Direct PostgreSQL and MySQL projects use the shell `DATABASE_URL`.
 
 ## `void db studio` {#void-db-studio}
 
@@ -87,11 +87,13 @@ By default, targets the local database. Pass `--remote` to open Studio against t
 
 - **Hosted PostgreSQL and MySQL projects**: fetch the stored connection string from the platform and open Studio against it. If the URL isn't stored yet, run `void db set-url` first.
 - **Direct Cloudflare PostgreSQL and MySQL projects**: use `DATABASE_URL` from the current shell.
-- **D1 projects**: remote Studio is not yet supported. Use `void db execute --remote` for ad-hoc queries against your deployed D1 database.
+- **D1 projects**: remote Studio is not available. Use `void db execute --remote` to query your deployed D1 database.
 
 ## `void db rename-migrations` {#void-db-rename-migrations}
 
-Rename existing migrations from the old numeric prefix format (`0001_name.sql`) to timestamp-based format (`20260410161500_name.sql`). Updates local tracking table and remote records if logged in with a linked project.
+Rename existing migrations from the old numeric prefix format (`0001_name.sql`) to timestamp-based format (`20260410161500_name.sql`). Updates local tracking table and remote records if logged in with a linked project. A project that deploys to Void must be linked first with `void project link`; otherwise the command stops without changes.
+
+Direct Cloudflare deploys are not supported: Void cannot rename the records in the deployed database, so the command stops without changes. Keep the existing names; new migrations use timestamps and run after them.
 
 ## `void db connect` {#void-db-connect}
 

package/docs/reference/cli/deploy.md

@@ -10,6 +10,7 @@ outline: deep
 void deploy [--project <name>] [--dir <path>] [--spa] [--skip-build] [--debug]
 void deploy [--platform <cloudflare|void>] [--require-email]
 void deploy --platform cloudflare --atomic
+void deploy --platform cloudflare --provision
 ```
 
 Auto-detects your project type and chooses the right pipeline. See [Supported App Types](../../guide/app-types.md) and [Deployment](../../guide/deployment.md) for details.
@@ -26,16 +27,17 @@ For an existing Void Worker, `void deploy` can link the Worker and migrate its r
 
 For Drizzle projects, deploy performs a read-only schema drift check. If a new migration would be generated, deploy stops and tells you to run `void db generate`, review the migration, commit it yourself, and rerun `void deploy`.
 
-| Flag                            | Purpose                                                                                            |
-| ------------------------------- | -------------------------------------------------------------------------------------------------- |
-| `--platform <cloudflare\|void>` | Override the platform stored in `.void/project.json`                                               |
-| `--project <name>`              | Target a specific Void project by slug; not supported with `--platform cloudflare`                 |
-| `--dir <path>`                  | Deploy a pre-built static directory (skips build)                                                  |
-| `--spa`                         | Use SPA mode instead of SSG for static deploys                                                     |
-| `--skip-build`                  | Skip the build step; on Cloudflare this is supported for static/SPA/SSG deploys only               |
-| `--require-email`               | Fail when email cannot be set up instead of deploying without it; requires `--platform cloudflare` |
-| `--atomic`                      | Publish an existing Durable Object Worker directly; readiness is checked after traffic changes     |
-| `--debug`                       | Mirror the structured deploy log to stderr (also written to `~/.void/logs/`)                       |
+| Flag                            | Purpose                                                                                                                                                              |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `--platform <cloudflare\|void>` | Override the platform stored in `.void/project.json`                                                                                                                 |
+| `--project <name>`              | Target a specific Void project by slug; not supported with `--platform cloudflare`                                                                                   |
+| `--dir <path>`                  | Deploy a pre-built static directory (skips build)                                                                                                                    |
+| `--spa`                         | Use SPA mode instead of SSG for static deploys                                                                                                                       |
+| `--skip-build`                  | Skip the build step; on Cloudflare this is supported for static/SPA/SSG deploys only                                                                                 |
+| `--require-email`               | Fail when email cannot be set up instead of deploying without it; requires `--platform cloudflare`                                                                   |
+| `--provision`                   | Run resource provisioning again even when every resource exists, for example to enable D1 read replication on an existing database; requires `--platform cloudflare` |
+| `--atomic`                      | Publish an existing Durable Object Worker directly; readiness is checked after traffic changes                                                                       |
+| `--debug`                       | Mirror the structured deploy log to stderr (also written to `~/.void/logs/`)                                                                                         |
 
 `--atomic` applies to one deployment. For an existing Durable Object Worker that consistently cannot stage, set `deploy: { cloudflare: { mode: 'atomic' } }` in `void.config.ts` so plain `void deploy` uses atomic publication. The default is `staged`.
 

package/docs/reference/cli/email.md

@@ -114,7 +114,7 @@ void email status --platform cloudflare
 
 Check the domain configured in `email.from`: permissions, DNS, routing, sending, handler addresses, and the email binding. Exits unsuccessfully when setup is incomplete. Workers Free setup can be ready with sending limited to verified destinations; run `void email setup --platform cloudflare` after upgrading to Workers Paid.
 
-Without `--platform cloudflare` (or with `--platform void`) the command is not available yet; on the Void platform use `void email usage` and `void email destinations`.
+`void email status` reads only your own Cloudflare account, so `--platform cloudflare` is required. On the Void platform, use `void email usage` and `void email destinations`.
 
 ## `void email setup` {#void-email-setup}
 

package/docs/reference/cli/generate.md

@@ -22,7 +22,7 @@ Creates:
 - An export from `db/schema.ts`
 - `routes/api/posts/index.ts`: `GET` for list and `POST` for insert with validation
 - `routes/api/posts/[id].ts`: `GET` by id with `404` handling
-- Regenerated `.void/db.d.ts`
+- Regenerated types and TypeScript configuration in `.void/`
 
 The generated routes automatically detect your validation library from `package.json` (`valibot`, `zod`, or `arktype`). If none is found, you will be prompted to choose one or skip validation. Run `void db push` to apply the schema locally, or `void db generate` to create migrations before deploying.
 

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

@@ -105,7 +105,7 @@ void platform rollback [id] --runtime <earlier-path> [--from-runtime <current-pa
 void platform repair [id] [--runtime <path>] [--dashboard-url <origin>] [--auth-config <path>] [--plan] [--yes]
 void platform disable [id] [--plan] [--yes]
 void platform enable [id] [--runtime <path>] [--plan] [--yes]
-void platform uninstall [id] [--plan] [--purge-data | --purge-resources] [--keep-zone] [--yes]
+void platform uninstall [id] [--plan] [--purge-data | --purge-resources] [--yes]
 ```
 
 `discover --installation` limits recovery and endpoint verification to one installation in a shared Cloudflare account.
@@ -149,7 +149,7 @@ An upgrade completes after the new Workers pass health checks. If rollout fails,
 
 If project Zero Trust is on and no platform user exists yet, uninstall turns it off and deletes its Access applications first. Run it on the computer that installed the platform.
 
-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.
+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. `--keep-zone` is deprecated and has no effect; uninstall always keeps zones.
 
 `--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.
 

package/docs/reference/cli/project.md

@@ -189,8 +189,10 @@ void project cancel [deployId]
 
 Cancel an active deployment.
 
-- If `[deployId]` is omitted, shows an interactive select menu of active deployments for the linked project
-- If `[deployId]` is provided, cancels that deployment directly
+- If `[deployId]` is omitted, targets the linked project's active deployment
+- If `[deployId]` is provided, targets that deployment; it must still be active
+
+Void asks for confirmation before it requests cancellation.
 
 This command is hosted-only. Direct Cloudflare deploys are local operations and do not expose a remote build to cancel.
 

package/docs/reference/cli.md

@@ -63,7 +63,7 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void project rollback`           | Roll back to a previous deployment                                            |
 | `void project cancel`             | Cancel an active deployment                                                   |
 | `void project zero-trust`         | Inspect or override project Zero Trust protection                             |
-| `void project purge-cache`        | Purge all cached pages                                                        |
+| `void project purge-cache`        | Purge all cached pages (Void platform)                                        |
 | `void build logs`                 | Stream, tail, or download build logs                                          |
 | `void email status`               | Show email readiness on your own Cloudflare account (`--platform cloudflare`) |
 | `void email setup`                | Set email up on your own Cloudflare account, without deploying                |

package/docs/reference/config.md

@@ -61,11 +61,21 @@ When set, those conventions move under the configured directory:
 
 With that config, Void reads `src/pages`, `src/routes`, `src/db/schema.ts`, `src/db/migrations`, `src/auth.ts`, and `src/env.ts`. Project files such as `void.config.ts`, `vite.config.ts`, `package.json`, `tsconfig.json`, `public/`, and the local-only `.env` stay at the project root. Void does not scan both locations; if source conventions exist in both places during dev/build, remove one copy so the active source tree is unambiguous.
 
+### `ai`
+
+`ai.gateway` names the Cloudflare AI Gateway that `ai.provider().fetch()` uses when your app runs on your own Cloudflare account. `ai.run()`, `ai.stream()`, and `ai.image()` use the Workers AI binding and do not need a gateway. On a Void platform, the platform selects the gateway and ignores this setting.
+
+```json
+{ "ai": { "gateway": "my-gateway" } }
+```
+
+See [AI on your Cloudflare account](../integrations/cloudflare.md#ai-self-host).
+
 ### `auth`
 
 High-level Better Auth configuration.
 
-Use `auth.providers` to select which built-in auth providers Void should enable by default. Include `"email"` for email/password auth. Social providers read credentials from `AUTH_<PROVIDER>_CLIENT_ID` and `AUTH_<PROVIDER>_CLIENT_SECRET`.
+Use `auth.providers` to select which built-in auth providers Void should enable by default. Include `"email"` for email/password auth. Social providers read credentials from `AUTH_<PROVIDER>_CLIENT_ID` and `AUTH_<PROVIDER>_CLIENT_SECRET`. `cognito` also needs a domain, region, and user pool ID: set `AUTH_COGNITO_DOMAIN`, `AUTH_COGNITO_REGION`, and `AUTH_COGNITO_USER_POOL_ID`, or set them in `auth.ts`.
 
 ```json
 {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "void",
-  "version": "1.1.0",
+  "version": "1.1.11",
   "description": "Full-stack framework and deployment CLI for Cloudflare Workers, powered by Vite.",
   "homepage": "https://void.cloud",
   "bugs": {
@@ -347,11 +347,11 @@
     "@cloudflare/workers-auth": "^0.14.0",
     "@cloudflare/workers-types": "^5.20261014.1",
     "@napi-rs/keyring": "^2.1.1",
-    "@void/deploy-cloudflare": "1.1.0",
-    "@void/deploy-core": "1.1.0",
-    "@void/edge": "1.1.0",
-    "@void/isr": "1.1.0",
-    "@void/platform": "1.1.0",
+    "@void/deploy-cloudflare": "1.1.11",
+    "@void/deploy-core": "1.1.11",
+    "@void/edge": "1.1.11",
+    "@void/isr": "1.1.11",
+    "@void/platform": "1.1.11",
     "better-auth": "^1.7.7",
     "better-sqlite3": "^13.0.3",
     "blake3-jit": "^1.1.0",
@@ -400,7 +400,7 @@
     "zod": "^4.6.7"
   },
   "peerDependencies": {
-    "@void/md": "1.1.0",
+    "@void/md": "1.1.11",
     "arktype": ">=2.0.0",
     "valibot": ">=1.0.0-beta.7",
     "vite": "^8.0.0",

package/dist/client-B60PwCC4.mjs

@@ -1 +0,0 @@
-export { r as PlatformClient } from "./client-DM9Kcf4e.mjs";

package/dist/collect-Cae8A7Zr.mjs

@@ -1 +0,0 @@
-export { t as collectMigrations } from "./collect-xjffdCdk.mjs";

package/dist/deploy-9lgfhrXS.mjs

@@ -1,2 +0,0 @@
-import "./deploy-transport-DWlWBe6M.mjs";
-export { i as checkWranglerMigrationApplySet, t as parseRootWranglerConfig, r as runDeploy } from "./deploy-BYYlnsiy.mjs";

package/dist/discover-ClzFSwns.mjs

@@ -1 +0,0 @@
-export { t as discoverSchema } from "./discover-D2PGT63u.mjs";

package/dist/gen-sXyp5DFO.mjs

@@ -1 +0,0 @@
-export { r as runGenCommand } from "./gen-CufHEf42.mjs";

package/dist/help-i2YGGnTH.mjs

@@ -1 +0,0 @@
-export { r as printHelpPage } from "./help-BT2hovNI.mjs";

package/dist/login-XD844Xs-.mjs

@@ -1 +0,0 @@
-export { r as selectPlatformLoginMethod } from "./login-C2T1oVG-.mjs";

package/dist/migrate-BRwU-blY.mjs

@@ -1 +0,0 @@
-export { n as runMigrateCommand } from "./migrate-BDIprOYd.mjs";

package/dist/operator-cmd-D6gnZsnK.mjs

@@ -1 +0,0 @@
-export { a as runOperatorCommand } from "./operator-cmd-DHieWtFp.mjs";

package/dist/platform-args-B0HeTh0C.mjs

@@ -1 +0,0 @@
-export { t as parsePlatformArgs } from "./platform-args-CaCL_1Ch.mjs";

package/dist/prepare-CYT6tAzD.mjs

@@ -1 +0,0 @@
-export { t as prepareProject } from "./prepare-DEB5SeVJ.mjs";

package/dist/r2-conditions-D1Wk8i7b.mjs

@@ -1,30 +0,0 @@
-//#region src/runtime/remote/r2-conditions.ts
-function serializeR2Conditional(value) {
-	if (value instanceof Headers) return Array.from(value.entries());
-	return {
-		...value,
-		uploadedBefore: value.uploadedBefore?.toISOString(),
-		uploadedAfter: value.uploadedAfter?.toISOString()
-	};
-}
-function parseR2Conditional(value) {
-	if (Array.isArray(value)) {
-		if (!value.every((pair) => Array.isArray(pair) && pair.length === 2 && pair.every((item) => typeof item === "string"))) throw new Error("Invalid R2 conditional headers");
-		return new Headers(value);
-	}
-	if (!value || typeof value !== "object") throw new Error("Invalid R2 conditional options");
-	const result = {};
-	for (const [key, entry] of Object.entries(value)) if (key === "etagMatches" || key === "etagDoesNotMatch") {
-		if (typeof entry !== "string") throw new Error(`Invalid R2 condition: ${key}`);
-		result[key] = entry;
-	} else if (key === "uploadedBefore" || key === "uploadedAfter") {
-		if (typeof entry !== "string" || !Number.isFinite(Date.parse(entry))) throw new Error(`Invalid R2 condition: ${key}`);
-		result[key] = new Date(entry);
-	} else if (key === "secondsGranularity") {
-		if (typeof entry !== "boolean") throw new Error(`Invalid R2 condition: ${key}`);
-		result[key] = entry;
-	} else throw new Error(`Unsupported R2 condition: ${key}`);
-	return result;
-}
-//#endregion
-export { serializeR2Conditional as n, parseR2Conditional as t };

package/dist/validate-BQFdf0Pi.mjs

@@ -1 +0,0 @@
-export { i as validateMigrations } from "./validate-CheZGRE7.mjs";