void 0.10.8 → 0.10.11

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

@@ -0,0 +1,64 @@
+# pathslash
+
+> `node:path`, platform-correct, with forward-slash output.
+
+`pathslash` is a tiny wrapper around `node:path` that always outputs forward slashes (`/`) while keeping the correct per-platform semantics. It never reimplements path logic. Every function delegates to `node:path` and only flips the separators in the result.
+
+## Why
+
+- **Forward slashes everywhere.** On Windows, the `win32` functions output `/` instead of `\`, which is what bundlers, route maps, and URLs expect.
+- **Correct semantics for free.** Drive letters, UNC paths, and case-insensitive `relative` behave exactly as in `node:path`, because they _are_ `node:path`.
+- **POSIX-safe.** On POSIX, a backslash is a valid filename character, so it is never rewritten there.
+- **A typed drop-in.** Same API and types as `node:path`.
+
+## Install
+
+```sh
+npm i pathslash
+```
+
+## Usage
+
+The default export and the top-level named exports follow the host platform, exactly like `node:path`:
+
+```ts
+import path, { join } from "pathslash";
+
+join("src", "a.ts"); // 'src/a.ts'
+path.sep; // '/'
+```
+
+To force a specific platform, use the `win32` and `posix` namespaces. They work on any host OS:
+
+```ts
+import { win32, posix } from "pathslash";
+
+win32.join("C:\\a", "b"); // 'C:/a/b'  (forward slashes)
+win32.normalize("C:\\a\\..\\b"); // 'C:/b'
+win32.relative("C:/Foo/Bar", "C:/foo/baz"); // '../baz'  (case-insensitive)
+
+posix.join("a", "b\\c"); // 'a/b\\c'  (backslash kept)
+```
+
+### `toSlash(path)`
+
+Safely normalizes separators to `/`. On Windows it converts `\` to `/`. On POSIX it returns the path unchanged, because a backslash is a valid filename character there and rewriting it would corrupt the path. Use it for paths that come from outside this package, such as `process.cwd()`:
+
+```ts
+import { toSlash } from "pathslash";
+
+toSlash("C:\\a\\b"); // 'C:/a/b' on Windows, unchanged on POSIX
+```
+
+## Notes
+
+- `win32.sep` is `"/"` instead of `"\\"`, and `win32.delimiter` stays `";"`.
+- `\\?\` (extended-length) paths stay verbatim. `toSlash` and every `win32.*` function leave them untouched, because a forward slash is a literal character there, not a separator.
+- `toNamespacedPath` always returns a native, backslash path, since `\\?\` paths are only valid with backslashes.
+- `matchesGlob` mirrors `node:path`. It exists only on Node versions that ship it (22.5+) and is `undefined` on older ones.
+- The types are a drop-in too: `import type { ParsedPath, FormatInputPathObject, PlatformPath } from "pathslash"`.
+- Everything else matches `node:path`, separators aside.
+
+## License
+
+[MIT](./LICENSE)

package/skills/void/docs/node_modules/void/node_modules/pathslash/README.md

@@ -0,0 +1,64 @@
+# pathslash
+
+> `node:path`, platform-correct, with forward-slash output.
+
+`pathslash` is a tiny wrapper around `node:path` that always outputs forward slashes (`/`) while keeping the correct per-platform semantics. It never reimplements path logic. Every function delegates to `node:path` and only flips the separators in the result.
+
+## Why
+
+- **Forward slashes everywhere.** On Windows, the `win32` functions output `/` instead of `\`, which is what bundlers, route maps, and URLs expect.
+- **Correct semantics for free.** Drive letters, UNC paths, and case-insensitive `relative` behave exactly as in `node:path`, because they _are_ `node:path`.
+- **POSIX-safe.** On POSIX, a backslash is a valid filename character, so it is never rewritten there.
+- **A typed drop-in.** Same API and types as `node:path`.
+
+## Install
+
+```sh
+npm i pathslash
+```
+
+## Usage
+
+The default export and the top-level named exports follow the host platform, exactly like `node:path`:
+
+```ts
+import path, { join } from "pathslash";
+
+join("src", "a.ts"); // 'src/a.ts'
+path.sep; // '/'
+```
+
+To force a specific platform, use the `win32` and `posix` namespaces. They work on any host OS:
+
+```ts
+import { win32, posix } from "pathslash";
+
+win32.join("C:\\a", "b"); // 'C:/a/b'  (forward slashes)
+win32.normalize("C:\\a\\..\\b"); // 'C:/b'
+win32.relative("C:/Foo/Bar", "C:/foo/baz"); // '../baz'  (case-insensitive)
+
+posix.join("a", "b\\c"); // 'a/b\\c'  (backslash kept)
+```
+
+### `toSlash(path)`
+
+Safely normalizes separators to `/`. On Windows it converts `\` to `/`. On POSIX it returns the path unchanged, because a backslash is a valid filename character there and rewriting it would corrupt the path. Use it for paths that come from outside this package, such as `process.cwd()`:
+
+```ts
+import { toSlash } from "pathslash";
+
+toSlash("C:\\a\\b"); // 'C:/a/b' on Windows, unchanged on POSIX
+```
+
+## Notes
+
+- `win32.sep` is `"/"` instead of `"\\"`, and `win32.delimiter` stays `";"`.
+- `\\?\` (extended-length) paths stay verbatim. `toSlash` and every `win32.*` function leave them untouched, because a forward slash is a literal character there, not a separator.
+- `toNamespacedPath` always returns a native, backslash path, since `\\?\` paths are only valid with backslashes.
+- `matchesGlob` mirrors `node:path`. It exists only on Node versions that ship it (22.5+) and is `undefined` on older ones.
+- The types are a drop-in too: `import type { ParsedPath, FormatInputPathObject, PlatformPath } from "pathslash"`.
+- Everything else matches `node:path`, separators aside.
+
+## License
+
+[MIT](./LICENSE)

package/skills/void/docs/node_modules/void/node_modules/proper-lockfile/CHANGELOG.md

@@ -0,0 +1,108 @@
+# Change Log
+
+All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
+
+<a name="4.1.2"></a>
+## [4.1.2](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.1...v4.1.2) (2021-01-25)
+
+
+### Bug Fixes
+
+* fix node 14 updating graceful-fs ([#102](https://github.com/moxystudio/node-proper-lockfile/issues/102)) ([b0d988e](https://github.com/moxystudio/node-proper-lockfile/commit/b0d988e))
+
+
+
+<a name="4.1.1"></a>
+## [4.1.1](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.0...v4.1.1) (2019-04-03)
+
+
+### Bug Fixes
+
+* fix mtime precision on some filesystems ([#88](https://github.com/moxystudio/node-proper-lockfile/issues/88)) ([f266158](https://github.com/moxystudio/node-proper-lockfile/commit/f266158)), closes [#82](https://github.com/moxystudio/node-proper-lockfile/issues/82) [#87](https://github.com/moxystudio/node-proper-lockfile/issues/87)
+
+
+
+<a name="4.1.0"></a>
+# [4.1.0](https://github.com/moxystudio/node-proper-lockfile/compare/v4.0.0...v4.1.0) (2019-03-18)
+
+
+### Features
+
+* allow second precision in mtime comparison ([#78](https://github.com/moxystudio/node-proper-lockfile/issues/78)) ([b2816a6](https://github.com/moxystudio/node-proper-lockfile/commit/b2816a6))
+
+
+
+<a name="4.0.0"></a>
+# [4.0.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.2.0...v4.0.0) (2019-03-12)
+
+
+### Bug Fixes
+
+* fix typo in error message ([#68](https://github.com/moxystudio/node-proper-lockfile/issues/68)) ([b91cb55](https://github.com/moxystudio/node-proper-lockfile/commit/b91cb55))
+
+
+### Features
+
+* make staleness check more robust ([#74](https://github.com/moxystudio/node-proper-lockfile/issues/74)) ([9cc0973](https://github.com/moxystudio/node-proper-lockfile/commit/9cc0973)), closes [#71](https://github.com/moxystudio/node-proper-lockfile/issues/71) [/github.com/ipfs/js-ipfs-repo/issues/188#issuecomment-468682971](https://github.com//github.com/ipfs/js-ipfs-repo/issues/188/issues/issuecomment-468682971)
+
+
+### BREAKING CHANGES
+
+* We were marking the lock as compromised when system went into sleep or if the event loop was busy taking too long to run the internals timers, Now we keep track of the mtime updated by the current process, and if we lose some cycles in the update process but recover and the mtime is still ours we do not mark the lock as compromised.
+
+
+
+<a name="3.2.0"></a>
+# [3.2.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.1.0...v3.2.0) (2018-11-19)
+
+
+### Features
+
+* add lock path option ([#66](https://github.com/moxystudio/node-proper-lockfile/issues/66)) ([32f1b8d](https://github.com/moxystudio/node-proper-lockfile/commit/32f1b8d))
+
+
+
+<a name="3.1.0"></a>
+# [3.1.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.2...v3.1.0) (2018-11-15)
+
+
+### Bug Fixes
+
+* **package:** update retry to version 0.12.0 ([#50](https://github.com/moxystudio/node-proper-lockfile/issues/50)) ([d400b98](https://github.com/moxystudio/node-proper-lockfile/commit/d400b98))
+
+
+### Features
+
+* add signal exit ([#65](https://github.com/moxystudio/node-proper-lockfile/issues/65)) ([f20bc45](https://github.com/moxystudio/node-proper-lockfile/commit/f20bc45))
+
+
+
+<a name="3.0.2"></a>
+## [3.0.2](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.1...v3.0.2) (2018-01-30)
+
+
+
+<a name="3.0.1"></a>
+## [3.0.1](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.0...v3.0.1) (2018-01-20)
+
+
+### Bug Fixes
+
+* restore ability to use lockfile() directly ([0ef8fbc](https://github.com/moxystudio/node-proper-lockfile/commit/0ef8fbc))
+
+
+
+<a name="3.0.0"></a>
+# [3.0.0](https://github.com/moxystudio/node-proper-lockfile/compare/v2.0.1...v3.0.0) (2018-01-20)
+
+
+### Chores
+
+* update project to latest node lts ([b1d43e5](https://github.com/moxystudio/node-proper-lockfile/commit/b1d43e5))
+
+
+### BREAKING CHANGES
+
+* remove callback support
+* use of node lts language features such as object spread
+* compromised function in lock() has been moved to an option

package/skills/void/docs/node_modules/void/node_modules/proper-lockfile/README.md

@@ -0,0 +1,183 @@
+# proper-lockfile
+
+[![NPM version][npm-image]][npm-url] [![Downloads][downloads-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Coverage Status][codecov-image]][codecov-url] [![Dependency status][david-dm-image]][david-dm-url] [![Dev Dependency status][david-dm-dev-image]][david-dm-dev-url]
+
+[npm-url]:https://npmjs.org/package/proper-lockfile
+[downloads-image]:https://img.shields.io/npm/dm/proper-lockfile.svg
+[npm-image]:https://img.shields.io/npm/v/proper-lockfile.svg
+[travis-url]:https://travis-ci.org/moxystudio/node-proper-lockfile
+[travis-image]:https://img.shields.io/travis/moxystudio/node-proper-lockfile/master.svg
+[codecov-url]:https://codecov.io/gh/moxystudio/node-proper-lockfile
+[codecov-image]:https://img.shields.io/codecov/c/github/moxystudio/node-proper-lockfile/master.svg
+[david-dm-url]:https://david-dm.org/moxystudio/node-proper-lockfile
+[david-dm-image]:https://img.shields.io/david/moxystudio/node-proper-lockfile.svg
+[david-dm-dev-url]:https://david-dm.org/moxystudio/node-proper-lockfile?type=dev
+[david-dm-dev-image]:https://img.shields.io/david/dev/moxystudio/node-proper-lockfile.svg
+
+An inter-process and inter-machine lockfile utility that works on a local or network file system.
+
+
+## Installation
+
+`$ npm install proper-lockfile`
+
+
+## Design
+
+There are various ways to achieve [file locking](http://en.wikipedia.org/wiki/File_locking).
+
+This library utilizes the `mkdir` strategy which works atomically on any kind of file system, even network based ones.
+The lockfile path is based on the file path you are trying to lock by suffixing it with `.lock`.
+
+When a lock is successfully acquired, the lockfile's `mtime` (modified time) is periodically updated to prevent staleness. This allows to effectively check if a lock is stale by checking its `mtime` against a stale threshold. If the update of the mtime fails several times, the lock might be compromised. The `mtime` is [supported](http://en.wikipedia.org/wiki/Comparison_of_file_systems) in almost every `filesystem`.
+
+
+### Comparison
+
+This library is similar to [lockfile](https://github.com/isaacs/lockfile) but the latter has some drawbacks:
+
+- It relies on `open` with `O_EXCL` flag which has problems in network file systems. `proper-lockfile` uses `mkdir` which doesn't have this issue.
+
+> O_EXCL is broken on NFS file systems; programs which rely on it for performing locking tasks will contain a race condition.
+
+- The lockfile staleness check is done via `ctime` (creation time) which is unsuitable for long running processes. `proper-lockfile` constantly updates lockfiles `mtime` to do proper staleness check.
+
+- It does not check if the lockfile was compromised which can lead to undesirable situations. `proper-lockfile` checks the lockfile when updating the `mtime`.
+
+- It has a default value of `0` for the stale option which isn't good because any crash or process kill that the package can't handle gracefully will leave the lock active forever.
+
+
+### Compromised
+
+`proper-lockfile` does not detect cases in which:
+
+- A `lockfile` is manually removed and someone else acquires the lock right after
+- Different `stale`/`update` values are being used for the same file, possibly causing two locks to be acquired on the same file
+
+`proper-lockfile` detects cases in which:
+
+- Updates to the `lockfile` fail
+- Updates take longer than expected, possibly causing the lock to become stale for a certain amount of time
+
+
+As you see, the first two are a consequence of bad usage. Technically, it was possible to detect the first two but it would introduce complexity and eventual race conditions.
+
+
+## Usage
+
+### .lock(file, [options])
+
+Tries to acquire a lock on `file` or rejects the promise on error.
+
+If the lock succeeds, a `release` function is provided that should be called when you want to release the lock. The `release` function also rejects the promise on error (e.g. when the lock was already compromised).
+
+Available options:
+
+- `stale`: Duration in milliseconds in which the lock is considered stale, defaults to `10000` (minimum value is `5000`)
+- `update`: The interval in milliseconds in which the lockfile's `mtime` will be updated, defaults to `stale/2` (minimum value is `1000`, maximum value is `stale/2`)
+- `retries`: The number of retries or a [retry](https://www.npmjs.org/package/retry) options object, defaults to `0`
+- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
+- `fs`: A custom fs to use, defaults to `graceful-fs`
+- `onCompromised`: Called if the lock gets compromised, defaults to a function that simply throws the error which will probably cause the process to die
+- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
+
+
+```js
+const lockfile = require('proper-lockfile');
+
+lockfile.lock('some/file')
+.then((release) => {
+    // Do something while the file is locked
+
+    // Call the provided release function when you're done,
+    // which will also return a promise
+    return release();
+})
+.catch((e) => {
+    // either lock could not be acquired
+    // or releasing it failed
+    console.error(e)
+});
+
+// Alternatively, you may use lockfile('some/file') directly.
+```
+
+
+### .unlock(file, [options])
+
+Releases a previously acquired lock on `file` or rejects the promise on error.
+
+Whenever possible you should use the `release` function instead (as exemplified above). Still there are cases in which it's hard to keep a reference to it around code. In those cases `unlock()` might be handy.
+
+Available options:
+
+- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
+- `fs`: A custom fs to use, defaults to `graceful-fs`
+- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
+
+
+```js
+const lockfile = require('proper-lockfile');
+
+lockfile.lock('some/file')
+.then(() => {
+    // Do something while the file is locked
+
+    // Later..
+    return lockfile.unlock('some/file');
+});
+```
+
+### .check(file, [options])
+
+Check if the file is locked and its lockfile is not stale, rejects the promise on error.
+
+Available options:
+
+- `stale`: Duration in milliseconds in which the lock is considered stale, defaults to `10000` (minimum value is `5000`)
+- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
+- `fs`: A custom fs to use, defaults to `graceful-fs`
+- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
+
+
+```js
+const lockfile = require('proper-lockfile');
+
+lockfile.check('some/file')
+.then((isLocked) => {
+    // isLocked will be true if 'some/file' is locked, false otherwise
+});
+```
+
+### .lockSync(file, [options])
+
+Sync version of `.lock()`.   
+Returns the `release` function or throws on error.
+
+### .unlockSync(file, [options])
+
+Sync version of `.unlock()`.   
+Throws on error.
+
+### .checkSync(file, [options])
+
+Sync version of `.check()`.
+Returns a boolean or throws on error.
+
+
+## Graceful exit
+
+`proper-lockfile` automatically removes locks if the process exits, except if the process is killed with SIGKILL or it crashes due to a VM fatal error (e.g.: out of memory).
+
+
+## Tests
+
+`$ npm test`   
+`$ npm test -- --watch` during development
+
+The test suite is very extensive. There's even a stress test to guarantee exclusiveness of locks.
+
+
+## License
+
+Released under the [MIT License](https://www.opensource.org/licenses/mit-license.php).

package/skills/void/docs/node_modules/void/skills/void/SKILL.md

@@ -32,39 +32,40 @@ Then ask what to do next.
 
 ## Task Routing
 
-| User intent                               | Docs file(s)                                                                              |
-| ----------------------------------------- | ----------------------------------------------------------------------------------------- |
-| CLI command syntax, flags, env vars       | `docs/reference/cli.md`                                                                   |
-| Initial setup, onboarding, first app      | `docs/guide/quickstart.md`, `docs/reference/cli.md`                                       |
-| App type detection and mode behavior      | `docs/guide/app-types.md`, `docs/reference/config.md`                                     |
-| Server/API routing and middleware         | `docs/guide/server-routing.md`, `docs/integrations/hono.md`                               |
-| Pages mode, loader/action, forms, layouts | `docs/guide/pages-routing/*.md`, `docs/guide/type-safety.md`                              |
-| Database and migrations                   | `docs/guide/database.md`, `docs/guide/type-safety.md`                                     |
-| Typed fetch and end-to-end typing         | `docs/guide/typed-fetch.md`, `docs/guide/type-safety.md`                                  |
-| Authentication                            | `docs/guide/auth.md`, `docs/guide/env-vars.md`                                            |
-| Cloudflare runtime bindings and config    | `docs/integrations/cloudflare.md`, `docs/reference/config.md`, `docs/guide/env-vars.md`   |
-| AI inference (Workers AI, providers)      | `docs/guide/ai.md`                                                                        |
-| KV / storage / queues / cron jobs         | `docs/guide/kv.md`, `docs/guide/storage.md`, `docs/guide/queues.md`, `docs/guide/jobs.md` |
-| SSR and caching                           | `docs/guide/ssr.md`, `docs/guide/edge/*.md`                                               |
-| Rewrites, redirects, fallbacks            | `docs/guide/edge/rewrites.md`, `docs/guide/edge/redirects.md`, `docs/reference/config.md` |
-| Static site generation                    | `docs/guide/ssg.md`                                                                       |
-| Deployment and CI                         | `docs/guide/deployment.md`, `docs/reference/cli.md`                                       |
-| Project status, deployment history        | `docs/reference/cli.md`                                                                   |
-| Cache purging                             | `docs/reference/cli.md`                                                                   |
-| Project logs, runtime errors              | `docs/reference/cli.md`                                                                   |
-| Secrets management (put/sync/delete)      | `docs/reference/cli.md`, `docs/guide/env-vars.md`                                         |
-| Typed env vars (`defineEnv`, `env.ts`)    | `docs/guide/env-vars.md`                                                                  |
-| Custom domain setup                       | `docs/reference/cli.md`                                                                   |
-| Database status, reset, seed, export      | `docs/reference/cli.md`, `docs/guide/database.md`                                         |
-| Auth login/logout/whoami                  | `docs/reference/cli.md`                                                                   |
-| Overview / introduction                   | `docs/guide/index.md`                                                                     |
-| API surface details                       | `docs/reference/api.md`                                                                   |
-| Meta framework integration                | `docs/integrations/frameworks/*.md`                                                       |
-| Coding agent setup                        | `docs/integrations/agents.md`                                                             |
-| Node.js / Bun / Deno targets              | `docs/integrations/nodejs-bun-deno.md`                                                    |
-| ORMs and external databases               | `docs/integrations/orms-and-external-dbs.md`                                              |
-| Project structure and conventions         | `docs/reference/structure.md`                                                             |
-| Resource/binding inference                | `docs/reference/resource-inference.md`                                                    |
+| User intent                                | Docs file(s)                                                                              |
+| ------------------------------------------ | ----------------------------------------------------------------------------------------- |
+| CLI command syntax, flags, env vars        | `docs/reference/cli.md`                                                                   |
+| Initial setup, onboarding, first app       | `docs/guide/quickstart.md`, `docs/reference/cli.md`                                       |
+| App type detection and mode behavior       | `docs/guide/app-types.md`, `docs/reference/config.md`                                     |
+| Server/API routing and middleware          | `docs/guide/server-routing.md`, `docs/integrations/hono.md`                               |
+| Pages mode, loader/action, forms, layouts  | `docs/guide/pages-routing/*.md`, `docs/guide/type-safety.md`                              |
+| Database and migrations                    | `docs/guide/database.md`, `docs/guide/type-safety.md`                                     |
+| Typed fetch and end-to-end typing          | `docs/guide/typed-fetch.md`, `docs/guide/type-safety.md`                                  |
+| Authentication                             | `docs/guide/auth.md`, `docs/guide/env-vars.md`                                            |
+| Cloudflare runtime bindings and config     | `docs/integrations/cloudflare.md`, `docs/reference/config.md`, `docs/guide/env-vars.md`   |
+| AI inference (Workers AI, providers)       | `docs/guide/ai.md`                                                                        |
+| KV / storage / queues / cron jobs          | `docs/guide/kv.md`, `docs/guide/storage.md`, `docs/guide/queues.md`, `docs/guide/jobs.md` |
+| SSR and caching                            | `docs/guide/ssr.md`, `docs/guide/edge/*.md`                                               |
+| Rewrites, redirects, fallbacks             | `docs/guide/edge/rewrites.md`, `docs/guide/edge/redirects.md`, `docs/reference/config.md` |
+| Static site generation                     | `docs/guide/ssg.md`                                                                       |
+| Deployment and CI                          | `docs/guide/deployment.md`, `docs/reference/cli.md`                                       |
+| Self-host deploy to own Cloudflare account | `docs/integrations/cloudflare.md`, `docs/reference/cli.md`                                |
+| Project status, deployment history         | `docs/reference/cli.md`                                                                   |
+| Cache purging                              | `docs/reference/cli.md`                                                                   |
+| Project logs, runtime errors               | `docs/reference/cli.md`                                                                   |
+| Secrets management (put/sync/delete)       | `docs/reference/cli.md`, `docs/guide/env-vars.md`                                         |
+| Typed env vars (`defineEnv`, `env.ts`)     | `docs/guide/env-vars.md`                                                                  |
+| Custom domain setup                        | `docs/reference/cli.md`                                                                   |
+| Database status, reset, seed, export       | `docs/reference/cli.md`, `docs/guide/database.md`                                         |
+| Auth login/logout/whoami                   | `docs/reference/cli.md`                                                                   |
+| Overview / introduction                    | `docs/guide/index.md`                                                                     |
+| API surface details                        | `docs/reference/api.md`                                                                   |
+| Meta framework integration                 | `docs/integrations/frameworks/*.md`                                                       |
+| Coding agent setup                         | `docs/integrations/agents.md`                                                             |
+| Node.js / Bun / Deno targets               | `docs/integrations/nodejs-bun-deno.md`                                                    |
+| ORMs and external databases                | `docs/integrations/orms-and-external-dbs.md`                                              |
+| Project structure and conventions          | `docs/reference/structure.md`                                                             |
+| Resource/binding inference                 | `docs/reference/resource-inference.md`                                                    |
 
 ## Working Rules
 

package/skills/void/docs/node_modules/void/test/e2e/README.md

@@ -0,0 +1,85 @@
+# `packages/void/test/e2e`
+
+Gated live-account end-to-end tests. These run REAL Cloudflare operations against a REAL account, so
+they **skip unless credentials are present**. Locally that means exporting the env vars below; in CI
+they run on **pushes to `main`** (see [In CI](#in-ci)).
+
+## `cloudflare-deploy-live.test.ts`
+
+Deploys `playground/spa` (D1 + KV + cron) to the target account via `void deploy --backend cloudflare`,
+verifies the live worker answers HTTP 200, then deletes the worker and every resource it created.
+
+It does **not** drive `--provision`: that path fails closed in non-interactive shells by design (a
+spawned CLI has no TTY, and CI cannot commit back the ids a create would mint). So the test plays the
+provisioner's role itself — it creates the id-bearing D1 + KV directly with `wrangler … create`,
+writes their real ids into the app's root config exactly as `--provision` would, then runs the
+CI-safe `void deploy --backend cloudflare` (no `--provision`). That exercises the real
+build → tamper-guard → remote-migrations → `wrangler deploy` pipeline end to end.
+
+### Prerequisites
+
+The suite is skipped unless BOTH env vars are set:
+
+| Env var                  | Purpose                                                                    |
+| ------------------------ | -------------------------------------------------------------------------- |
+| `VOID_E2E_CF_TOKEN`      | Cloudflare API token that can create + delete Workers Scripts, D1, and KV. |
+| `VOID_E2E_CF_ACCOUNT_ID` | Cloudflare account id to deploy into.                                      |
+
+The token needs, on that account, **Workers Scripts: Edit**, **D1: Edit**, and **Workers KV Storage:
+Edit** (Edit implies read, covering the ownership/teardown list calls). Cron triggers ride along with
+the worker deploy — no extra permission.
+
+The account must also have a **workers.dev subdomain** already registered (with its wildcard TLS cert
+provisioned). Without one, `wrangler deploy` uploads the worker but cannot publish a public URL, and
+the HTTP-200 assertion has nothing to hit. Opening the Workers & Pages dashboard once registers a
+subdomain automatically; a freshly-registered subdomain takes a few minutes for its cert to go live,
+during which the first run may see a TLS handshake failure — rerun once the cert is ready.
+
+With no env vars the suite SKIPS cleanly (0 run, N skipped).
+
+### Running it
+
+```sh
+# Ensure the CLI is built first (dist/cli/cli.mjs):
+vp run build:core
+
+VOID_E2E_CF_TOKEN=... VOID_E2E_CF_ACCOUNT_ID=... vp test run packages/void/test/e2e
+```
+
+### In CI
+
+`VOID_E2E_CF_TOKEN` and `VOID_E2E_CF_ACCOUNT_ID` are **environment secrets** on the `cloudflare-e2e`
+GitHub Environment (not repo secrets), and a dedicated `live-e2e` job in `.github/workflows/ci.yml`
+consumes them — the main `test` job carries no creds at all. Two layers keep the account token off
+untrusted code:
+
+- The `live-e2e` job runs only on a direct push to `main` (`github.event_name == 'push' && github.ref
+== 'refs/heads/main'`), so `pull_request` runs, tag pushes, and `workflow_call` (release) skip it.
+- The `cloudflare-e2e` environment's deployment branch policy allows `main` **only**, enforced by
+  GitHub server-side on the run's ref. A `pull_request` run's ref is `refs/pull/<n>/merge`, so it can
+  never reach the secret **even if a PR edits this workflow** — the expression-level gate alone would
+  be bypassable that way; the environment ref-check is the real boundary.
+
+So the credentialed live deploy runs on every merge to `main`; everywhere else the creds are empty and
+the suite SKIPS (the `test` job still imports the file and skips it). The `live-e2e` job itself is
+fail-closed — a preflight step errors if either credential is empty (a missing, deleted, or
+not-yet-rotated secret), so a misconfigured gate is loud instead of a silent green skip. Each
+`live-e2e` run also gets `VOID_E2E_RUN_ID = <run-id>-<attempt>` for the unique per-run resource names
+below.
+
+### Resource naming & cleanup
+
+Each run derives a UNIQUE resource name — `void-e2e-cf-deploy-<suffix>` — so overlapping runs never
+collide on remote resources. The suffix is `VOID_E2E_RUN_ID` (CI: `<run-id>-<attempt>`) or, locally, a
+timestamp + random. Derived names mirror the provisioner: `<name>-db` (D1), `<name>-kv` (KV). The
+shared `void-e2e-cf-deploy-` prefix keeps every resource greppable, so an orphan from a hard-killed run
+is easy to find and `wrangler delete`. A pre-run ownership gate refuses to start if the run's names
+already exist (failing closed on any lookup it cannot confirm), so the test never adopts or deletes a
+resource it does not own. Teardown runs even when the deploy or an assertion fails.
+
+> **Local concurrency:** unique names isolate _remote_ resources, but a run also snapshots and
+> overwrites the shared `playground/spa/wrangler.jsonc` and builds in place. Do **not** run two live
+> e2e invocations against the same checkout at once — they would race that file. CI is unaffected (each
+> runner is an isolated checkout, and only the single `main`-push `live-e2e` job deploys). The deploy
+> test also asserts the returned host's worker label equals this run's `WORKER_NAME`, so a clobbered
+> overlay fails loudly instead of validating another run's worker.