void 0.7.13 → 0.8.0

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

@@ -16,11 +16,14 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void prepare`                    | Generate `.void` artifacts without starting Vite |
 | `void gen model <name> [cols...]` | Scaffold migration + CRUD routes                 |
 | `void gen route <path>`           | Create an API route                              |
+| `void db push`                    | Apply schema directly without migration files    |
+| `void db generate`                | Generate SQL migrations from schema changes      |
 | `void db status`                  | Show local/remote migration status               |
 | `void db reset`                   | Drop and re-apply all migrations                 |
 | `void db seed`                    | Reset + seed local database                      |
 | `void db studio`                  | Open Drizzle Studio for local database           |
 | `void secret put <name=value>`    | Set a production secret                          |
+| `void secret list`                | List production secrets                          |
 | `void secret sync .env.local`     | Bulk upload secrets from dotenv file             |
 | `void env check [--remote]`       | Validate env.ts schema                           |
 | `void env types`                  | Regenerate .void/env.d.ts from env.ts            |
@@ -29,7 +32,9 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void project link`               | Link directory to a project                      |
 | `void project logs`               | Show runtime logs from deployed project          |
 | `void project rollback`           | Roll back to a previous deployment               |
+| `void project cancel`             | Cancel an active deployment                      |
 | `void project purge-cache`        | Purge all cached pages                           |
+| `void mcp`                        | Start the Void MCP server                        |
 | `void init`                       | Setup wizard for new or existing projects        |
 
 ## Binary Invocation
@@ -184,6 +189,17 @@ Roll back to a previous deployment. Traffic instantly switches to the target dep
 
 Only **retained** deployments can be rolled back to. The number of retained deployments depends on your plan (free: 1, solo: 5, pro: 25, unlimited for sponsored/custom).
 
+### `void project cancel [deployId]`
+
+```
+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
+
 ### `void project delete [name]`
 
 Permanently delete a project and all its resources (databases, KV namespaces, R2 buckets, deployments). Requires typing the project slug to confirm.
@@ -234,6 +250,18 @@ That fallback is mainly for projects that skipped Void project setup during `voi
 
 ## Database
 
+### `void db push`
+
+Apply your Drizzle schema directly to the development database without creating migration files. For D1 projects, this updates the local D1 database used by dev. For PostgreSQL projects, this uses `DATABASE_URL` from `.env.local`.
+
+Use this for quick schema iteration while prototyping. Before deploying, generate and review migration files with `void db generate`.
+
+### `void db generate`
+
+Generate SQL migration files from schema changes.
+
+The command compares your current `db/schema.ts` or `db/schema/` modules against the last generated Drizzle snapshot and writes new migration artifacts under `db/migrations/`. Review and commit the generated files before deploying.
+
 ### `void db status`
 
 Show migration status. Displays which migrations are applied or pending locally. When logged in and linked to a project, also shows remote status.
@@ -418,6 +446,14 @@ void gen queue emails
 
 ## Secrets
 
+### `void secret list`
+
+```
+void secret list [--project <name>]
+```
+
+List the production secrets configured for the project. Secret values are never printed.
+
 ### `void secret put`
 
 ```
@@ -539,10 +575,12 @@ List all custom domains and their status (active/pending).
 ### `void domain status`
 
 ```
