@mostra/cli 0.0.0-stage → 0.2.0

package/dist/reference/errors/MOSTRA_REGRESSION_ARIA.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_ARIA
+severity: warning
+phase: regression
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_REGRESSION_ARIA
+
+Controls or landmarks gone since the last passing version. Severity: warning. Phase: regression.
+
+## What it means
+
+Verify compared this source's accessibility snapshot with the newest version whose verdict passed, rendered in the same run with the same data. The controls or landmarks the message lists (by role and name) were there and aren't now. A redesign may remove them on purpose.
+
+## How to fix it
+
+If they should be gone, nothing needs to change. If not, look at what removed them.
+
+## Hint
+
+Observed only: the last passing version had these controls or landmarks and this source doesn't; a change that removed them on purpose needs nothing more.

package/dist/reference/errors/MOSTRA_REGRESSION_FIELD_REMOVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_FIELD_REMOVED
+severity: warning
+phase: contract
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_REGRESSION_FIELD_REMOVED
+
+Field gone since the last passing version. Severity: warning. Phase: contract.
+
+## What it means
+
+A field ID the last passing version used is gone from this source. Viewers' answers under it become orphans when they switch (D42): kept, shown read-only and delivered, but not editable. The message gives how many saved answers it affects.
+
+## How to fix it
+
+If the field was renamed by mistake, keep its old ID. If it was removed on purpose, nothing needs to change.
+
+## Hint
+
+Observed only: answers saved under this field ID won't carry over to this version; a field removed on purpose needs nothing more.

package/dist/reference/errors/MOSTRA_REGRESSION_LIVE_REMOVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_LIVE_REMOVED
+severity: warning
+phase: contract
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_REGRESSION_LIVE_REMOVED
+
+Live source gone since the last passing version. Severity: warning. Phase: contract.
+
+## What it means
+
+A live source (`live.ts` export) the last passing version had is gone, so its producer stops and hosts that push to it push to a key no page reads.
+
+## How to fix it
+
+If it was renamed by mistake, keep its name. If it was removed on purpose, nothing needs to change.
+
+## Hint
+
+Observed only: the last passing version had this live source and this source doesn't; one removed on purpose needs nothing more.

package/dist/reference/errors/MOSTRA_REGRESSION_PAGE_REMOVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_PAGE_REMOVED
+severity: warning
+phase: contract
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_REGRESSION_PAGE_REMOVED
+
+Page route gone since the last passing version. Severity: warning. Phase: contract.
+
+## What it means
+
+A route of `pages/` the last passing version had is gone, so links and bookmarks to it now open the artifact's fallback page.
+
+## How to fix it
+
+If it was renamed by mistake, keep its path. If it was removed on purpose, nothing needs to change.
+
+## Hint
+
+Observed only: the last passing version had this page route and this source doesn't; one removed on purpose needs nothing more.

package/dist/reference/errors/MOSTRA_REGRESSION_PIXELS.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_PIXELS
+severity: warning
+phase: regression
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_REGRESSION_PIXELS
+
+Page looks different from the last passing version. Severity: warning. Phase: regression.
+
+## What it means
+
+Verify rendered the newest version whose verdict passed and this source at the same viewport, clock and data, and the share of pixels the message gives differs between them. Any intended visual change shows here too.
+
+## How to fix it
+
+If the change is one you made on purpose, nothing needs to change. To see where it is, read the ARIA snapshots, or look at the diff image the message names if you can view images.
+
+## Hint
+
+Observed only: this share of the viewport's pixels differs from the last passing version; an intended visual change shows here too and needs nothing more.

package/dist/reference/errors/MOSTRA_RUNTIME_BLANK.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_RUNTIME_BLANK
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_RUNTIME_BLANK
+
+Page rendered nothing. Severity: error. Phase: runtime.
+
+## What it means
+
+After the page reported ready, no element had a visible box (text, image, SVG, canvas or video) and the screenshot was one uniform color. Usually the page threw during its first render, rendered nothing until data arrived, or hid everything with CSS.
+
+## How to fix it
+
+Look at the other diagnostics for an error during the first render, and make the page show content (or a loading state) right away.
+
+## Hint
+
+Make the page render something visible; check its first render and its imports.

