void 0.10.5 → 0.10.6

package/skills/void/docs/node_modules/void/node_modules/@clack/prompts/CHANGELOG.md

@@ -1,5 +1,99 @@
 # @clack/prompts
 
+## 1.7.0
+
+### Minor Changes
+
+- [#574](https://github.com/bombshell-dev/clack/pull/574) [`8f1c380`](https://github.com/bombshell-dev/clack/commit/8f1c380683cfb5fb7a094610342046ae1603e28e) Thanks [@dreyfus92](https://github.com/dreyfus92)! - Add `showInstructions` option to `select`, `multiselect`, and `groupMultiselect`. Keyboard hints remain shown by default; pass `showInstructions: false` to hide them.
+
+### Patch Changes
+
+- [#582](https://github.com/bombshell-dev/clack/pull/582) [`4b24953`](https://github.com/bombshell-dev/clack/commit/4b249539e28eecc16c13b3a1bd0ba447e9f38d06) Thanks [@43081j](https://github.com/43081j)! - Handle empty arrays in various prompts and utilities.
+
+- Updated dependencies [[`4b24953`](https://github.com/bombshell-dev/clack/commit/4b249539e28eecc16c13b3a1bd0ba447e9f38d06)]:
+  - @clack/core@1.4.3
+
+## 1.6.0
+
+### Minor Changes
+
+- [#568](https://github.com/bombshell-dev/clack/pull/568) [`f87933f`](https://github.com/bombshell-dev/clack/commit/f87933fb7b3f4c401b9e51a152b95cb8e7200fe5) Thanks [@florian-lefebvre](https://github.com/florian-lefebvre)! - Updates default formatter of `note()` to note dim lines anymore
+
+  If you want the old behavior, provide a `format()` function:
+
+  ```diff
+  import { note } from '@clack/prompts';
+  +import { styleText } from 'node:util';
+
+  note(
+    'You can edit the file src/index.jsx',
+    'Next steps.'
+  +  { format: (text) => styleText('dim', text) }
+  );
+  ```
+
+- [#567](https://github.com/bombshell-dev/clack/pull/567) [`cc6aab5`](https://github.com/bombshell-dev/clack/commit/cc6aab50186cff8a02dc98e9cfd3897c29a33b15) Thanks [@dreyfus92](https://github.com/dreyfus92)! - Add keyboard instruction footers to `select`, `multiselect`, and `groupMultiselect` in the active state, matching autocomplete. No option — always shown.
+
+### Patch Changes
+
+- Updated dependencies [[`2f2b52f`](https://github.com/bombshell-dev/clack/commit/2f2b52f77cbfa9af618c6d929249ab8395fc37a1), [`e1b6ee7`](https://github.com/bombshell-dev/clack/commit/e1b6ee71a76e17a3c33ba7ee6e5fb34e886233bb)]:
+  - @clack/core@1.4.2
+
+## 1.5.1
+
+### Patch Changes
+
+- [#548](https://github.com/bombshell-dev/clack/pull/548) [`2356e97`](https://github.com/bombshell-dev/clack/commit/2356e97c1f46007ead55133c3a26910404ef1cfb) Thanks [@43081j](https://github.com/43081j)! - Remove sourcemaps and enable pretty-ish build output.
+
+- [#546](https://github.com/bombshell-dev/clack/pull/546) [`56e9d67`](https://github.com/bombshell-dev/clack/commit/56e9d6707715bc858d9c2dbc444230b02813e809) Thanks [@ghostdevv](https://github.com/ghostdevv)! - docs: add jsdoc for `date`, `limit-options`, and `messages`
+
+- Updated dependencies [[`2356e97`](https://github.com/bombshell-dev/clack/commit/2356e97c1f46007ead55133c3a26910404ef1cfb)]:
+  - @clack/core@1.4.1
+
+## 1.5.0
+
+### Minor Changes
+
+- [#543](https://github.com/bombshell-dev/clack/pull/543) [`83428ac`](https://github.com/bombshell-dev/clack/commit/83428ac6d8bc5eda87615cc7b1f14e0c8b16e1b6) Thanks [@florian-lefebvre](https://github.com/florian-lefebvre)! - Adds support for Standard Schema validation
+
+  Prompts accept an optional `validate()` function to validate user input. While a function provides more flexibility and customization over your validation, it can be a bit verbose. To help solve this, there are libraries that provide schema-based validation to make shorthand and type-strict validation substantially easier.
+
+  Libraries following the [Standard Schema specification](https://github.com/standard-schema/standard-schema) are now natively supported. For example, using [Arktype](https://arktype.io/):
+
+  ```diff
+  import { text } from '@clack/prompts';
+  import { type } from 'arktype';
+
+  const name = await text({
+  	message: 'Enter your email',
+  +	validate: type('string.email').describe('Invalid email'),
+  });
+  ```
+
+### Patch Changes
+
+- [#542](https://github.com/bombshell-dev/clack/pull/542) [`adb6af9`](https://github.com/bombshell-dev/clack/commit/adb6af9f5fb39408934323a7415beb46b63ecd9a) Thanks [@ghostdevv](https://github.com/ghostdevv)! - docs: add jsdoc for `box`, `group`, and `group-multi-select`
+
+- [#534](https://github.com/bombshell-dev/clack/pull/534) [`3dcb31a`](https://github.com/bombshell-dev/clack/commit/3dcb31a7d63827d95a5a52ac630cbd48e3a68364) Thanks [@MattStypa](https://github.com/MattStypa)! - Fixed spaces and uppercase characters in multiline prompt
+
+- [#540](https://github.com/bombshell-dev/clack/pull/540) [`3170ed9`](https://github.com/bombshell-dev/clack/commit/3170ed94dc2a6ed7973228d46c664fb7461969ad) Thanks [@ghostdevv](https://github.com/ghostdevv)! - docs: add jsdoc for `autocomplete`, `confirm`, and `path` prompts
+
+- Updated dependencies [[`83428ac`](https://github.com/bombshell-dev/clack/commit/83428ac6d8bc5eda87615cc7b1f14e0c8b16e1b6), [`3dcb31a`](https://github.com/bombshell-dev/clack/commit/3dcb31a7d63827d95a5a52ac630cbd48e3a68364)]:
+  - @clack/core@1.4.0
+
+## 1.4.0
+
+### Minor Changes
+
+- 284677e: Support scrolling and `maxItems` option for `groupMultiselect`, and removes indent when `withGuide` is set to `false`
+
+### Patch Changes
+
+- aab46a2: docs: add jsdoc for `text`, `password`, and `multiline` prompts
+- 54be8d7: Fix line wrapping and overflow computation in group multi-select and other list-like prompts.
+- Updated dependencies [54be8d7]
+  - @clack/core@1.3.1
+
 ## 1.3.0
 
 ### Minor Changes

package/skills/void/docs/node_modules/void/node_modules/@clack/prompts/README.md

@@ -65,7 +65,7 @@ const meaning = await text({
 
 ### Password
 
-The password component behaves like `text`, but masks the input as the user types.
+The password prompt behaves like the [`text`](#text) prompt, but masks the input as the user types.
 
 ```js
 import { password } from '@clack/prompts';
@@ -81,7 +81,7 @@ const secret = await password({
 
 ### Confirm
 
-The confirm component accepts a yes or no answer. The result is a boolean value of `true` or `false`.
+The `confirm` prompt accepts a yes or no choice, returning a boolean value corresponding to the user's selection.
 
 ```js
 import { confirm } from '@clack/prompts';
@@ -93,16 +93,16 @@ const shouldContinue = await confirm({
 
 ### Date
 
-The date component accepts a calendar date and returns a `Date` value.
+The `date` prompt provides an interactive date picker, allowing users to navigate between year, month, and day segments and increment/decrement values using keyboard controls.
 
 ```js
 import { date } from '@clack/prompts';
 
-const dueDate = await date({
-  message: 'Pick a due date.',
-  format: 'YMD',
-  minDate: new Date(Date.UTC(2026, 0, 1)),
-  maxDate: new Date(Date.UTC(2026, 11, 31)),
+const birthday = await date({
+  message: 'Pick your birthday',
+  minDate: new Date('1900-01-01'),
+  initialValue: new Date(),
+  maxDate: new Date(),
 });
 ```
 
@@ -125,7 +125,7 @@ const projectType = await select({
 
 ### Autocomplete
 
-The autocomplete component lets a user filter a list by typing, then choose one option from the matching results. By default, matching uses each option's `label`, `hint`, and `value`. The result is the selected option's `value`.
+The `autocomplete` prompt combines text input with a searchable list of options. It's perfect for when you have a large list of options and want to help users find what they're looking for quickly.
 
 ```js
 import { autocomplete } from '@clack/prompts';
@@ -142,6 +142,27 @@ const framework = await autocomplete({
 });
 ```
 
+### Autocomplete Multi-Select
+
+The `autocompleteMultiselect` prompt combines the search functionality of [autocomplete](#autocomplete) with the ability to select multiple options.
+
+```js
+import { autocomplete } from '@clack/prompts';
+
+const framework = await autocomplete({
+  message: 'Search for a framework',
+  options: [
+    { value: 'next', label: 'Next.js', hint: 'React framework' },
+    { value: 'astro', label: 'Astro', hint: 'Content-focused' },
+    { value: 'svelte', label: 'SvelteKit', hint: 'Compile-time framework' },
+    { value: 'remix', label: 'Remix', hint: 'Full stack framework' },
+    { value: 'nuxt', label: 'Nuxt', hint: 'Vue framework' },
+  ],
+  placeholder: 'Type to search...',
+  maxItems: 5,
+});
+```
+
 ### Select Key
 
 The `selectKey` component lets a user choose an option by pressing its single-character string `value` key directly.
@@ -201,7 +222,7 @@ const basket = await groupMultiselect({
 
 ### Multi-Line Text
 
-The multi-line text component accepts multiple lines of text input. By default, pressing `Enter` twice submits the input.
+The multi-line prompt accepts multiple lines of text input. By default, pressing `Enter` twice submits the input.
 
 ```js
 import { multiline } from '@clack/prompts';
@@ -226,7 +247,7 @@ const bio = await multiline({
 
 ### Path
 
-The path component offers filesystem path suggestions and returns the selected path as a string. When `directory: true` is set, only directories can be selected.
+The `path` prompt extends [`autocomplete`](#autocomplete) to provide file and directory suggestions.
 
 ```js
 import { path } from '@clack/prompts';

package/skills/void/docs/node_modules/void/node_modules/@cloudflare/sandbox/README.md

@@ -98,6 +98,49 @@ export default {
 };
 ```
 
+## Quick tunnels
+
+`sandbox.tunnels.get(port)` exposes a service running inside the
+sandbox on a `*.trycloudflare.com` URL. No Cloudflare account or DNS
+setup required — cloudflared opens a persistent QUIC connection to
+Cloudflare's edge and Cloudflare hands back a hostname.
+
+```ts
+// Inside a Worker with an RPC-transport sandbox:
+const tunnel = await sandbox.tunnels.get(8080);
+console.log(tunnel.url);
+// → https://random-words-here.trycloudflare.com
+
+// Repeated calls for the same port return the same record:
+const same = await sandbox.tunnels.get(8080);
+console.log(same.url === tunnel.url); // true
+
+// Tear down by port number or by the record:
+await sandbox.tunnels.destroy(8080);
+// or: await sandbox.tunnels.destroy(tunnel);
+```
+
+`get()` is idempotent: it consults a per-sandbox cache in Durable
+Object storage, returns the cached record on a hit, and only spawns a
+fresh cloudflared process on a miss. `list()` returns every cached
+tunnel.
+
+Notes:
+
+- Requires the RPC transport. The route-based transport's `tunnels`
+  stub throws "RPC transport required".
+- URLs do **not** survive a container restart. Cloudflare assigns the
+  hostname during cloudflared's startup handshake, so every restart
+  yields a new URL. The SDK clears its cache on container start, so
+  the next `get(port)` after a restart returns a fresh record.
+- The first fetch through a brand-new URL can take a couple of
+  seconds while DNS propagates, even after `get()` resolves.
+- `*.trycloudflare.com` buffers `text/event-stream` responses.
+  WebSockets work fine.
+- Local builds behind a TLS-intercepting proxy (e.g. Cloudflare WARP)
+  need the host CA bundle injected at build time — see
+  [DOCKER_README.md](../../DOCKER_README.md).
+
 ## Documentation
 
 **📖 [Full Documentation](https://developers.cloudflare.com/sandbox/)**
@@ -115,6 +158,7 @@ export default {
 - **File System Access** - Read, write, and manage files
 - **Command Execution** - Run any command with streaming support
 - **Preview URLs** - Expose services with public URLs
+- **Quick tunnels** - Zero-config `*.trycloudflare.com` URLs via `sandbox.tunnels.get(port)`
 - **Git Integration** - Clone repositories directly
 
 ## Contributing
@@ -156,6 +200,7 @@ See the [examples directory](./examples) for complete working examples:
 - [Claude Code](./examples/claude-code) - Run [Claude Code](https://claude.ai/code) headless on any repo
 - [OpenAI Agents](./examples/openai-agents) - `Shell` and `Editor` tools for [OpenAI Agents SDK](https://openai.github.io/openai-agents-js/)
 - [OpenCode](./examples/opencode) - [OpenCode](https://github.com/sst/opencode) web UI or [SDK](https://opencode.ai/docs/sdk/) in a sandbox
+- [Git Repo Per Sandbox](./examples/git-repo-per-sandbox) - One Artifacts Git repo per sandbox
 - [TypeScript Validator](./examples/typescript-validator) - Build with npm in sandbox, execute in [isolates](https://developers.cloudflare.com/workers/runtime-apis/bindings/worker-loader/)
 
 ## Status

package/skills/void/docs/node_modules/void/node_modules/@electric-sql/pglite/README.md

@@ -7,7 +7,7 @@
       <source media="(prefers-color-scheme: light)"
           srcset="https://raw.githubusercontent.com/electric-sql/pglite/main/docs/public/img/brand/logo-light.svg"
       />
-      <img alt="ElectricSQL logo"
+      <img alt="PGlite logo"
           src="https://raw.githubusercontent.com/electric-sql/pglite/main/docs/public/img/brand/logo-light.svg"
       />
     </picture>
@@ -15,7 +15,7 @@
 </p>
 
 <p align="center">
-  <a href="https://pglite.dev">PGlite</a> - the WASM build of Postgres from <a href="https://electric-sql.com" target="_blank">ElectricSQL</a>.<br>
+  <a href="https://pglite.dev">PGlite</a> - the WASM build of Postgres from <a href="https://electric.ax" target="_blank">Electric</a>.<br>
   Build reactive, realtime, local-first apps directly on Postgres.
 <p>
 
@@ -33,7 +33,7 @@
 
 ![PGlite](https://raw.githubusercontent.com/electric-sql/pglite/main/screenshot.png)
 
-PGlite is a WASM Postgres build packaged into a TypeScript client library that enables you to run Postgres in the browser, Node.js, Bun and Deno, with no need to install any other dependencies. It is only 3mb gzipped and has support for many Postgres extensions, including [pgvector](https://github.com/pgvector/pgvector).
+PGlite is a WASM Postgres build packaged into a TypeScript client library that enables you to run Postgres in the browser, Node.js, Bun and Deno, with no need to install any other dependencies. It is only 3mb gzipped and has support for many Postgres extensions, including [pgvector](https://github.com/pgvector/pgvector) and [PostGIS](https://postgis.net).
 
 ```javascript
 import { PGlite } from '@electric-sql/pglite'
@@ -180,10 +180,10 @@ And follow the instructions to create an appropriate changeset. Please ensure an
 
 ## Acknowledgments
 
-PGlite builds on the work of [Stas Kelvich](https://github.com/kelvich) of [Neon](https://neon.tech) in this [Postgres fork](https://github.com/electric-sql/postgres-wasm).
+PGlite builds on the work of [Stas Kelvich](https://github.com/kelvich) of [Neon](https://neon.tech) in this [Postgres fork](https://github.com/electric-sql/postgres-pglite).
 
 ## License
 
 PGlite is dual-licensed under the terms of the [Apache License 2.0](https://github.com/electric-sql/pglite/blob/main/LICENSE) and the [PostgreSQL License](https://github.com/electric-sql/pglite/blob/main/POSTGRES-LICENSE), you can choose which you prefer.
 
-Changes to the [Postgres source](https://github.com/electric-sql/postgres-wasm) are licensed under the PostgreSQL License.
+Changes to the [Postgres source](https://github.com/electric-sql/postgres-pglite) are licensed under the PostgreSQL License.

package/skills/void/docs/node_modules/void/node_modules/@types/node/README.md

@@ -8,7 +8,7 @@ This package contains type definitions for node (https://nodejs.org/).
 Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node.
 
 ### Additional Details
- * Last updated: Thu, 07 May 2026 22:21:35 GMT
+ * Last updated: Wed, 01 Jul 2026 11:03:38 GMT
  * Dependencies: [undici-types](https://npmjs.com/package/undici-types)
 
 # Credits

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/@types/node/README.md

@@ -8,7 +8,7 @@ This package contains type definitions for node (https://nodejs.org/).
 Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node.
 
 ### Additional Details
- * Last updated: Thu, 07 May 2026 22:21:35 GMT
+ * Last updated: Wed, 01 Jul 2026 11:03:38 GMT
  * Dependencies: [undici-types](https://npmjs.com/package/undici-types)
 
 # Credits

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/markdown-exit/README.md

@@ -5,6 +5,7 @@
 [![npm version][npm-version-src]][npm-version-href]
 [![bundle][bundle-src]][bundle-href]
 [![License][license-src]][license-href]
+[![CodSpeed][codspeed-src]][codspeed-href]
 
 A TypeScript rewrite of [markdown-it](https://github.com/markdown-it/markdown-it) with first-class typings, modern tooling, and enhancements.
 
@@ -13,7 +14,7 @@ A TypeScript rewrite of [markdown-it](https://github.com/markdown-it/markdown-it
 - 🛡️ **Type Safety:** Ship robust types, improve DX, and enable type-safe development.
 - ⚡ **New features:** [Async rendering](https://markdown-exit.pages.dev/guide/rendering.html#async-rendering) for all rules includeing syntax highlighting and [more](https://github.com/serkodev/markdown-exit/issues?q=is:issue%20label:features).
 - 🔌 **Extensibility:** Extend the markdown syntax, custom rendering with [Plugins](https://markdown-exit.pages.dev/guide/plugins.html).
-- 🤝 **Compatibility:** Compatible with markdown-it `v14.1.0` and plugin API.
+- 🤝 **Compatibility:** Compatible with markdown-it `v14.2.0` and plugin API.
 
 ## Documentation
 
@@ -122,3 +123,5 @@ This project owes its foundation to the [markdown-it](https://github.com/markdow
 [bundle-href]: https://bundlephobia.com/result?p=markdown-exit
 [license-src]: https://img.shields.io/github/license/serkodev/markdown-exit.svg?style=flat&colorA=00AF6B&colorB=000
 [license-href]: https://github.com/serkodev/markdown-exit/blob/main/LICENSE
+[codspeed-src]: https://img.shields.io/badge/CodSpeed-benchmark-blue
+[codspeed-href]: https://codspeed.io/serkodev/markdown-exit?utm_source=badge

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/markdown-it-attrs/README.md

@@ -47,8 +47,7 @@ nums = [x for x in range(10)]
 
 Output:
 ```html
-<pre><code data="asdf" class="language-python">
-nums = [x for x in range(10)]
+<pre data="asdf"><code class="language-python">nums = [x for x in range(10)]
 </code></pre>
 ```
 
@@ -293,35 +292,53 @@ Output:
 If you need finer control, [decorate](https://github.com/rstacruz/markdown-it-decorate) might help you.
 
 ## Custom rendering
-If you would like some other output, you can override renderers:
+By default, fenced code block attributes are rendered on `<pre>`.
+
+If you prefer markdown-it's default behavior (attributes on `<code>`), opt out:
 
 ```js
 const md = require('markdown-it')();
 const markdownItAttrs = require('markdown-it-attrs');
 
-md.use(markdownItAttrs);
+md.use(markdownItAttrs, {
+  fenceAttrsOnPre: false
+});
+```
+
+If you need fully custom output, define your own `fence` renderer. The plugin
+will not override an existing custom `fence` renderer.
+
+```js
+const md = require('markdown-it')();
+const markdownItAttrs = require('markdown-it-attrs');
 
-// custom renderer for fences
 md.renderer.rules.fence = function (tokens, idx, options, env, slf) {
   const token = tokens[idx];
-  return  '<pre' + slf.renderAttrs(token) + '>'
-    + '<code>' + token.content + '</code>'
-    + '</pre>';
-}
+  const info = token.info ? token.info.trim() : '';
+  const langName = info ? info.split(/\s+/g)[0] : '';
+  const langClass = langName ? ' class="' + options.langPrefix + langName + '"' : '';
+  const content = md.utils.escapeHtml(token.content);
+
+  return '<pre' + slf.renderAttrs(token) + '><code' + langClass + '>'
+    + content
+    + '</code></pre>\n';
+};
+
+md.use(markdownItAttrs);
 
-let src = [
+const src = [
   '',
   '```js {.abcd}',
   'var a = 1;',
   '```'
-].join('\n')
+].join('\n');
 
 console.log(md.render(src));
 ```
 
 Output:
 ```html
-<pre class="abcd"><code>var a = 1;
+<pre class="abcd"><code class="language-js">var a = 1;
 </code></pre>
 ```
 

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/tinyglobby/README.md

@@ -1,7 +1,7 @@
 # tinyglobby
 
 [![npm version](https://img.shields.io/npm/v/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
-[![monthly downloads](https://img.shields.io/npm/dm/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
+[![weekly downloads](https://img.shields.io/npm/dw/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
 
 A fast and minimal alternative to globby and fast-glob, meant to behave the same way.
 

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/AGENTS.md

@@ -11,5 +11,6 @@ Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.de
 - [ ] Run `vp install` after pulling remote changes and before getting started.
 - [ ] Run `vp check` and `vp test` to format, lint, type check and test changes.
 - [ ] Check if there are `vite.config.ts` tasks or `package.json` scripts necessary for validation, run via `vp run <script>`.
+- [ ] If setup, runtime, or package-manager behavior looks wrong, run `vp env doctor` and include its output when asking for help.
 
 <!--VITE PLUS END-->

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/README.md

@@ -3,7 +3,7 @@
 **The Unified Toolchain for the Web**
 _runtime and package management, create, dev, check, test, build, pack, and monorepo task caching in a single dependency_
 
-This package provides the project-local version of Vite+. The global `vite` command automatically delegates to this package for all project-specific tasks.
+This package provides the project-local version of Vite+. The global `vp` command automatically delegates to this package for all project-specific tasks.
 
 ---
 
@@ -111,6 +111,7 @@ Use `vp migrate` to migrate to Vite+. It merges tool-specific config files such
 
 - **run** - Run monorepo tasks
 - **exec** - Execute a command from local `node_modules/.bin`
+- **node** - Run a Node.js script with the resolved Vite+ environment
 - **dlx** - Execute a package binary without installing it as a dependency
 - **cache** - Manage the task cache
 
@@ -122,7 +123,7 @@ Use `vp migrate` to migrate to Vite+. It merges tool-specific config files such
 
 #### Manage Dependencies
 
-Vite+ automatically wraps your package manager (pnpm, npm, or Yarn) based on `packageManager` and lockfiles:
+Vite+ automatically wraps your package manager (pnpm, npm, Yarn, or Bun) based on `packageManager` and lockfiles:
 
 - **add** - Add packages to dependencies
 - **remove** (`rm`, `un`, `uninstall`) - Remove packages from dependencies
@@ -133,6 +134,7 @@ Vite+ automatically wraps your package manager (pnpm, npm, or Yarn) based on `pa
 - **why** (`explain`) - Show why a package is installed
 - **info** (`view`, `show`) - View package metadata from the registry
 - **link** (`ln`) / **unlink** - Manage local package links
+- **rebuild** - Rebuild native modules
 - **pm** - Forward a command to the package manager
 
 #### Maintain
@@ -150,6 +152,16 @@ vp create
 
 You can run `vp create` inside of a project to add new apps or libraries to your project.
 
+Organizations can expose a curated set of templates under their npm scope by
+publishing `@org/create` with a `createConfig.templates` manifest in its `package.json`.
+Once published, `vp create @org` opens an interactive picker over those
+templates, and setting `create: { defaultTemplate: '@org' }` in
+`vite.config.ts` makes it the default for bare `vp create`. See the
+[Organization Templates guide](https://viteplus.dev/guide/create#organization-templates)
+for the authoring workflow and
+[`create.defaultTemplate`](https://viteplus.dev/config/create) for the
+config reference.
+
 ### Migrating an existing project
 
 You can migrate an existing project to Vite+:
@@ -177,12 +189,12 @@ If you are manually migrating a project to Vite+, install these dev dependencies
 npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
 ```
 
-You need to add overrides to your package manager for `vite` and `vitest` so that other packages depending on Vite and Vitest will use the Vite+ versions:
+You need to add overrides to your package manager so that other packages resolve the Vite+ versions: alias `vite` to `@voidzero-dev/vite-plus-core`, and pin `vitest` to the version Vite+ bundles (run `vp --version`) so the whole project shares a single Vitest copy with `vp test`. Without the `vitest` pin, a dependency or workspace package can pull a different Vitest than the bundled runner, splitting Vitest's internals (mocks, `expect`, runner state):
 
 ```json
 "overrides": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+  "vitest": "4.1.9"
 }
 ```
 
@@ -191,7 +203,7 @@ If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
 ```yaml
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: npm:@voidzero-dev/vite-plus-test@latest
+  vitest: 4.1.9
 ```
 
 Or, if you are using Yarn:
@@ -199,7 +211,7 @@ Or, if you are using Yarn:
 ```json
 "resolutions": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+  "vitest": "4.1.9"
 }
 ```
 

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/build.md

@@ -4,7 +4,7 @@
 
 ## Example
 
-```ts
+```ts [vite.config.ts]
 import { defineConfig } from 'vite-plus';
 
 export default defineConfig({

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/check.md

@@ -0,0 +1,35 @@
+# Check Config
+
+`vp check` runs format, lint, and type checks together. The `check` block in `vite.config.ts` sets defaults for the composite command, mirroring the `--no-fmt` and `--no-lint` CLI flags.
+
+This is useful when a project wants to keep most of the toolchain but skip one step by default. For example, a team that lints but does not format can disable `check.fmt` so a plain `vp check` (the command agents and contributors run most) only lints, without anyone needing to remember `--no-fmt`.
+
+## Example
+
+```ts [vite.config.ts]
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  check: {
+    // Skip the format step in `vp check`. Defaults to true.
+    fmt: false,
+    // Skip lint rules in `vp check`. Type-check still runs when both
+    // `lint.options.typeAware` and `lint.options.typeCheck` are enabled.
+    // Defaults to true.
+    lint: true,
+  },
+});
+```
+
+When a step is disabled here, `vp check` prints a short `note:` line so it is clear why the step did not run. With the `check.fmt: false` config above:
+
+```bash
+$ vp check
+note: Format skipped (check.fmt: false in vite.config.ts)
+pass: Found no warnings or lint errors in 1 file (12ms, 8 threads)
+```
+
+## Scope and precedence
+
+- These options only affect the composite `vp check`. Standalone [`vp fmt`](/config/fmt) and [`vp lint`](/config/lint) are unaffected, so you can still run a disabled tool directly when you need it once. Note that any `vp check` invocation honors these defaults, including one run from a pre-commit hook: if your [`staged`](/config/staged) tasks call `vp check`, that step is skipped there too.
+- A step is skipped if the config disables it **or** the matching CLI flag is passed. There is no flag to re-enable a step disabled in config; run `vp fmt` or `vp lint` directly instead.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/config/create.md

@@ -0,0 +1,70 @@
+# Create Config
+
+`vp create` reads the `create` block in `vite.config.ts` to set per-repo defaults. See the [Creating a Project guide](/guide/create#organization-templates) for the full `@org` template workflow.
+
+## `create.defaultTemplate`
+
+When `vp create` is invoked with no `TEMPLATE` argument, Vite+ uses this value as if the user had typed it. Typically set to an npm scope whose `@scope/create` package publishes a `createConfig.templates` manifest — so bare `vp create` drops into the org picker.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  create: {
+    defaultTemplate: '@your-org',
+  },
+});
+```
+
+Any value accepted by `vp create` as a first argument works here: `@your-org` for an org picker, `@your-org:web` for a direct manifest entry, `vite:application` for a built-in, or the `name` of a local `create.templates` entry (see below).
+
+## `create.templates`
+
+Declare local templates available to `vp create` inside a monorepo. Each entry is listed in the `vp create` picker, and selecting it (or passing its `name` as the template argument) runs the resolved `template`.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  create: {
+    templates: [
+      {
+        name: 'component',
+        description: 'Internal UI component',
+        template: './tools/create-component',
+      },
+      { name: 'service', description: 'Backend service', template: 'service-generator' },
+    ],
+  },
+});
+```
+
+Each entry has:
+
+| Field         | Required | Notes                                                                                                                                                                                                                                            |
+| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `name`        | yes      | Identifier shown in the picker and accepted as `vp create <name>`. Must be unique within the array. The `vite:` prefix is reserved for built-in templates.                                                                                       |
+| `description` | yes      | One-line description shown in the picker.                                                                                                                                                                                                        |
+| `template`    | yes      | A workspace package name, a relative `./path` to a local package's directory (resolved against the workspace root), a `vite:*` built-in, a GitHub URL, or a full npm package name (e.g. `create-foo`). It is run as-is (not shorthand-expanded). |
+
+`create.templates` is the source of truth for local templates: only entries listed here appear in the picker. Vite+ does not infer templates from package.json keywords. A `create.templates` entry whose `template` does not match any workspace package, or resolves to a local package without a `bin`, is reported as an error rather than falling through to an unrelated npm package.
+
+[`vp create vite:generator`](/guide/create#code-generators) adds an entry here automatically (idempotently, preserving `defaultTemplate`); you can also edit the list by hand.
+
+`create.defaultTemplate` can name a local entry, so bare `vp create` opens it directly.
+
+## Precedence
+
+CLI argument > `create.defaultTemplate` > the standard built-in picker.
+
+Explicit specifiers always win, so scripts and CI can bypass the configured default:
+
+```bash
+# Uses create.defaultTemplate
+vp create
+
+# Explicitly ignores the default
+vp create vite:library
+```
+
+The org picker also appends a trailing "Vite+ built-in templates" entry — selecting it routes to the `vite:monorepo` / `vite:application` / `vite:library` / `vite:generator` flow, so built-ins stay reachable interactively even when a default is configured.