void 0.10.2 → 0.10.3

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

@@ -0,0 +1,135 @@
+# markdown-it-footnote
+
+[![CI](https://github.com/markdown-it/markdown-it-footnote/actions/workflows/ci.yml/badge.svg)](https://github.com/markdown-it/markdown-it-footnote/actions/workflows/ci.yml)
+[![NPM version](https://img.shields.io/npm/v/markdown-it-footnote.svg?style=flat)](https://www.npmjs.org/package/markdown-it-footnote)
+[![Coverage Status](https://img.shields.io/coveralls/markdown-it/markdown-it-footnote/master.svg?style=flat)](https://coveralls.io/r/markdown-it/markdown-it-footnote?branch=master)
+
+> Footnotes plugin for [markdown-it](https://github.com/markdown-it/markdown-it) markdown parser.
+
+__v2.+ requires `markdown-it` v5.+, see changelog.__
+
+Markup is based on [pandoc](http://johnmacfarlane.net/pandoc/README.html#footnotes) definition.
+
+__Normal footnote__:
+
+```
+Here is a footnote reference,[^1] and another.[^longnote]
+
+[^1]: Here is the footnote.
+
+[^longnote]: Here's one with multiple blocks.
+
+    Subsequent paragraphs are indented to show that they
+belong to the previous footnote.
+```
+
+html:
+
+```html
+<p>Here is a footnote reference,<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup> and another.<sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup></p>
+<p>This paragraph won’t be part of the note, because it
+isn’t indented.</p>
+<hr class="footnotes-sep">
+<section class="footnotes">
+<ol class="footnotes-list">
+<li id="fn1"  class="footnote-item"><p>Here is the footnote. <a href="#fnref1" class="footnote-backref">↩</a></p>
+</li>
+<li id="fn2"  class="footnote-item"><p>Here’s one with multiple blocks.</p>
+<p>Subsequent paragraphs are indented to show that they
+belong to the previous footnote. <a href="#fnref2" class="footnote-backref">↩</a></p>
+</li>
+</ol>
+</section>
+```
+
+__Inline footnote__:
+
+```
+Here is an inline note.^[Inlines notes are easier to write, since
+you don't have to pick an identifier and move down to type the
+note.]
+```
+
+html:
+
+```html
+<p>Here is an inline note.<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></p>
+<hr class="footnotes-sep">
+<section class="footnotes">
+<ol class="footnotes-list">
+<li id="fn1"  class="footnote-item"><p>Inlines notes are easier to write, since
+you don’t have to pick an identifier and move down to type the
+note. <a href="#fnref1" class="footnote-backref">↩</a></p>
+</li>
+</ol>
+</section>
+```
+
+
+## Install
+
+node.js, browser:
+
+```bash
+npm install markdown-it-footnote --save
+bower install markdown-it-footnote --save
+```
+
+## Use
+
+```js
+var md = require('markdown-it')()
+            .use(require('markdown-it-footnote'));
+
+md.render(/*...*/) // See examples above
+```
+
+_Differences in browser._ If you load script directly into the page, without
+package system, module will add itself globally as `window.markdownitFootnote`.
+
+
+### Customize
+
+If you want to customize the output, you'll need to replace the template
+functions. To see which templates exist and their default implementations,
+look in [`index.js`](index.js). The API of these template functions is out of
+scope for this plugin's documentation; you can read more about it [in the
+markdown-it
+documentation](https://github.com/markdown-it/markdown-it/blob/master/docs/architecture.md#renderer).
+
+To demonstrate with an example, here is how you might replace the `<hr>` that
+this plugin emits by default with an `<h4>` emitted by your own template
+function override:
+
+```js
+const md = require('markdown-it')().use(require('markdown-it-footnote'));
+
+md.renderer.rules.footnote_block_open = () => (
+  '<h4 class="mt-3">Footnotes</h4>\n' +
+  '<section class="footnotes">\n' +
+  '<ol class="footnotes-list">\n'
+);
+```
+
+Here's another example that customizes footnotes for epub books:
+
+```js
+const backrefLabel = 'back to text';
+
+const epubRules = {
+  footnote_ref: ['<a', '<a epub:type="noteref"'],
+  footnote_open: ['<li', '<li epub:type="footnote"'],
+  footnote_anchor: ['<a', `<a aria-label="${backrefLabel}"`],
+}
+
+Object.keys(epubRules).map(rule => {
+  let defaultRender = md.renderer.rules[rule];
+  md.renderer.rules[rule] = (tokens, idx, options, env, self) => {
+    return defaultRender(tokens, idx, options, env, self).replace(...epubRules[rule]);
+  }
+})
+```
+
+## License
+
+[MIT](https://github.com/markdown-it/markdown-it-footnote/blob/master/LICENSE)

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

@@ -35,6 +35,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 purge-cache`        | Purge all cached pages                                              |
+| `void build logs`                 | Stream, tail, or download build logs                                |
 | `void mcp`                        | Start the Void MCP server                                           |
 | `void init`                       | Setup wizard for new or existing projects                           |
 
@@ -606,13 +607,16 @@ Connect a GitHub repository to a Void project for automatic deploys. On every pu
 
 **Options**
 
-| Flag                  | Description                                                                     |
-| --------------------- | ------------------------------------------------------------------------------- |
-| `--project <name>`    | Project name (alias for the positional argument)                                |
-| `--installation <id>` | GitHub App installation ID (required when you have multiple installations)      |
-| `--repo <owner/repo>` | Repository full name — required unless the installation grants exactly one repo |
-| `--branch <name>`     | Branch to deploy from — **required in non-interactive mode**                    |
-| `--executor <type>`   | Build executor: `container` (default) or `github_actions`                       |
+| Flag                  | Description                                                                       |
+| --------------------- | --------------------------------------------------------------------------------- |
+| `--project <name>`    | Project name (alias for the positional argument)                                  |
+| `--installation <id>` | GitHub App installation ID (required when you have multiple installations)        |
+| `--repo <owner/repo>` | Repository full name — required unless the installation grants exactly one repo   |
+| `--branch <name>`     | Branch to deploy from — **required in non-interactive mode**                      |
+| `--executor <type>`   | Build executor: `container` (default) or `github_actions`                         |
+| `--workflow <path>`   | Authorized deploy workflow file — defaults to `.github/workflows/void-deploy.yml` |
+
+The `--workflow` path is the workflow file the GitHub OIDC exchange authorizes to mint this project's deploy token. It defaults to the scaffolded `.github/workflows/void-deploy.yml`; set it only if your deploy step lives in a different workflow file (it must be under `.github/workflows/` and end in `.yml`/`.yaml`). Because the exchange is secretless, **only this one workflow** can mint a deploy token — any other workflow in the repo (including an unsafe `pull_request_target`) is rejected. Pointing it at a broad, multi-purpose workflow widens that trust, so prefer a dedicated file.
 
 **Non-interactive use (CI)**
 
@@ -633,17 +637,18 @@ void github connect my-app \
 void github update [project] [options]
 ```
 
-Update an existing connection's deploy **branch** and/or **build executor**. Use this to change settings on a project that is already connected — for example, flipping the executor from `container` to `github_actions` for a monorepo whose Void app lives in a subdirectory, or moving the deploy branch. The project must already be connected (run `void github connect` first); the repository and installation are not changed.
+Update an existing connection's deploy **branch**, **build executor**, and/or authorized **workflow file**. Use this to change settings on a project that is already connected — for example, flipping the executor from `container` to `github_actions` for a monorepo whose Void app lives in a subdirectory, moving the deploy branch, or pointing the OIDC trust at a different workflow file. The project must already be connected (run `void github connect` first); the repository and installation are not changed.
 
 **Options**
 
-| Flag                | Description                                         |
-| ------------------- | --------------------------------------------------- |
-| `--project <name>`  | Project name (alias for the positional argument)    |
-| `--branch <name>`   | New branch to deploy from                           |
-| `--executor <type>` | New build executor: `container` or `github_actions` |
+| Flag                | Description                                                      |
+| ------------------- | ---------------------------------------------------------------- |
+| `--project <name>`  | Project name (alias for the positional argument)                 |
+| `--branch <name>`   | New branch to deploy from                                        |
+| `--executor <type>` | New build executor: `container` or `github_actions`              |
+| `--workflow <path>` | New authorized deploy workflow file (under `.github/workflows/`) |
 
-Interactively (TTY), `void github update` shows the current branch and executor and prompts for new values, defaulting each to the current setting. When stdin is not a TTY, it never prompts: pass at least one of `--branch` / `--executor`, or it fails closed. If nothing actually changes, the command reports "no changes" and does not call the API.
+Interactively (TTY), `void github update` shows the current branch and executor and prompts for new values, defaulting each to the current setting. `--workflow` is flag-only — it is never prompted for; pass it explicitly to change the authorized workflow file. When stdin is not a TTY, it never prompts: pass at least one of `--branch` / `--executor` / `--workflow`, or it fails closed. If nothing actually changes, the command reports "no changes" and does not call the API.
 
 ```
 void github update my-app --executor github_actions
@@ -651,6 +656,40 @@ void github update my-app --executor github_actions
 
 **Project resolution** follows the same order as deploy: positional / `--project`, `VOID_PROJECT`, linked project (`.void/project.json`).
 
+## Build
+
+Inspect Deploy-on-GitHub builds.
+
+### `void build logs`
+
+```
+void build logs [build] [--follow] [--output <file>] [--project <slug>]
+```
+
+Stream, tail, or download the build logs for a **container** build. With no
+`[build]` argument, targets the project's most recent build.
+
+| Flag                     | Purpose                                                           | Default |
+| ------------------------ | ----------------------------------------------------------------- | ------- |
+| `--follow`, `-f`         | Live-tail: poll until the build reaches a terminal status.        | off     |
+| `--output <file>`, `-o`  | Write logs to a file instead of stdout (appends while following). | stdout  |
+| `--project <slug>`, `-p` | Target project.                                                   | linked  |
+
+**Project resolution** follows the same order as deploy: positional / `--project`,
+`VOID_PROJECT`, linked project (`.void/project.json`).
+
+Builds run on **GitHub Actions** keep their logs on GitHub — the command prints
+the Actions run URL instead of streaming. Only the last 10,000 log lines of a
+container build are retained.
+
+Examples:
+
+```
+void build logs                     # print the latest build's logs
+void build logs -f                  # follow the latest build until it finishes
+void build logs bld_123 -o build.log  # download a specific build's logs
+```
+
 ## Custom Domains
 
 ### `void domain add`