@overcrow/mcp 0.1.3 → 0.1.4

package/README.md

@@ -6,7 +6,7 @@ VS Code or Codex, and the assistant can create a widget, check it, test it,
 audit its security and lightness, package it and prepare its submission.
 
 You need Node.js 22.18 or later, nothing else: the server installs the
-OverCrow creator tools it needs by itself.
+PlayerVox OverCrow creator tools it needs by itself.
 
 ```sh
 claude mcp add overcrow -- npx -y @overcrow/mcp
@@ -45,7 +45,7 @@ use; `--tools-zip <file>` gives a local copy of the creator tools ZIP.
 | `audit` | Security and lightness, scored out of 100, with fixes and examples |
 | `explain_permission`, `explain_error` | A permission or a code, in plain words |
 | `search_docs`, `read_doc`, `read_example` | The documentation and the reference widgets, offline |
-| `prepare_submission` | Everything the OverCrow creator space asks for, checked; the ZIP of the sources in `dist/`; the texts to draft with you |
+| `prepare_submission` | Everything the PlayerVox OverCrow creator space asks for, checked; the ZIP of the sources in `dist/`; the texts to draft with you |
 
 Resources: the documentation (`overcrow://docs/{en,fr}/…`), the manifest
 reference, the limits, the templates and the reference widgets. Prompts:
@@ -56,10 +56,10 @@ reference, the limits, the templates and the reference widgets. Prompts:
 - The server works only in your project folders, through their real paths:
   no system folder, no whole home folder, no link that leads out, no
   hidden folder.
-- It runs the OverCrow widget CLI and npm, without a shell, with a minimal
-  environment (no token is passed on), time limits and bounded output. It
-  never runs a command chosen by the assistant.
-- It downloads only the creator tools ZIP of the OverCrow release this
+- It runs the PlayerVox OverCrow widget CLI and npm, without a shell, with a
+  minimal environment (no token is passed on), time limits and bounded output.
+  It never runs a command chosen by the assistant.
+- It downloads only the creator tools ZIP of the PlayerVox OverCrow release this
   version pins, from GitHub, and checks its size and SHA-256 and every file
   in it before use. npm installs only `@overcrow/sdk` and TypeScript, with
   install scripts disabled, and their integrity is checked against the
@@ -71,7 +71,7 @@ reference, the limits, the templates and the reference widgets. Prompts:
   instructions found in it.
 - No telemetry. Logs go to standard error, without your paths.
 - It never sends, signs or publishes anything: you send the sources ZIP
-  in the OverCrow creator space, at creators.playervox.com.
+  in the PlayerVox OverCrow creator space, at creators.playervox.com.
 
 ## Platforms
 

package/dist/bootstrap/pin.json

