@overcrow/mcp 0.1.3 → 0.1.4

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

@@ -23,15 +23,15 @@ Each widget runs behind two barriers.
    capabilities, a Job Object per widget, and process mitigations that
    forbid dynamic code and the window system.
 
-OverCrow draws everything itself: the VM sends a description of the view,
-never pixels, and never runs code in OverCrow's process. Hover, focus,
-pressed states and transitions are resolved by OverCrow, so a widget does
-not observe pointer motion it has not asked for through an event.
+PlayerVox OverCrow draws everything itself: the VM sends a description of
+the view, never pixels, and never runs code in OverCrow's process. Hover,
+focus, pressed states and transitions are resolved by OverCrow, so a widget
+does not observe pointer motion it has not asked for through an event.
 
-Going over a budget ends only that widget. OverCrow shows a fixed error in
-its frame and restarts it after 1, 5 and 15 seconds, at most three times;
-a package or protocol error waits for the user to enable it again. The
-numbers are in [limits](limits.md#logic).
+Going over a budget ends only that widget. PlayerVox OverCrow shows a fixed
+error in its frame and restarts it after 1, 5 and 15 seconds, at most three
+times; a package or protocol error waits for the user to enable it again.
+The numbers are in [limits](limits.md#logic).
 
 ## Permissions and consent
 
@@ -40,22 +40,22 @@ declaration grants nothing by itself. When the widget is installed, the
 Control Center proposes each permission checked, and the user may uncheck
 any. Later, the user allows or takes back each permission in the Control
 Center; taking one back restarts the widget without it.
-OverCrow checks the permission again at every call of a service.
+PlayerVox OverCrow checks the permission again at every call of a service.
 
 Four permissions open general services: `network` (exact HTTPS routes,
-through OverCrow's broker), `storage` (a key-value store for this widget
-only), `clipboardWrite` (writing text, during a user action) and
+through PlayerVox OverCrow's broker), `storage` (a key-value store for this
+widget only), `clipboardWrite` (writing text, during a user action) and
 `gameEvents` (named game events).
 
-Capabilities give access to data and actions of OverCrow and of the user's
-accounts. A **sensitive** capability reveals personal data or the game
-being played: a widget that declares one cannot also declare `network` or
-`clipboardWrite`, and its storage lasts only as long as its process, so the
-data cannot leave the machine through the widget.
+Capabilities give access to data and actions of PlayerVox OverCrow and of
+the user's accounts. A **sensitive** capability reveals personal data or the
+game being played: a widget that declares one cannot also declare `network`
+or `clipboardWrite`, and its storage lasts only as long as its process, so
+the data cannot leave the machine through the widget.
 
-Account connections (PlayerVox, Twitch) belong to OverCrow: sign-in, codes
-and tokens are drawn and kept by OverCrow, and a widget receives only the
-data its capability describes.
+Account connections (PlayerVox, Twitch) belong to PlayerVox OverCrow:
+sign-in, codes and tokens are drawn and kept by OverCrow, and a widget
+receives only the data its capability describes.
 
 Each permission, each capability and the services it opens are described
 in [services and permissions](services.md). Declare the least you need:
@@ -70,15 +70,15 @@ Services that change something for the user can be called only while the
 logic handles a real action of the user in the widget: a click, a key, an
 edit, a submitted form. A call from a timer, from a service answer or from
 a row of the options menu is refused with `gesture_required`. Widgets
-receive input only in OverCrow's Interactive mode; in Passive mode they are
-click-through. Deleting a note or a journal session also asks the user to
-confirm in a dialog drawn by OverCrow. See
+receive input only in PlayerVox OverCrow's Interactive mode; in Passive mode
+they are click-through. Deleting a note or a journal session also asks the
+user to confirm in a dialog drawn by OverCrow. See
 [calls that need a user action](services.md#calls-that-need-a-user-action).
 
 What the user writes to notes, ratings and chat never passes through your
 logic: a `form` with an `intent` sends the values of its own text fields and
-sliders, which OverCrow fills, edits and submits itself. Your logic can read
-them, not set them. See
+sliders, which PlayerVox OverCrow fills, edits and submits itself. Your
+logic can read them, not set them. See
 [forms that write user data](forms.md#forms-that-write-user-data).
 
 ## What a widget cannot do
@@ -88,9 +88,9 @@ them, not set them. See
 - Start processes, load native code, compile code at runtime or fetch code:
   the only code is the reviewed `logic.js` of the package.
 - See other widgets, their state, storage or permissions, or the game's
-  memory, window or input. OverCrow never injects into the game.
-- Draw outside its frame, cover or imitate OverCrow's frame, menus or
-  confirmations.
+  memory, window or input. PlayerVox OverCrow never injects into the game.
+- Draw outside its frame, cover or imitate PlayerVox OverCrow's frame, menus
+  or confirmations.
 - Read account tokens, cookies or credentials.
 - Read the clipboard.
 - Write to logs in production: `log.*` output appears only in a local
@@ -100,13 +100,13 @@ them, not set them. See
 ## What OverCrow verifies
 
 Every package is checked when it is admitted to the catalog and again each
-time OverCrow starts it: the signed catalog, the ledger of its files and
-the compiled view must match, or the widget does not start. See
+time PlayerVox OverCrow starts it: the signed catalog, the ledger of its
+files and the compiled view must match, or the widget does not start. See
 [the package](package.md#how-overcrow-checks-a-package) and
 [publishing and review](publishing.md).
 
 A version of the catalog can be suspended or revoked after its
-publication: OverCrow then stops the installed copy. See
+publication: PlayerVox OverCrow then stops the installed copy. See
 [version statuses](publishing.md#version-statuses).
 
 ## Reporting a vulnerability

package/dist/content/docs/en/service-reference.md

@@ -229,7 +229,7 @@ update.
 
 ### `notes.delete`
 
-- **Kind**: call, answered once; the user confirms it first, in a dialog drawn by OverCrow
+- **Kind**: call, answered once; the user confirms it first, in a dialog drawn by PlayerVox OverCrow
 - **Requires**: capability `notes.write`
 - **When it can be called**: Only during a user action
 - **Parameters**: `note`: text ≤ 128 bytes
@@ -292,7 +292,7 @@ update.
 
 ### `journal.delete`
 
-- **Kind**: call, answered once; the user confirms it first, in a dialog drawn by OverCrow
+- **Kind**: call, answered once; the user confirms it first, in a dialog drawn by PlayerVox OverCrow
 - **Requires**: capability `journal.delete`
 - **When it can be called**: Only during a user action
 - **Parameters**: `session`: text ≤ 128 bytes

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

@@ -28,8 +28,8 @@ Two kinds of authority exist, both declared in `permissions` of
 - four **permissions** for general services: `network`, `storage`,
   `clipboardWrite` and `gameEvents`;
 - **capabilities**, listed under `permissions.capabilities`, for the data
-  and actions of OverCrow itself and of the user's accounts: the frame
-  rate, the media player, notes, PlayerVox ratings, Twitch chat…
+  and actions of PlayerVox OverCrow itself and of the user's accounts: the
+  frame rate, the media player, notes, PlayerVox ratings, Twitch chat…
 
 <!-- source: docs/content/examples/weather/manifest.json -->
 ```json
@@ -89,9 +89,9 @@ async function readStored(key: string): Promise<JsonValue | undefined> {
 }
 ```
 
-**A subscription** takes a listener. OverCrow calls it with the current
-value at once, then with each new value, until you `cancel()` it or it
-ends with a failure. The listener comes last; a service with parameters
+**A subscription** takes a listener. PlayerVox OverCrow calls it with the
+current value at once, then with each new value, until you `cancel()` it or
+it ends with a failure. The listener comes last; a service with parameters
 takes them first.
 
 <!-- source: widgets/media/logic.ts -->
@@ -123,10 +123,10 @@ Services are grouped in namespaces of the SDK: `storage`, `http`,
 `twitch`). Every service, with its parameters and its result, is in the
 [service reference](service-reference.md).
 
-OverCrow checks every call when it arrives, in this order: the permission
-or capability, the parameters, the user action when the service needs one,
-then the account when it needs one. The SDK's types help you call a
-service right; they are not what enforces the rules.
+PlayerVox OverCrow checks every call when it arrives, in this order: the
+permission or capability, the parameters, the user action when the service
+needs one, then the account when it needs one. The SDK's types help you call
+a service right; they are not what enforces the rules.
 
 ## Errors
 
@@ -160,20 +160,20 @@ subscription that fails delivers the same error in its last update.
 | `gesture_required` | The service can be called only during a user action, and this call was not made while one was handled, or that action already allowed another call. |
 | `not_connected` | The service needs the user's PlayerVox or Twitch account, which is not connected at the moment. |
 | `stale_context` | What the call was about changed before the answer: another game, another account, another media player, an object deleted meanwhile. Read the current state again. |
-| `unavailable` | OverCrow's source for this data failed, or cannot act right now. A subscription that ends with it can be started again later. |
+| `unavailable` | PlayerVox OverCrow's source for this data failed, or cannot act right now. A subscription that ends with it can be started again later. |
 | `busy` | Too much is in progress: a confirmation is already open, a queue or the budget of network responses is full, or the provider asks to wait. Try again later. |
 | `cancelled` | The user declined the confirmation, or left Interactive mode while it was open. |
 | `quota_exceeded` | A quota is full: the storage, the timers, the notes, the favourite channels. |
 | `unsupported` | The target cannot do this: a media player that does not offer the command, for instance. |
-| `url_invalid` | `http.fetch`: the URL is not an absolute HTTPS URL that OverCrow accepts. |
+| `url_invalid` | `http.fetch`: the URL is not an absolute HTTPS URL that PlayerVox OverCrow accepts. |
 | `resolve_failed` | `http.fetch`: the host name could not be resolved. |
 | `address_denied` | `http.fetch`: the host name resolves to a local, private or otherwise non-public address. |
-| `too_many_addresses` | `http.fetch`: the host name resolves to more addresses than OverCrow accepts. |
+| `too_many_addresses` | `http.fetch`: the host name resolves to more addresses than PlayerVox OverCrow accepts. |
 | `peer_mismatch` | `http.fetch`: the server that answered is not at one of the addresses that were resolved and checked. |
-| `redirect_denied` | `http.fetch`: the server answered with a redirection. OverCrow follows none: declare and request the final URL. |
-| `encoding_denied` | `http.fetch`: the response is compressed or encoded in a way OverCrow does not accept, or its body does not decode as `as` asks (invalid JSON or text). |
-| `content_type_denied` | `http.fetch`: the media type of the response is not one that OverCrow accepts for this request. |
-| `response_metadata_limit` | `http.fetch`: the status line or the headers of the response are malformed or exceed OverCrow's bounds. |
+| `redirect_denied` | `http.fetch`: the server answered with a redirection. PlayerVox OverCrow follows none: declare and request the final URL. |
+| `encoding_denied` | `http.fetch`: the response is compressed or encoded in a way PlayerVox OverCrow does not accept, or its body does not decode as `as` asks (invalid JSON or text). |
+| `content_type_denied` | `http.fetch`: the media type of the response is not one that PlayerVox OverCrow accepts for this request. |
+| `response_metadata_limit` | `http.fetch`: the status line or the headers of the response are malformed or exceed PlayerVox OverCrow's bounds. |
 | `request_body_limit` | `http.fetch`: the request body is larger than 256 KiB. |
 | `response_body_limit` | `http.fetch`: the response body is larger than the bound of the network rule (`maxResponseBytes`, or 1 MiB without it and for `as: "image"`). |
 | `image_invalid` | `http.fetch` with `as: "image"`: the response is not a PNG, JPEG or WebP image within the image limits. |
@@ -185,8 +185,8 @@ Three habits cover most cases:
 
 - **Show a state, not an error message.** The codes are for your logic;
   the user sees "Forecast unavailable", not `transport_failed`.
-- **Retry a subscription that ended.** A source of OverCrow can fail while
-  the widget runs (the media player's session, for instance): the
+- **Retry a subscription that ended.** A source of PlayerVox OverCrow can
+  fail while the widget runs (the media player's session, for instance): the
   subscription ends with `unavailable`. Subscribe again a few seconds later
   with `timers.after`; OverCrow restarts the source for the new
   subscription. The Media widget waits five seconds:
@@ -231,10 +231,11 @@ The same call from a timer, from the answer of another service, from
 
 - One user action allows one protected call. Call the service directly in
   the handler, not after an `await` on something else.
-- Widgets receive input only in OverCrow's Interactive mode, so a protected
-  call can only happen there.
+- Widgets receive input only in PlayerVox OverCrow's Interactive mode, so a
+  protected call can only happen there.
 - `notes.delete` and `journal.delete` also ask the user to confirm, in a
-  dialog drawn by OverCrow; a declined confirmation is `cancelled`.
+  dialog drawn by PlayerVox OverCrow; a declined confirmation is
+  `cancelled`.
 
 The tables below say, for each service, when it can be called.
 
@@ -326,8 +327,8 @@ Each path and query parameter has a constraint:
 | `string` | `{ maxLength }` | Query parameters only; any text without control characters; `maxLength` from 1 to 256 bytes. |
 <!-- /generated:parameter-constraints -->
 
-The request leaves through OverCrow's broker, never from the widget's
-process. The broker:
+The request leaves through PlayerVox OverCrow's broker, never from the
+widget's process. The broker:
 
 - refuses any URL that no rule allows (`permission_denied`), before any
   DNS query;
@@ -363,8 +364,8 @@ once.
 
 ### Storage
 
-`storage` is a key-value store that OverCrow keeps for your widget only:
-`storage.get({ key })`, `storage.set({ key, value })`,
+`storage` is a key-value store that PlayerVox OverCrow keeps for your widget
+only: `storage.get({ key })`, `storage.set({ key, value })`,
 `storage.remove({ key })` and `storage.keys()`. A value is any JSON value.
 There is no file access.
 
@@ -403,7 +404,7 @@ user action. A widget cannot read the clipboard.
 ```
 
 Text that the user selects in a `text` element with the `selectable`
-attribute is copied by OverCrow itself, and needs no permission.
+attribute is copied by PlayerVox OverCrow itself, and needs no permission.
 
 ### Game events
 
@@ -413,9 +414,9 @@ attribute is copied by OverCrow itself, and needs no permission.
 
 ## Capabilities
 
-A capability gives access to data or actions that OverCrow holds: what the
-game's use of the machine, the media player, the user's notes, their
-PlayerVox and Twitch accounts.
+A capability gives access to data or actions that PlayerVox OverCrow holds:
+what the game's use of the machine, the media player, the user's notes,
+their PlayerVox and Twitch accounts.
 
 <!-- generated:capability-list -->
 | Capability | Sensitive | Account | Meaning |
@@ -494,9 +495,9 @@ widget needs both an HTTP API and a sensitive capability, make two widgets.
 ### Accounts
 
 Some capabilities need the user's PlayerVox or Twitch account. The
-connection belongs to OverCrow: it draws the sign-in, keeps the tokens and
-shows its own panel over the widget while the account is signed out. A
-widget never sees a token; it receives only the data its capability
+connection belongs to PlayerVox OverCrow: it draws the sign-in, keeps the
+tokens and shows its own panel over the widget while the account is signed
+out. A widget never sees a token; it receives only the data its capability
 describes, and its calls fail with `not_connected` while the account is
 not connected.
 

package/dist/content/docs/en/style-properties.md

@@ -266,5 +266,5 @@ Lucide 1.34.0, 1777 icons.
 
 Any other name is refused, and the SDK's `IconName` type lists them all, so
 a wrong name in the logic is a TypeScript error. Within API v1 the set may
-grow but never loses or renames an icon. OverCrow draws the icons itself: a
-widget ships no icon font.
+grow but never loses or renames an icon. PlayerVox OverCrow draws the icons
+itself: a widget ships no icon font.

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

@@ -79,9 +79,9 @@ states: `button.primary:hover`. Compounds are joined by a space
 }
 ```
 
-The states are resolved by OverCrow, not by your logic: `:hover` and
-`:active` follow the pointer, `:focus` the keyboard focus, `:disabled` the
-`disabled` attribute, and `:checked` the state of a `toggle` or
+The states are resolved by PlayerVox OverCrow, not by your logic: `:hover`
+and `:active` follow the pointer, `:focus` the keyboard focus, `:disabled`
+the `disabled` attribute, and `:checked` the state of a `toggle` or
 `checkbox`. A widget is not told about pointer moves: a hover effect costs
 it nothing.
 
@@ -134,7 +134,7 @@ how the countdown example puts the time in the middle of its ring:
 }
 ```
 
-A widget cannot draw outside its frame: OverCrow clips it.
+A widget cannot draw outside its frame: PlayerVox OverCrow clips it.
 
 ## Values
 
@@ -144,17 +144,17 @@ the unit) and percentages, colours as `#rrggbb`, `#rrggbbaa` or
 tokens as `var(--name)`. The exact notation of each kind of value is in
 [values](style-properties.md#values).
 
-Lengths are logical pixels: OverCrow multiplies them by the user's content
-scale (50 % to 175 %) and by the screen's density, so `12px` is the same
-physical size on every screen. Shorthands expand as in CSS: one to four
+Lengths are logical pixels: PlayerVox OverCrow multiplies them by the user's
+content scale (50 % to 175 %) and by the screen's density, so `12px` is the
+same physical size on every screen. Shorthands expand as in CSS: one to four
 values for sides and corners, one or two for gaps.
 
 ## Design tokens
 
-A token is a value of OverCrow's design system, written `var(--name)`.
-Colour tokens change with the user's theme, light or dark: a widget styled
-with tokens follows the theme without any code. Prefer them to literal
-colours.
+A token is a value of PlayerVox OverCrow's design system, written
+`var(--name)`. Colour tokens change with the user's theme, light or dark: a
+widget styled with tokens follows the theme without any code. Prefer them to
+literal colours.
 
 <!-- source: docs/content/examples/countdown/style.ocss -->
 ```css
@@ -176,8 +176,9 @@ length. There is no fallback argument, and a widget cannot declare its own
 custom properties. All tokens are listed in
 [design tokens](style-properties.md#design-tokens).
 
-OverCrow draws the panel behind the widget (`--color-surface-panel`), its
-frame and its shadow: start from a transparent background.
+PlayerVox OverCrow draws the panel behind the widget
+(`--color-surface-panel`), its frame and its shadow: start from a
+transparent background.
 
 ## Text
 
@@ -187,8 +188,8 @@ container to style what it holds.
 
 - Three font families exist: `ui` (Noto Sans, the default), `mono` (Noto
   Sans Mono, for values) and `display` (Space Grotesk, for grades and
-  scores). OverCrow bundles them; system fonts are never used, so a widget
-  looks the same on every machine.
+  scores). PlayerVox OverCrow bundles them; system fonts are never used, so
+  a widget looks the same on every machine.
 - `font-variant-numeric: tabular-nums` gives digits one width, so a
   changing number does not move its neighbours.
 - `text-overflow: ellipsis` cuts an overflowing line with `…`;
@@ -224,9 +225,9 @@ plays a `@keyframes` block of the same sheet.
 
 Only properties that change paint, not layout, can be animated:
 `opacity`, `color`, `background-color`, `border-color` and `transform`.
-A `@keyframes` block holds only those. OverCrow runs the animation itself:
-no timer and no code of the widget run while it plays, and nothing is
-repainted when nothing changes. A widget that is hidden does not animate.
+A `@keyframes` block holds only those. PlayerVox OverCrow runs the animation
+itself: no timer and no code of the widget run while it plays, and nothing
+is repainted when nothing changes. A widget that is hidden does not animate.
 
 `@keyframes` is the only at-rule. Its name is an identifier that is not an
 animation keyword, unique in the sheet.

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

@@ -5,9 +5,9 @@ a game or an account:
 
 - **Unit tests of the logic**, in Node.js, with `@overcrow/sdk/testing`:
   fast, for the functions of `logic.ts`.
-- **Scenarios**, played by `overcrow-widget test` in OverCrow's **headless
-  runtime**: the real VM, style, layout and renderer, OverCrow's own
-  checks, simulated services, virtual time and reference images. What
+- **Scenarios**, played by `overcrow-widget test` in PlayerVox OverCrow's
+  **headless runtime**: the real VM, style, layout and renderer, OverCrow's
+  own checks, simulated services, virtual time and reference images. What
   passes there is what the overlay shows.
 
 <!-- source: templates/counter/tests/example.scenario.json -->
@@ -35,8 +35,8 @@ is "Increase", then checks the new text and image.
 by `overcrow-widget init`, otherwise
 `npm install --save-dev --save-exact @overcrow/sdk@1.0.0`.
 
-`installRuntime()` puts a stand-in for OverCrow in place before the logic
-is imported: service calls return promises that your test settles,
+`installRuntime()` puts a stand-in for PlayerVox OverCrow in place before
+the logic is imported: service calls return promises that your test settles,
 subscriptions take the values you push, timers fire when you advance the
 time, and `Date.now()` is virtual.
 
@@ -74,17 +74,17 @@ test("one timer at the next local minute, then each minute", () => {
 | --- | --- |
 | `installRuntime({ now, host })` | Installs the stand-in; `Date.now()` returns the virtual time. One at a time. |
 | `now`, `advance(ms)` | The virtual time; `advance` fires the timers that fall due, in order (a repeating one re-arms), and returns their count. |
-| `setHost(changes)` | Changes `host` as OverCrow does: `region`, `locale`, `options`… |
+| `setHost(changes)` | Changes `host` as PlayerVox OverCrow does: `region`, `locale`, `options`… |
 | `calls`, `lastCall(service)` | Every service call, with `resolve(value)` and `reject(code)`. |
 | `push(service, value)`, `fail(service, code)` | The next update, or the final failure, of the subscriptions to a service. |
 | `menu(row)` | Chooses an `action` row of the options menu. |
 | `draws`, `logs`, `timers`, `table` | What the logic sent: canvas drawings, logs, timers, and the functions of the view. |
 | `uninstall()` | Removes the stand-in and gives `Date.now` back. |
 
-The stand-in runs your logic only: it does not apply OverCrow's rules (the
-grants, the accounts, the user-action rule) and renders nothing. Scenarios
-do. The reference widgets compile their `logic.ts` with a small loader
-before importing it:
+The stand-in runs your logic only: it does not apply PlayerVox OverCrow's
+rules (the grants, the accounts, the user-action rule) and renders nothing.
+Scenarios do. The reference widgets compile their `logic.ts` with a small
+loader before importing it:
 
 <!-- source: widgets/clock/tests/load-logic.mjs -->
 ```js
@@ -143,13 +143,13 @@ Everything is optional.
 | `size` | the manifest's preferred size | `{ width, height }` of the frame, in logical pixels; the manifest's `fit` still applies. |
 | `mode` | `passive` | `interactive` gives input to the widget. |
 | `visible` | `true` | Hidden, the widget gets no timer tick. |
-| `frame` | `false` | `true` captures OverCrow's frame around the content. |
+| `frame` | `false` | `true` captures PlayerVox OverCrow's frame around the content. |
 | `background` | the theme's panel colour | `#rrggbb` behind the widget. |
 | `region` | `us`, date order of the locale | `{ numberFormat, dateOrder }`. |
 | `zone` | UTC | `{ offsetMinutes, transitions: [{ at, offsetMinutes }] }`: the user's UTC offset, and the instants at which it changes. |
 | `startAt` | 2026-01-01T00:00:00Z | The virtual time at which the widget starts, in Unix milliseconds. |
 | `options` | the rows' defaults | Values of the rows of the options menu. |
-| `grants` | `"declared"` | Or the exact list of what the user granted (`storage`, `network`, `fps.read`…): OverCrow refuses the rest. |
+| `grants` | `"declared"` | Or the exact list of what the user granted (`storage`, `network`, `fps.read`…): PlayerVox OverCrow refuses the rest. |
 | `accounts` | connected | `{ playervox, twitch }`, each `connected`, `disconnected`, `pending`, `expired` or `offline`. |
 | `features` | all | The data sources of the machine, for `requires`. |
 | `storage` | empty | The widget's storage before it starts. |
@@ -174,15 +174,16 @@ Everything is optional.
   },
 ```
 
-With an account that is not `connected`, OverCrow draws its own account
-panel over the widget, as it does for the user; capture it with `frame`.
+With an account that is not `connected`, PlayerVox OverCrow draws its own
+account panel over the widget, as it does for the user; capture it with
+`frame`.
 
 ### `fixtures`
 
-Fixtures replace where the data comes from, never OverCrow's checks. A call
-first passes the grants, its parameters, the user-action rule and the
-account check, exactly as in the overlay; only then does a fixture answer
-it. Every value must have the shape of the service's
+Fixtures replace where the data comes from, never PlayerVox OverCrow's
+checks. A call first passes the grants, its parameters, the user-action rule
+and the account check, exactly as in the overlay; only then does a fixture
+answer it. Every value must have the shape of the service's
 [result](result-shapes.md): one that does not is an error of the scenario,
 not of the widget.
 
@@ -191,7 +192,7 @@ not of the widget.
 | `subscriptions` | The value of a subscription when it starts; `publish` steps send the next ones. |
 | `calls` | The calls of a service, in order: `{ "value": … }` or `{ "error": code }`. A call beyond them is an error of the scenario. |
 | `http` | The `http.fetch` requests, each used once: `{ "request": { method, url }, "response": { status, contentType, body } }` (or `bodyBase64`), or `{ "request": …, "error": code }`. The manifest's network rules apply first, and the response bounds apply as in the overlay. |
-| `confirmations` | `accept` or `cancel`, in order, for OverCrow's confirmation of `notes.delete` and `journal.delete`. |
+| `confirmations` | `accept` or `cancel`, in order, for PlayerVox OverCrow's confirmation of `notes.delete` and `journal.delete`. |
 | `intents` | The answer to each submitted [write intent](forms.md#forms-that-write-user-data), in order: `"accepted"`, `{ "error": code }` or `"pending"`. |
 
 <!-- source: widgets/stopwatch/tests/errors.scenario.json -->
@@ -267,7 +268,7 @@ not of the widget.
     ]
 ```
 
-The codes that OverCrow gives itself (`permission_denied`,
+The codes that PlayerVox OverCrow gives itself (`permission_denied`,
 `gesture_required`, `not_connected`, `invalid_request`) cannot be written
 in a fixture: get them the real way, with `grants`, `accounts`, a call
 outside a user action, or wrong parameters. Storage, timers and the
@@ -275,9 +276,9 @@ clipboard are OverCrow's own and need no fixture.
 
 ### `assets`
 
-Images that a fixture hands to the widget, as OverCrow hands it a media
-cover or a chat emote: `{ "<name>": "<path>" }`, at most 8, each a PNG or
-JPEG of the project (`tests/assets/cover.png`). Where a result holds an
+Images that a fixture hands to the widget, as PlayerVox OverCrow hands it a
+media cover or a chat emote: `{ "<name>": "<path>" }`, at most 8, each a PNG
+or JPEG of the project (`tests/assets/cover.png`). Where a result holds an
 image handle, the fixture writes `"fixture:<name>"`.
 
 ### `steps`
@@ -313,7 +314,7 @@ was sent and nothing is in flight. There is no real waiting.
 | `state` | `starting`, `running`, `restarting`, `failed`, `refused` or `stopped`. |
 | `fault` | The last fault of the widget's VM, or `none`. |
 | `clipboard` | The last text the widget wrote to the clipboard. |
-| `intents` | Exactly these write intents were submitted since the previous `intents` expectation, in order: `{ intent, fields?, outcome? }`. `fields` are the exact values OverCrow's form sent. |
+| `intents` | Exactly these write intents were submitted since the previous `intents` expectation, in order: `{ intent, fields?, outcome? }`. `fields` are the exact values PlayerVox OverCrow's form sent. |
 
 <!-- source: templates/chart/tests/example.scenario.json -->
 ```json
@@ -365,7 +366,7 @@ bytes, on Linux and on Windows.
 - Time is virtual: `Date.now()` and `new Date()` return the scenario's
   time, timers fire when the scenario moves it.
 - `Math.random()` is seeded with a fixed value.
-- Text uses the fonts bundled with OverCrow, never the system's.
+- Text uses the fonts bundled with PlayerVox OverCrow, never the system's.
 - Rendering does not depend on the graphics card.
 
 This holds for the test runtime only: in the overlay, time and randomness
@@ -373,22 +374,22 @@ are real.
 
 ## The headless runtime
 
-`overcrow-widget-headless` is OverCrow's own code without a window: it
-validates the package as the overlay does and runs the widget's logic in
-the same sandbox. `overcrow-widget test` runs the version this CLI pins,
-0.7.1-beta.1, and prints its version and SHA-256. Without the operating
-system's sandbox the runtime refuses to run and says so; the test command
-then ends with status 2.
+`overcrow-widget-headless` is PlayerVox OverCrow's own code without a
+window: it validates the package as the overlay does and runs the widget's
+logic in the same sandbox. `overcrow-widget test` runs the version this CLI
+pins, 0.7.2-beta.1, and prints its version and SHA-256. Without the
+operating system's sandbox the runtime refuses to run and says so; the test
+command then ends with status 2.
 
 The first time `test` needs the runtime, it downloads it: from the
-creator tools ZIP of your platform in the OverCrow release that
+creator tools ZIP of your platform in the PlayerVox OverCrow release that
 published it, it keeps only the runtime, and only once its SHA-256 is the
 one this CLI pins. The ZIP is not kept. The runtime then stays in the CLI's cache:
 
 | Platform | Path |
 | --- | --- |
-| Linux | `~/.cache/overcrow-widget/runtime/0.7.1-beta.1/` (`$XDG_CACHE_HOME` instead of `~/.cache` when set) |
-| Windows | `%LOCALAPPDATA%\overcrow-widget\runtime\0.7.1-beta.1\` |
+| Linux | `~/.cache/overcrow-widget/runtime/0.7.2-beta.1/` (`$XDG_CACHE_HOME` instead of `~/.cache` when set) |
+| Windows | `%LOCALAPPDATA%\overcrow-widget\runtime\0.7.2-beta.1\` |
 
 To work offline, put the runtime of the creator tools ZIP there yourself
 (executable on Linux): `test` finds it and downloads nothing. With
@@ -397,4 +398,4 @@ To work offline, put the runtime of the creator tools ZIP there yourself
 The CLI checks its SHA-256 before every run. When a download fails,
 nothing is kept and `test` says to try again or to pass `--runtime`.
 `--runtime <path>` runs another runtime instead, such as one built from
-OverCrow; the output then says it is not the pinned one.
+PlayerVox OverCrow; the output then says it is not the pinned one.

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

@@ -57,8 +57,8 @@ in text, are refused: write `{` and `}`.
 Each element has a fixed content, a set of attributes and the events it can
 send. Containers (`box`, `scroll`, `list`, `form`, `popover`, `button`)
 hold other elements; `text` holds text and inline children; the others are
-leaves that OverCrow draws: `icon`, `image`, `toggle`, `slider`, `field`,
-`chart`, `gauge`…
+leaves that PlayerVox OverCrow draws: `icon`, `image`, `toggle`, `slider`,
+`field`, `chart`, `gauge`…
 
 <!-- generated:element-list -->
 | Element | Meaning |
@@ -132,9 +132,10 @@ view is compiled:
 | text, identifier | the text itself |
 | image | a file of the package: `src="assets/logo.png"` |
 
-`attr={expression}` binds the attribute to an expression instead; OverCrow
-checks every value the widget sends. Values that exist only when the widget
-runs, such as an image handed by a service, must be bound.
+`attr={expression}` binds the attribute to an expression instead;
+PlayerVox OverCrow checks every value the widget sends. Values that exist
+only when the widget runs, such as an image handed by a service, must be
+bound.
 
 Five attributes exist on every element:
 
@@ -176,8 +177,8 @@ a component, where it would name several nodes.
 
 ## Events
 
-`on:event={handler}` asks OverCrow to send an event of the element to the
-logic. Without it, the widget does not hear about the event at all: a
+`on:event={handler}` asks PlayerVox OverCrow to send an event of the element
+to the logic. Without it, the widget does not hear about the event at all: a
 widget is not told about pointer moves or key presses it has not asked for.
 
 A handler is written in one of two ways:
@@ -202,8 +203,8 @@ The events are `activate`, `contextmenu`, `wheel`, `keydown`, `input`,
 and each [element](elements.md#elements) lists the ones it sends. Some of
 them are user actions, during which a widget may call a protected service;
 see [calls that need a user action](services.md#calls-that-need-a-user-action).
-Widgets receive input only in OverCrow's Interactive mode: in Passive mode,
-clicks go through them to the game.
+Widgets receive input only in PlayerVox OverCrow's Interactive mode: in
+Passive mode, clicks go through them to the game.
 
 ## Conditions, loops and components
 
@@ -236,7 +237,7 @@ may separate them.
 
 `for` repeats its children for each item of a list. `each`, `as` and `key`
 are all required, and the key must be unique among the repeated items: it
-is how OverCrow knows which row moved, appeared or went away.
+is how PlayerVox OverCrow knows which row moved, appeared or went away.
 
 <!-- source: widgets/warframe-market/view.ocml -->
 ```xml
@@ -248,8 +249,8 @@ is how OverCrow knows which row moved, appeared or went away.
       </for>
 ```
 
-For a long list, put the `for` in a `list` element: OverCrow lays out and
-paints only the rows that are visible.
+For a long list, put the `for` in a `list` element: PlayerVox OverCrow lays
+out and paints only the rows that are visible.
 
 ### Components