package/dist/reference/errors/MOSTRA_RUNTIME_NOT_READY.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_RUNTIME_NOT_READY
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_RUNTIME_NOT_READY
+
+Page never became ready. Severity: error. Phase: runtime.
+
+## What it means
+
+The page never reported `mostra/ready`: the client runtime didn't mount it within the time verify allows, usually because the entry threw while loading or a module failed to load.
+
+## How to fix it
+
+Fix the load error the other diagnostics report. A page that waits for data should render a loading state first.
+
+## Hint
+
+Make sure the entry's default export renders; check the other diagnostics for an error at load.

package/dist/reference/errors/MOSTRA_RUNTIME_PAGE_ERROR.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_RUNTIME_PAGE_ERROR
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_RUNTIME_PAGE_ERROR
+
+Uncaught error in the page. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact's page threw an error that nothing caught, or a promise rejected with nothing handling it, while verify rendered it or while the smoke test used a control (the message says which). A viewer's page would meet the same error.
+
+## How to fix it
+
+Find the stack's first frame in the artifact's code and fix the error there, or catch it where the page can recover.
+
+## Hint
+
+Fix the error the message names; it was thrown in the page and nothing caught it.

package/dist/reference/errors/MOSTRA_RUNTIME_WORKER_CRASHED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_RUNTIME_WORKER_CRASHED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_RUNTIME_WORKER_CRASHED
+
+Artifact server code crashed. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact version's worker process exited while serving a call: it threw outside any call, ran out of its heap (1 GiB by default), or kept its event loop blocked past the watchdog (10 s by default). Other artifacts and the gateway keep working (RT-04). Mostra appends `worker.crashed` with the cause and starts the worker again on the next request, waiting longer after each crash (1 s up to 60 s). `verify` reports it too when the source's server code crashes, fails to load or hangs while the page renders, even when the page handled the failed call.
+
+## How to fix it
+
+Fix the crash in the server code. A long synchronous computation can raise `limits.watchdogMs` in the manifest, and a large data set `limits.heapMb`; both are stability limits, not security ones.
+
+## Hint
+
+Read the cause and the worker's last output, fix the server code, and publish again.

package/dist/reference/errors/MOSTRA_RUNTIME_WORKER_PARKED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_RUNTIME_WORKER_PARKED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_RUNTIME_WORKER_PARKED
+
+Artifact server code keeps crashing. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact version's worker crashed more than 5 times in 10 minutes, so Mostra stopped starting it (FAILURE_MODEL §2). Calls, runs and live sources of that version answer this code until the park clears, and the shell tells the viewer that the artifact's server code keeps crashing.
+
+## How to fix it
+
+Find the cause in the message and the worker's output, fix it, and publish again: a new publish, `verify` or a restart of the instance clears the park.
+
+## Hint
+
+Fix the server code and publish again, which clears the park; the message names the last crash's cause.

package/dist/reference/errors/MOSTRA_SECRET_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SECRET_MISSING
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SECRET_MISSING
+
+Secret not set. Severity: error. Phase: runtime.
+
+## What it means
+
+Server code called `secret(name)` for a secret that neither the host's `secrets` port, the artifact's own secrets nor the home's shared secrets hold (D44). The call throws, and an action run fails with this code.
+
+## How to fix it
+
+Set the secret for the artifact (`mostra secret set NAME --artifact <path|id>`) or for every artifact of the home (`mostra secret set NAME`), passing the value on stdin, then run the action again. Secret values never go into the artifact's source.
+
+## Hint
+
+Set the secret with `mostra secret set NAME`, reading the value from stdin.