@@ -1,107 +1,107 @@
 {
-  "release": "0.7.1-beta.1",
+  "release": "0.7.2-beta.1",
   "tools": {
     "linux-x86_64": {
-      "name": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64.zip",
-      "size": 15995038,
-      "sha256": "e5691386592857aa624359f91baaf6e8162f403994d6d7445d586992adc75cfe",
+      "name": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64.zip",
+      "size": 15992509,
+      "sha256": "8ef74f86d6f754036de4b20609196a7933c47522514446b2579b9a92a83425dd",
       "files": [
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/README.txt",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/README.txt",
           "size": 1636,
-          "sha256": "5488b72ea5fa3b5bffd817807b466a320b08c8da2e1d4630cb3ab044a2c4cd83"
+          "sha256": "3487492fc93226a72d474e391bf8e714147148aef182239c38b67584c908abf8"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/SHA256SUMS",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/SHA256SUMS",
           "size": 797,
-          "sha256": "a1762f910bd5dc68312d59d66ba9deca4d3307884af5fb93892af6e73696f6cf"
+          "sha256": "e1cb2fb41b01b52d20a46c84e497aa7af35a680dda21fc2e4be793e6762fb896"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/cli.json",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/cli.json",
           "size": 1014,
-          "sha256": "6975d04ef3508151c4e539ba27396b460e4293460b591b405a422528885e9ac3"
+          "sha256": "596f02e649d58803f4580b0e62f67be4737bb54bb670fd1cbd08989007161406"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.4-LICENSE.txt",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.5-LICENSE.txt",
           "size": 1071,
           "sha256": "c159eef41245fe20d4cd29fc33a0e88a85f47b53ac321f266abfb7b707aee8c3"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.4-THIRD-PARTY-NOTICES.md",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.5-THIRD-PARTY-NOTICES.md",
           "size": 212099,
           "sha256": "8c679481b61f9fb4c8352bd4d1c3bcfc23acf4d51b8252140ed214b1f5b756c4"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.4-linux-x86_64",
-          "size": 9511032,
-          "sha256": "28557b787a18143fb5ebfc6c117e068290da5ad28b065d1f9aebccb993dd8f1e"
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/overcrow-widget-1.0.0-beta.5-linux-x86_64",
+          "size": 9508600,
+          "sha256": "e899ab38f6c72e41e15a81de469fee0093394297bd0288338627e3b39e6348e0"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/overcrow-widget-headless-0.7.1-beta.1-LICENSE.md",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/overcrow-widget-headless-0.7.2-beta.1-LICENSE.md",
           "size": 217457,
-          "sha256": "8f4895218bf254acc8f65a643d65ceceafdfa3b9611ee4807307b7d8830d55f4"
+          "sha256": "a20df95a937c0c4e794edd027042bbe3fb0427d0e7d16fe2ed8f12d96bf23b03"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/overcrow-widget-headless-0.7.1-beta.1-linux-x86_64",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/overcrow-widget-headless-0.7.2-beta.1-linux-x86_64",
           "size": 24959192,
-          "sha256": "2616c578ca11b685dad44fb045f402a443445909153a1da9c1b5802a12de0b7a"
+          "sha256": "ad3553c91fbbc2484b7534d61b77e54731c3413588b4b1cfa85e17da0d6d6c64"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-linux-x86_64/runtimes.json",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-linux-x86_64/runtimes.json",
           "size": 774,
-          "sha256": "f099e933965f6396ffbb63fbb92b6d17bcd187ab1c1869a989cb5923443e7f15"
+          "sha256": "c354b0e4bdf95befd0b428014212729b21c621b76ba8addb58e0944c87304922"
         }
       ]
     },
     "windows-x86_64": {
-      "name": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64.zip",
-      "size": 15910251,
-      "sha256": "40dbe6e6d6d411aab510ff120e99eb381174258b856390ecad0d5626e0ca890c",
+      "name": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64.zip",
+      "size": 15909302,
+      "sha256": "e8b0efb252e4f589f4126e4194a194ba4b16a8cc9fee5790a13fa5a0b964b223",
       "files": [
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/README.txt",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/README.txt",
           "size": 1457,
-          "sha256": "f4d37f0d43473d497b1a8240a6aad4c71a37055a171addba8422d81fc19b2975"
+          "sha256": "f12ab0895d4d155de4af20abdd9e8cd9c3d279bea375702e41d47a29ef062b28"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/SHA256SUMS",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/SHA256SUMS",
           "size": 809,
-          "sha256": "01e76cd9e09a3f0f43395acc94a6285beb0b17ce6c08f706eef3266499901cc9"
+          "sha256": "bdb200171439600794a84055b8c3f68674554bffe6f3872547c1a3772c7e83b5"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/cli.json",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/cli.json",
           "size": 1014,
-          "sha256": "6975d04ef3508151c4e539ba27396b460e4293460b591b405a422528885e9ac3"
+          "sha256": "596f02e649d58803f4580b0e62f67be4737bb54bb670fd1cbd08989007161406"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.4-LICENSE.txt",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.5-LICENSE.txt",
           "size": 1071,
           "sha256": "c159eef41245fe20d4cd29fc33a0e88a85f47b53ac321f266abfb7b707aee8c3"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.4-THIRD-PARTY-NOTICES.md",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.5-THIRD-PARTY-NOTICES.md",
           "size": 212099,
           "sha256": "8c679481b61f9fb4c8352bd4d1c3bcfc23acf4d51b8252140ed214b1f5b756c4"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.4-windows-x86_64.exe",
-          "size": 9513984,
-          "sha256": "a6b046bfe11938f07e37225f2f993d9656fe92bdb403cd695ce23dfa88dd370a"
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/overcrow-widget-1.0.0-beta.5-windows-x86_64.exe",
+          "size": 9528320,
+          "sha256": "4e26c45c74e1e6b291892e097236b3f64da0d9d881cb8eba6d9561e3fc3fc831"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/overcrow-widget-headless-0.7.1-beta.1-LICENSE.md",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/overcrow-widget-headless-0.7.2-beta.1-LICENSE.md",
           "size": 217457,
-          "sha256": "8f4895218bf254acc8f65a643d65ceceafdfa3b9611ee4807307b7d8830d55f4"
+          "sha256": "a20df95a937c0c4e794edd027042bbe3fb0427d0e7d16fe2ed8f12d96bf23b03"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/overcrow-widget-headless-0.7.1-beta.1-windows-x86_64.exe",
-          "size": 25644544,
-          "sha256": "66019a1ff9bdcd7074f27facba56b684d870642497388a265bb05eb9f80946f4"
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/overcrow-widget-headless-0.7.2-beta.1-windows-x86_64.exe",
+          "size": 25638912,
+          "sha256": "ca4dbbe2a4acd757db2345e699c35b8bf35953b932c65f1e9273d3248b4e092d"
         },
         {
-          "path": "overcrow-creator-tools-0.7.1-beta.1-windows-x86_64/runtimes.json",
+          "path": "overcrow-creator-tools-0.7.2-beta.1-windows-x86_64/runtimes.json",
           "size": 774,
-          "sha256": "f099e933965f6396ffbb63fbb92b6d17bcd187ab1c1869a989cb5923443e7f15"
+          "sha256": "c354b0e4bdf95befd0b428014212729b21c621b76ba8addb58e0944c87304922"
         }
       ]
     }