-void domain status <hostname> [--project <name>]
+void domain status <hostname> [--project <name>] [--verbose]
 ```
 
-Check verification and SSL status for a specific domain. Shows hostname, status, SSL status, and any verification errors.
+Check verification and SSL status for a specific domain. Prints a rolled-up state (`awaiting_dns`, `verifying_dns`, `issuing_cert`, `deploying_cert`, `awaiting_deployment`, `active`, `error`, or `pending`) with a one-line diagnostic explaining what Cloudflare is doing and any user action required. When DNS records are still pending, the command also prints the exact TXT records to add at your DNS provider.
+
+Pass `--verbose` to additionally print the raw multi-line status breakdown (DB status, SSL status, ownership state, verification errors) underneath the rollup.
 
 Project resolution for domain commands follows the same order as deploy (`--project`, `VOID_PROJECT`, linked project).
 
@@ -558,9 +596,17 @@ Runs all agent setup steps:
 
 If no agent is detected, `void init --agents` asks you to choose from Claude Code, Cursor, Codex, Gemini CLI, or Generic.
 
+### `void mcp`
+
+```
+void mcp
+```
+
+Start the Void MCP server over stdio for supported coding agents.
+
 ## Environment variables
 
-| Variable       | Purpose                                                      | Default |
-| -------------- | ------------------------------------------------------------ | ------- |
-| `VOID_TOKEN`   | Auth token override instead of saved config                  | none    |
-| `VOID_PROJECT` | Default project slug for deploy, secret, and delete commands | none    |
+| Variable       | Purpose                                                                   | Default |
+| -------------- | ------------------------------------------------------------------------- | ------- |
+| `VOID_TOKEN`   | Auth token override instead of saved config                               | none    |
+| `VOID_PROJECT` | Default project slug for deploy, secret, domain, and cache purge commands | none    |

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

@@ -13,6 +13,7 @@ Project-level configuration lives in a `void.json` file at the project root. Mos
 ```json
 {
   "$schema": "./node_modules/void/schema.json",
+  "sourceDir": "src",
   "target": "cloudflare",
   "auth": {
     "providers": ["email", "github", "google"]
@@ -36,10 +37,24 @@ Project-level configuration lives in a `void.json` file at the project root. Mos
 }
 ```
 
-Add the `$schema` field for autocomplete and validation in your editor.
+Add the `$schema` field for autocomplete and validation in your editor. The schema ships with the `void` package at `node_modules/void/schema.json` and is also exposed as the `void/schema.json` package subpath.
 
 ## Fields
 
+### `sourceDir`
+
+Directory containing Void source conventions, relative to the project root.
+
+When omitted, Void uses the existing project-root conventions: `pages/`, `routes/`, `middleware/`, `crons/`, `queues/`, `db/`, `auth.ts`, and `env.ts`.
+
+When set, those conventions move under the configured directory:
+
+```json
+{ "sourceDir": "src" }
+```
+
+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.json`, `vite.config.ts`, `package.json`, `tsconfig.json`, `wrangler.json`, `public/`, and `.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.
+
 ### `auth`
 
 High-level Better Auth configuration.
@@ -222,7 +237,9 @@ Deploy target runtime. Defaults to `"cloudflare"`.
 | `"bun"`        | Bun, using `Bun.serve()`                                  |
 | `"deno"`       | Deno, using `Deno.serve()`                                |
 
-Non-CF targets disable CF bindings (`void/db`, `void/kv`, `void/auth`, `void/storage`, `void/ai`, `void/sandbox`, `void/env`, `void/ws`). Importing any of these with a non-CF target produces a compile-time error. File-based routing, middleware, and `void/client` all work normally.
+Non-CF targets disable CF binding imports (`void/db`, `void/kv`, `void/auth`, `void/storage`, `void/ai`, `void/sandbox`, `void/env`). Importing any of these with a non-CF target produces a compile-time error. File-based routing, middleware, and `void/client` all work normally.
+
+Void-managed WebSocket route files (`*.ws.ts`) are Cloudflare-only because they compile to Durable Objects. The `void/ws` subpath itself is not blocked on non-CF targets so client-side `connect()` code can still be bundled where a browser-like `WebSocket` runtime is available.
 
 ```json
 { "target": "node" }
@@ -236,23 +253,29 @@ Curated Cloudflare Workers configuration. Cloudflare-targeted apps require an ex
 | --------------------- | ---------- | -------------------------------------- |
 | `compatibility_date`  | `string`   | Cloudflare Workers compatibility date  |
 | `compatibility_flags` | `string[]` | Cloudflare Workers compatibility flags |
+| `vars`                | `object`   | Plain-text worker variables            |
 
 ```json
 {
   "worker": {
     "compatibility_date": "2025-12-01",
-    "compatibility_flags": ["nodejs_compat"]
+    "compatibility_flags": ["nodejs_compat"],
+    "vars": {
+      "PUBLIC_API_BASE": "https://api.example.com"
+    }
   }
 }
 ```
 
+`worker.vars` values must be strings. They are merged into Worker bindings before `.env` files are loaded, so project `.env` values override `worker.vars` for local dev/build. Do not put secrets here; use `env.ts` plus `void secret put` for production secrets.
+
 ### `routing`
 
 Routing and edge configuration for headers, redirects, rewrites, and caching.
 
 #### `routing.headers`
 
-Custom response headers for static assets. Keys are URL patterns, values are arrays of `"Name: value"` strings. See [Custom Headers](../guide/edge/headers) for details.
+Custom response headers for dispatch-worker responses. Keys are URL patterns, values are arrays of `"Name: value"` strings. See [Custom Headers](../guide/edge/headers) for details.
 
 ```json
 {

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

@@ -26,7 +26,7 @@ This runs once before plugins initialize, so the results are available to config
 | `AI`      | `Ai`                              | `import { ai } from "void/ai"`                                            | `env.AI` or `c.env.AI`           |
 | `SANDBOX` | `DurableObjectNamespace<Sandbox>` | `import { getSandbox } from "void/sandbox"`                               | `env.SANDBOX` or `c.env.SANDBOX` |
 | Auth      | none                              | `import { ... } from "void/auth"` or `import { auth } from "void/client"` | none                             |
-| `QUEUE_*` | `Queue`                           | `import { ... } from "void/queue"`                                        | `env.QUEUE_*`                    |
+| `QUEUE_*` | `Queue`                           | `import { queues } from "void/queues"`                                    | `env.QUEUE_*`                    |
 
 Auth detection also triggers when importing the `auth` specifier from `void/client` (but not when importing only `fetch`).