package/dist/reference/errors/MOSTRA_SMOKE_BUDGET.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SMOKE_BUDGET
+severity: hint
+phase: smoke
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SMOKE_BUDGET
+
+Smoke test stopped at its budget. Severity: hint. Phase: smoke.
+
+## What it means
+
+The page has more controls than the smoke test uses in one run, so it stopped at its budget. The controls it used are counted in `smoke.interactions`.
+
+## How to fix it
+
+Nothing is required.
+
+## Hint
+
+Nothing to fix: the smoke test stops after 200 interactions or 60 s.

package/dist/reference/errors/MOSTRA_SMOKE_NO_EFFECT.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SMOKE_NO_EFFECT
+severity: warning
+phase: smoke
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SMOKE_NO_EFFECT
+
+Control showed no effect. Severity: warning. Phase: smoke.
+
+## What it means
+
+Verify's smoke test clicked or hovered the control the message names, once among the other controls and again after them, and saw no change either time: no change to the page, no request, no saved field, no navigation and no error. Controls that are disabled or already active (the selected tab) are skipped, and those that open on hover are hovered. A control can still be fine: it may act on something verify can't observe, such as the clipboard or a sound.
+
+## How to fix it
+
+Read the control's handler. If it does what it should, nothing needs to change; if it is meant to change the page, look at why it doesn't.
+
+## Hint
+
+Observed only: using this control twice changed nothing verify could see; a control that acts on something verify can't observe needs no change.

package/dist/reference/errors/MOSTRA_SUBMIT_ALREADY.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_ALREADY
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_ALREADY
+
+Already submitted. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact's submission policy is `once`, and a submission already closed this draft: for scope `per-artifact` any viewer's submission closes every draft, for `per-viewer` the viewer's own. A submission is immutable and final, so Mostra refuses a second one and further edits to the closed draft. The refusal carries the existing submission. A repeated submit of the same view at the same draft revision is not refused: it returns the original submission.
+
+## How to fix it
+
+Read the existing submission with `mostra results <artifact>`. When another round of answers is wanted, publish a new artifact linked to this one (`links: [{ rel: "round-of", artifact }]`), or have the host publish with the `epochs` policy.
+
+## Hint
+
+This artifact takes one submission, and it was made; read it with `mostra results`.

package/dist/reference/errors/MOSTRA_SUBMIT_BLOCKED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_BLOCKED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_BLOCKED
+
+Answers missing before submit. Severity: error. Phase: runtime.
+
+## What it means
+
+Before a submit, the shell and the client runtime check every mounted field (D106): a `required` field without a value, a value its `validate` rejects, or a conflict the viewer hasn't resolved blocks the submit. The diagnostic lists the blockers with their field IDs and labels; `useSubmit().blockers` lists them before anyone submits. Nothing was submitted.
+
+## How to fix it
+
+Show `useSubmit().blockers` next to your submit button, or let the shell list them by label. Answer the required fields, fix the invalid values, and keep or take the conflicting values, then submit again.
+
+## Hint
+
+Fill in the fields this diagnostic lists, fix their errors or resolve their conflicts, then submit again.

package/dist/reference/errors/MOSTRA_SUBMIT_CHANNEL_DENIED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_CHANNEL_DENIED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_CHANNEL_DENIED
+
+Submit channel not allowed. Severity: error. Phase: runtime.
+
+## What it means
+
+A submission comes through one of two channels (D40): the shell's trusted Submit (`shell`), which only a person can press, or the artifact's own code (`artifact`, `useSubmit().submit()` and `useChoice().choose()`). The host decides which it accepts (D108): through `HomeConfig.submitChannels` for the home, or its `trustedControls` port for each artifact. This view allows only the other channel, so Mostra refused the submit or the choice. `useSubmit().allowed` is `false` in such a view.
+
+## How to fix it
+
+Ask the viewer to press the shell's Submit (relabel it with `useSubmitControl`), and use `useChoice(id, { candidates })` to have the shell render a trusted Choose. Check `allowed` before showing an in-page submit button.
+
+## Hint
+
+Let the viewer submit with the shell's trusted Submit; this host doesn't take submissions from artifact code.