package/dist/content/docs/en/cli.md

@@ -23,7 +23,7 @@ overcrow-widget test
 | [`check`](#check) | Validates a project without writing anything. |
 | [`package`](#package) | Checks, then writes the `.ocpkg` package. |
 | [`inspect`](#inspect) | Shows what a package holds and asks for. |
-| [`dev`](#dev) | Runs the widget in OverCrow and reloads it when you save. |
+| [`dev`](#dev) | Runs the widget in PlayerVox OverCrow and reloads it when you save. |
 | [`test`](#test) | Plays the project's test scenarios and compares their images. |
 | [`doctor`](#doctor) | Says what your setup has and lacks. |
 | [`admit`](#admit) | Runs the admission of the creator space on your sources, a folder or a ZIP. |
@@ -37,7 +37,7 @@ and [exit status](#exit-status) are stable for scripts.
 
 ## Installing
 
-Each [OverCrow release](https://github.com/Valhallab/playervox-overcrow-releases/releases)
+Each [PlayerVox OverCrow release](https://github.com/Valhallab/playervox-overcrow-releases/releases)
 carries the creator tools in one ZIP per platform: the tool with its
 license and third-party notices, OverCrow's headless runtime that
 [`test`](#test) uses, a `README.txt` and a `SHA256SUMS` of every file.
@@ -122,8 +122,8 @@ empty: `init` never overwrites a file.
 | `chart` | A live chart updated by a timer. |
 
 Pass `--id` with your widget's ID: `<handle>.<name>`, your publisher handle
-in the OverCrow creator space and a name (`nova.lol-timers`), or a reverse
-domain you verified and a name (`gg.nova.lol-timers`); see
+in the PlayerVox OverCrow creator space and a name (`nova.lol-timers`), or a
+reverse domain you verified and a name (`gg.nova.lol-timers`); see
 [the manifest](manifest.md#identity-and-version). Without `--id`, the ID is
 `yourhandle.<dir>`: replace `yourhandle` before you submit, as `admit`
 refuses it. `com.playervox.*` is reserved. Every template
@@ -141,17 +141,17 @@ Runs every check, in this order, and writes nothing:
 
 1. **Project files**: the required files are there and within their size
    bounds, one logic module, both locale files or neither.
-2. **Manifest**: OverCrow's own manifest validator.
+2. **Manifest**: PlayerVox OverCrow's own manifest validator.
 3. **View**: `view.ocml` is compiled and the result validated; static
    images must exist in `assets/`.
-4. **Style**: `style.ocss` is parsed with OverCrow's parser.
+4. **Style**: `style.ocss` is parsed with PlayerVox OverCrow's parser.
 5. **Locales**: objects of strings with valid keys, the same keys in both
    files. A `t("key")` of the view whose key has no message is a warning.
 6. **Logic**: the [lint](logic.md#what-the-logic-cannot-use), and the
    exports the view calls.
 7. **Types**: the project's `tsc --noEmit -p tsconfig.json`.
 8. **Package**: `logic.js` is built, the package is written in memory and
-   read back exactly as OverCrow will read it.
+   read back exactly as PlayerVox OverCrow will read it.
 
 Options: `--no-typecheck`, `--deny-warnings` (a warning fails the command),
 `--format json`.
@@ -180,14 +180,14 @@ holds is described in [the package](package.md).
 overcrow-widget inspect dist/nova.my-widget-0.1.0.ocpkg
 ```
 
-Validates a package as OverCrow does, then shows it as a reviewer sees it:
-the ID, version and names; the size and SHA-256 of the archive; the SDK
-version its `logic.js` contains; each permission in words (network routes
-with their parameter constraints and declared response bound, storage,
-clipboard, game events); each capability with its summary and whether it is
-sensitive or needs an account; the number of menu rows; and every file with
-its size and SHA-256. A package that OverCrow would refuse is reported
-instead, with the reason.
+Validates a package as PlayerVox OverCrow does, then shows it as a reviewer
+sees it: the ID, version and names; the size and SHA-256 of the archive; the
+SDK version its `logic.js` contains; each permission in words (network
+routes with their parameter constraints and declared response bound,
+storage, clipboard, game events); each capability with its summary and
+whether it is sensitive or needs an account; the number of menu rows; and
+every file with its size and SHA-256. A package that OverCrow would refuse
+is reported instead, with the reason.
 
 ## dev
 
@@ -195,8 +195,8 @@ instead, with the reason.
 overcrow-widget dev
 ```
 
-Runs the widget in the OverCrow overlay running on your machine, while you
-edit it:
+Runs the widget in the PlayerVox OverCrow overlay running on your machine,
+while you edit it:
 
 1. it connects to the overlay, which must have been started with
    development installs allowed;
@@ -215,7 +215,7 @@ edit it:
 Options: `--no-typecheck`, `--format json` (one JSON object per line).
 Exit status: 0 after Ctrl+C, 1 when the overlay ends the session, 2 when no
 overlay is reachable. [The development channel](dev-channel.md) says how to
-start OverCrow for it, and what each state and refusal means.
+start PlayerVox OverCrow for it, and what each state and refusal means.
 
 ## test
 
@@ -225,8 +225,8 @@ overcrow-widget test --scenario example
 overcrow-widget test --update
 ```
 
-Plays the scenarios of `tests/` in OverCrow's headless runtime and compares
-the images it renders with the references:
+Plays the scenarios of `tests/` in PlayerVox OverCrow's headless runtime and
+compares the images it renders with the references:
 
 1. it builds the package as `package` does;
 2. it reads every `tests/<name>.scenario.json` and checks it against the
@@ -268,7 +268,7 @@ overcrow-widget doctor
 | Code | Severity | Meaning |
 | --- | --- | --- |
 | `doctor.overcrow_missing` | warning | OverCrow is not installed. |
-| `doctor.development_off` | warning | No overlay allows development installs; the help gives the commands to restart OverCrow with them. |
+| `doctor.development_off` | warning | No overlay allows development installs; the help gives the commands to restart PlayerVox OverCrow with them. |
 | `doctor.channel_busy` | warning | The overlay already serves its maximum of `dev` sessions. |
 | `doctor.channel_io` | warning | The connection to the overlay failed. |
 | `doctor.channel_untrusted` | error | What answers is not this user's overlay. |
@@ -384,8 +384,8 @@ overcrow-widget submit --dry-run --submission submission.json
 overcrow-widget submit --submission submission.json
 ```
 
-Sends a version of your widget to the OverCrow creator space, from a
-terminal, a CI job or the OverCrow MCP server, then follows its checks. It
+Sends a version of your widget to the PlayerVox OverCrow creator space, from
+a terminal, a CI job or the OverCrow MCP server, then follows its checks. It
 never asks a question: what is missing is said, with a stable
 [exit status](#exit-status). It takes the widget folder (the current one
 without argument) or a ZIP of it.
@@ -499,8 +499,8 @@ an hour expires, and every submission counts in the daily limit.
 | `justifications` | For the reviewer, one `{permission, text}` per new or widened permission, by its [key](#permission-keys); 500 characters each. |
 | `reviewMessage` | A private message to the reviewer, 2,000 characters. |
 
-Every key is optional; any other key is refused. The OverCrow MCP server
-writes this file.
+Every key is optional; any other key is refused. The PlayerVox OverCrow MCP
+server writes this file.
 
 ### In a CI job
 
@@ -510,10 +510,11 @@ the key in the repository's secrets:
 
 <!-- source: docs/content/examples/weather/.github/workflows/submit.yml -->
 ```yaml
-# Sends the widget to the OverCrow creator space when a version tag is
-# pushed. The publish key is a secret of the repository, and the OverCrow
-# release whose creator tools to use is a variable of the repository.
-name: Submit to OverCrow
+# Sends the widget to the PlayerVox OverCrow creator space when a version
+# tag is pushed. The publish key is a secret of the repository, and the
+# OverCrow release whose creator tools to use is a variable of the
+# repository.
+name: Submit to PlayerVox OverCrow
 
 on:
   push:
@@ -538,7 +539,7 @@ jobs:
           (cd "$tools" && sha256sum --check --quiet SHA256SUMS)
           install -D -m 755 "$tools"/overcrow-widget-*-linux-x86_64 "$HOME/.local/bin/overcrow-widget"
           echo "$HOME/.local/bin" >> "$GITHUB_PATH"
-      - name: Submit to OverCrow
+      - name: Submit to PlayerVox OverCrow
         run: overcrow-widget submit --submission submission.json
         env:
           OVERCROW_PUBLISH_KEY: ${{ secrets.OVERCROW_PUBLISH_KEY }}
@@ -547,7 +548,7 @@ jobs:
 The job fails on any status but 0. `OVERCROW_API_URL` points `submit`
 and `status` to another API, for tests only: `https://`, or `http://` to
 `127.0.0.1`, `localhost` or `[::1]`, with a warning every time. Never set
-it in a real job; the OverCrow MCP server never sets it.
+it in a real job; the PlayerVox OverCrow MCP server never sets it.
 
 ## status
 

package/dist/content/docs/en/dev-channel.md

@@ -15,8 +15,8 @@ builds the widget, sends it and stays in the foreground until Ctrl+C.
 
 ## Turn it on
 
-The channel exists only while OverCrow runs with development installs
-allowed: started with the environment variable
+The channel exists only while PlayerVox OverCrow runs with development
+installs allowed: started with the environment variable
 `OVERCROW_WIDGET_DEVELOPMENT=1`. Without it, the overlay opens nothing.
 
 **Linux.** Set the variable for your session's services, then restart the
@@ -34,7 +34,7 @@ systemctl --user unset-environment OVERCROW_WIDGET_DEVELOPMENT
 systemctl --user restart overcrow-overlay.service
 ```
 
-**Windows.** Quit OverCrow from its tray icon, then start it from
+**Windows.** Quit PlayerVox OverCrow from its tray icon, then start it from
 PowerShell:
 
 ```text
@@ -126,5 +126,5 @@ before a session starts. Widgets cannot use it: their sandbox has no access
 to it.
 
 This is why the channel is off by default. With it on, any program you run
-can show an unverified widget in your overlay, for as long as OverCrow
-runs. Turn it off when you are done.
+can show an unverified widget in your overlay, for as long as
+PlayerVox OverCrow runs. Turn it off when you are done.

package/dist/content/docs/en/elements.md

@@ -19,7 +19,7 @@ them: expressions, `if`, `for`, components.
 ```
 
 Two `box` containers, two `text` elements bound to the state, and a `chart`
-with one `series`: OverCrow draws all of it, the chart included.
+with one `series`: PlayerVox OverCrow draws all of it, the chart included.
 
 ## How to read an element
 
@@ -435,10 +435,10 @@ Any other `key` is one printable character.
 
 ## Default sizes
 
-The elements that OverCrow draws take these sizes, in logical pixels at
-100 %, unless the style sets `width` or `height`. Any other element is
-sized by its content and by the style: a `canvas` has no size until the
-style gives it one.
+The elements that PlayerVox OverCrow draws take these sizes, in logical
+pixels at 100 %, unless the style sets `width` or `height`. Any other
+element is sized by its content and by the style: a `canvas` has no size
+until the style gives it one.
 
 <!-- generated:default-sizes -->
 | Element | When | Width | Height |

package/dist/content/docs/en/forms.md

@@ -8,9 +8,9 @@ intent** is how a widget lets the user write to their notes, publish a
 rating or send a chat message, without the text ever passing through the
 widget's code.
 
-Widgets receive input only in OverCrow's Interactive mode. In Passive mode
-a click goes through the widget to the game: hide or disable what cannot be
-used, as the built-ins do with `host.mode`.
+Widgets receive input only in PlayerVox OverCrow's Interactive mode. In
+Passive mode a click goes through the widget to the game: hide or disable
+what cannot be used, as the built-ins do with `host.mode`.
 
 ## Controls
 
@@ -58,9 +58,10 @@ slider, text for the others.
 
 ### Text fields
 
-OverCrow edits the text of a `field` or a `textarea` itself: the caret, the
-selection, copy and paste, and input methods for languages that compose
-characters. The logic receives a copy of the text in each `input` event.
+PlayerVox OverCrow edits the text of a `field` or a `textarea` itself: the
+caret, the selection, copy and paste, and input methods for languages that
+compose characters. The logic receives a copy of the text in each `input`
+event.
 
 <!-- source: widgets/warframe-market/view.ocml -->
 ```xml
@@ -91,9 +92,9 @@ Binding `value` replaces what the field holds: bind it to the state your
 the field is empty.
 
 A field also sends `keydown` when you ask for it, with the key and its
-modifiers, for shortcuts such as Escape to cancel. Keys that OverCrow
-reserves (Tab to move the focus, its own shortcuts, a composition in
-progress) are not delivered.
+modifiers, for shortcuts such as Escape to cancel. Keys that
+PlayerVox OverCrow reserves (Tab to move the focus, its own shortcuts, a
+composition in progress) are not delivered.
 
 ### The focus when an editor opens
 
@@ -107,7 +108,7 @@ the caret in the field, after its text, as a click in it would.
         <field class="title-field" name="title" autofocus placeholder={t("title-hint")} label={t("title-hint")} on:input={titleInput(editor.key, event.value)} on:keydown={keyed(editor.key, event.key, event.ctrl)}/>
 ```
 
-OverCrow gives that focus only when the element appears during a
+PlayerVox OverCrow gives that focus only when the element appears during a
 [user action](services.md#calls-that-need-a-user-action), in Interactive
 mode, in the widget the user acted on; when several such elements appear
 together, the first one of the view takes it. An element that appears when
@@ -186,22 +187,23 @@ form with an `intent` attribute sends them:
     </form>
 ```
 
-When the user submits such a form, **OverCrow reads the values of the
-form's own controls and sends them itself**. The widget's logic never
+When the user submits such a form, **PlayerVox OverCrow reads the values of
+the form's own controls and sends them itself**. The widget's logic never
 supplies the text, so a widget cannot write something the user did not
 type, and cannot submit without the user: the form goes only on a user
 action, in Interactive mode, with the capability granted.
 
 What this changes for the view and the logic:
 
-- **The controls belong to OverCrow.** The `field`, `textarea` and `slider`
-  controls of the form take no `value`: `overcrow-widget check` refuses it
-  (`view.bound_value`), and OverCrow stops a widget that sets one at run
-  time. Their `name` attribute says which field of the intent each one is.
-- **OverCrow fills them** where the intent says so: the note's title, body
-  and checklist, the user's published rating. A fill sends the control's
-  `input` event with the value, so the logic knows what is shown; that
-  event is not a user action.
+- **The controls belong to PlayerVox OverCrow.** The `field`, `textarea` and
+  `slider` controls of the form take no `value`: `overcrow-widget check`
+  refuses it (`view.bound_value`), and OverCrow stops a widget that sets one
+  at run time. Their `name` attribute says which field of the intent each
+  one is.
+- **PlayerVox OverCrow fills them** where the intent says so: the note's
+  title, body and checklist, the user's published rating. A fill sends the
+  control's `input` event with the value, so the logic knows what is shown;
+  that event is not a user action.
 - **The logic follows through `input` events**, to show a counter or to
   enable the button, and may disable the controls.
 - **The outcome arrives in the form's `submit` event**: `event.outcome` is
@@ -284,10 +286,10 @@ ID for `notes.save`, the ID of the message replied to for
 ### Several rows of one field
 
 The `notes.save` intent takes one `item` field per checklist row. The
-logic decides which rows the form has, with a `for`; OverCrow fills each
-row's field from the stored note and remembers which checklist entry it
-put there. A row that the logic removes or moves keeps its entry, and a
-row added since is a new entry.
+logic decides which rows the form has, with a `for`; PlayerVox OverCrow
+fills each row's field from the stored note and remembers which checklist
+entry it put there. A row that the logic removes or moves keeps its entry,
+and a row added since is a new entry.
 
 <!-- source: widgets/notes/view.ocml -->
 ```xml
@@ -308,11 +310,11 @@ Ctrl+Enter or the `submit` button saves.
 ## Confirmations
 
 Two services delete user data: `notes.delete` and `journal.delete`. They
-are ordinary calls that need a user action, and OverCrow then asks the
-user to confirm in a dialog that it draws itself, outside the widget. The
-call resolves when the user confirms and fails with `cancelled` when they
-decline. Do not draw your own "Are you sure?": OverCrow's is the one that
-counts.
+are ordinary calls that need a user action, and PlayerVox OverCrow then asks
+the user to confirm in a dialog that it draws itself, outside the widget.
+The call resolves when the user confirms and fails with `cancelled` when
+they decline. Do not draw your own "Are you sure?": OverCrow's is the one
+that counts.
 
 ## Checklist for a form
 
@@ -325,4 +327,4 @@ counts.
   sliders, and every named control is a field of the intent.
 - Test it with a scenario: `text` steps type into the focused field,
   `key` steps press Enter, and `expect.intents` checks exactly what
-  OverCrow sent. See [testing a widget](testing.md#steps).
+  PlayerVox OverCrow sent. See [testing a widget](testing.md#steps).

package/dist/content/docs/en/guide.md

@@ -5,8 +5,8 @@ submission: create a project, edit its view, style and logic, run it in
 OverCrow, test it, package it and submit it. Each step links to the page
 that covers it in full.
 
-To work with an AI assistant instead, add OverCrow's MCP server to it: see
-[MCP](mcp.md).
+To work with an AI assistant instead, add PlayerVox OverCrow's MCP server to
+it: see [MCP](mcp.md).
 
 ## 1. Install the tools
 
@@ -15,7 +15,7 @@ To work with an AI assistant instead, add OverCrow's MCP server to it: see
 - **Node.js 22 or later** and npm, so that `check` can type-check your
   logic with the project's own TypeScript and the SDK from npm. The CLI checks and packages without it, but
   warns that types were not checked.
-- **OverCrow**, to run the widget while you write it.
+- **PlayerVox OverCrow**, to run the widget while you write it.
 
 `overcrow-widget doctor` tells what your setup has and lacks.
 
@@ -141,8 +141,8 @@ Provide both files or neither, with the same keys. See
 overcrow-widget check
 ```
 
-`check` runs the same validators as OverCrow: manifest, view, style,
-locales, a lint of the logic against what the VM runs, the project's
+`check` runs the same validators as PlayerVox OverCrow: manifest, view,
+style, locales, a lint of the logic against what the VM runs, the project's
 TypeScript, and a package built in memory and read back. Each problem has a
 stable code, a position and a help line; see
 [diagnostics](cli.md#diagnostics).
@@ -153,13 +153,13 @@ stable code, a position and a help line; see
 overcrow-widget dev
 ```
 
-`dev` sends the widget to the OverCrow overlay running on your machine and
-reloads it each time you save. OverCrow offers this only when it was
-started with development installs allowed (`OVERCROW_WIDGET_DEVELOPMENT=1`;
-`overcrow-widget doctor` prints the commands). The widget shows an
-**Unverified · development package** marker; its declared permissions are
-granted for the session only, and nothing is stored. `log.info(…)` from your
-logic prints in the terminal. See
+`dev` sends the widget to the PlayerVox OverCrow overlay running on your
+machine and reloads it each time you save. OverCrow offers this only when it
+was started with development installs allowed
+(`OVERCROW_WIDGET_DEVELOPMENT=1`; `overcrow-widget doctor` prints the
+commands). The widget shows an **Unverified · development package** marker;
+its declared permissions are granted for the session only, and nothing is
+stored. `log.info(…)` from your logic prints in the terminal. See
 [the development channel](dev-channel.md).
 
 ## 9. Test it
@@ -168,9 +168,9 @@ Two kinds of tests, both described in [testing a widget](testing.md):
 
 - unit tests of the logic with `@overcrow/sdk/testing`, which runs your
   module with virtual time and simulated services;
-- scenarios played by `overcrow-widget test` in OverCrow's headless
-  runtime: the real VM and renderer, services answered by fixtures, and
-  images compared with references.
+- scenarios played by `overcrow-widget test` in PlayerVox OverCrow's
+  headless runtime: the real VM and renderer, services answered by fixtures,
+  and images compared with references.
 
 <!-- source: templates/counter/tests/example.scenario.json -->
 ```json
@@ -241,7 +241,7 @@ locally stays unverified; users get widgets from the signed catalog. See
 
 Add a `listing.json` with the marketplace text and run the admission
 yourself. Widgets are no longer proposed by pull request: you will send
-yours from the OverCrow creator space when it opens.
+yours from the PlayerVox OverCrow creator space when it opens.
 
 ```sh
 overcrow-widget admit