package/dist/reference/errors/MOSTRA_SUBMIT_NOT_FOUND.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_NOT_FOUND
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_NOT_FOUND
+
+No such submission. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact has no submission yet, or none with the ID asked for. Submissions are durable once made, so this means none was made (or the ID belongs to another artifact or home).
+
+## How to fix it
+
+Run `mostra wait <artifact> --until submitted` to block until the viewer submits, then read the results. List the artifact's submissions through `submission.created` events.
+
+## Hint
+
+Wait for a submission with `mostra wait <artifact> --until submitted`, or name one that exists.

package/dist/reference/errors/MOSTRA_SUBMIT_POLICY_NONE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_POLICY_NONE
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_POLICY_NONE
+
+Artifact takes no submissions. Severity: error. Phase: runtime.
+
+## What it means
+
+The artifact's submission policy is `none` (D63): long-lived artifacts such as dashboards and task managers talk to agents through artifact state, actions, signals and events, and the shell shows no Submit control. Mostra refuses a submit, and a `wait --until submitted`, on such an artifact.
+
+## How to fix it
+
+Wait for a signal (`--until signal:<name>`), a state change (`--until state:<field>`) or an event instead, and read state with `mostra state get`. To collect submissions, publish with policy `once` or `epochs`.
+
+## Hint
+
+Exchange data through artifact state, actions and signals; this artifact has no submissions.

package/dist/reference/errors/MOSTRA_SUBMIT_REVISION_MOVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_REVISION_MOVED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_REVISION_MOVED
+
+Draft changed before submit. Severity: error. Phase: runtime.
+
+## What it means
+
+A submit names the draft revision the viewer saw (`expectedRevision`), and the draft has changed since: another tab, device or writer saved an edit. Mostra never makes a submission from content the viewer didn't see (FAILURE_MODEL §4), so it refuses. The message names the draft's current revision.
+
+## How to fix it
+
+Let the page reload the draft so the viewer sees exactly what will be sent, then submit with the new revision. The shell and the client runtime flush pending saves before they submit, which makes this rare.
+
+## Hint
+
+Reload the draft, check what changed, and submit again with its current revision.

package/dist/reference/errors/MOSTRA_SUBMIT_SIGNAL_INVALID.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_SIGNAL_INVALID
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_SIGNAL_INVALID
+
+Invalid signal. Severity: error. Phase: runtime.
+
+## What it means
+
+A signal names something the artifact wants a host's attention for, such as `ping-agent`. Its name is 1 to 64 characters of letters, digits, `.`, `_` and `-`, starting with a letter or digit, and its payload is JSON of at most 64 KiB. This one broke one of those rules. The name `submit` is reserved for submissions.
+
+## How to fix it
+
+Rename the signal or shrink its payload; put large data into a field or artifact state and send its ID in the payload.
+
+## Hint
+
+Name signals with letters, digits, `.`, `_` and `-`, and keep their payload under 64 KiB of JSON.

package/dist/reference/errors/MOSTRA_SUBMIT_VIEW_INVALID.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_SUBMIT_VIEW_INVALID
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_SUBMIT_VIEW_INVALID
+
+Unknown view. Severity: error. Phase: runtime.
+
+## What it means
+
+Mutations and submits name the view they come from, the one the shell created when it opened this frame. The view named doesn't exist, belongs to another artifact, or belongs to another viewer. Mostra binds every submission to the exact version its view showed, so it refuses a view it can't place.
+
+## How to fix it
+
+Use the `viewId` the shell handed this frame. A page opened outside Mostra's shell has no view and can't submit.
+
+## Hint
+
+Send the view ID this page was opened with.

package/dist/reference/errors/MOSTRA_TARGET_UNAVAILABLE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_TARGET_UNAVAILABLE
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_TARGET_UNAVAILABLE
+
+Not available in this delivery target. Severity: error. Phase: runtime.
+
+## What it means
+
+The page called something that needs Mostra's server, such as a server function, and this delivery target doesn't provide it: a static export, a file opened from disk, or a runtime without server support. The page keeps working without it.
+
+## How to fix it
+
+Open the artifact through its Mostra link, where server functions, submissions and live data are available. In a static export, handle the error so the page explains what isn't available.
+
+## Hint
+
+Open the published version through Mostra to use this feature.

package/dist/reference/errors/MOSTRA_TYPE_ERROR.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_TYPE_ERROR
+severity: error
+phase: compile
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_TYPE_ERROR
+
+Type error. Severity: error. Phase: compile.
+
+## What it means
+
+TypeScript's checker (`tsc --noEmit`, TypeScript 7) found an error in the artifact's code. Verify checks with the artifact's own `tsconfig.json` when it has one, else in strict mode without the unused-variable rules, and resolves imports exactly as the build does. MDX isn't checked.
+
+## How to fix it
+
+Open the file at the reported line and fix the code, for example a missing property, a wrong argument type or a misspelled import.
+
+## Hint
+
+Fix the type error at the reported location; the message carries TypeScript's code and text.

package/dist/reference/errors/MOSTRA_TYPE_UNTYPED_PACKAGE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_TYPE_UNTYPED_PACKAGE
+severity: warning
+phase: compile
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_TYPE_UNTYPED_PACKAGE
+
+Package without type declarations. Severity: warning. Phase: compile.
+
+## What it means
+
+The artifact imports a package that ships no type declarations (TypeScript's TS7016). The package still builds and runs, so this is a warning: its values are typed `any`.
+
+## How to fix it
+
+Optionally add a declaration file such as `declare module "<package>";`, or a typed wrapper, to the artifact.
+
+## Hint
+
+Nothing breaks: the package works without types; declare a module for it if you want them checked.

package/dist/reference/errors/MOSTRA_VERIFY_ACTION_SKIPPED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_ACTION_SKIPPED
+severity: hint
+phase: smoke
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_VERIFY_ACTION_SKIPPED
+
+Action skipped in verify. Severity: hint. Phase: smoke.
+
+## What it means
+
+Verify's smoke test never runs a server function that doesn't check `dryRun()` (D55). When the page called one, verify refused the call instead: the page's `run()` or server reference rejected with a `MostraError` carrying this code, as it would for any failed action. The verdict lists every such function in `smoke.skippedActions`. Nothing was sent, written or charged.
+
+## How to fix it
+
+Nothing is wrong. To have verify exercise the action, add `if (dryRun()) return <a representative result>;` before its side effects; verify then runs it with `dryRun()` true.
+
+## Hint
+
+To have verify run this action, check `dryRun()` from `@mostra/server` in it and return early without its side effects when it is true.

package/dist/reference/errors/MOSTRA_VERIFY_BASELINE_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_BASELINE_MISSING
+severity: hint
+phase: regression
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_VERIFY_BASELINE_MISSING
+
+Baseline version's build is missing. Severity: hint. Phase: regression.
+
+## What it means
+
+The newest version that passed verify is recorded in the ledger, but its stored build isn't in the home any more, so verify couldn't render it and ran no regression stage.
+
+## How to fix it
+
+Nothing is required. A version published from this source becomes the next baseline.
+
+## Hint
+
+Nothing to fix here; publish again to give later versions a baseline.

package/dist/reference/errors/MOSTRA_VERIFY_CRASHED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_CRASHED
+severity: error
+phase: runtime
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_VERIFY_CRASHED
+
+Verify runner crashed. Severity: error. Phase: runtime.
+
+## What it means
+
+The verify runner, the child process that drives the browser, stopped before it finished (FAILURE_MODEL §2). The message carries its last lines of output. Nothing was published, and the next verify starts a fresh runner.
+
+## How to fix it
+
+Verify again. A crash that repeats for the same artifact can come from a page that exhausts the browser's memory; one that repeats for every artifact means the runtime's browser is damaged.
+
+## Hint
+
+Verify again; if it keeps crashing, report the message with `mostra doctor`'s output.