@mostra/cli 0.0.0-stage → 0.2.0

package/dist/reference/errors/MOSTRA_HOST_SUBSCRIPTION_UNKNOWN.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_SUBSCRIPTION_UNKNOWN
+severity: error
+phase: host
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HOST_SUBSCRIPTION_UNKNOWN
+
+Unknown subscription. Severity: error. Phase: host.
+
+## What it means
+
+The subscription ID belongs to no subscription on this connection: it was never created here, was ended with `events/unsubscribe`, or belonged to a connection that closed. Subscriptions live as long as their connection; a named subscriber's acknowledged cursor outlives it.
+
+## How to fix it
+
+Call `events/subscribe` again on this connection. With the same `name`, delivery resumes after the last acknowledged cursor.
+
+## Hint
+
+Subscribe again with `events/subscribe`, then use the ID it returns.

package/dist/reference/errors/MOSTRA_HOST_TIMEOUT.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_TIMEOUT
+severity: error
+phase: host
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HOST_TIMEOUT
+
+Request timed out. Severity: error. Phase: host.
+
+## What it means
+
+No response arrived within the time the caller allowed. The other side may still be working on the request, and it may still take effect.
+
+## How to fix it
+
+Retry with the same request ID, which returns the recorded result if the first attempt completed. Allow a longer timeout for slow operations.
+
+## Hint
+
+Retry the request with the same request ID, or allow it more time.

package/dist/reference/errors/MOSTRA_HYGIENE_CONTENT_TYPE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_CONTENT_TYPE
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_CONTENT_TYPE
+
+JSON content type required. Severity: error. Phase: hygiene.
+
+## What it means
+
+Requests that change state must have a JSON body. A form or plain-text body is something any website can send without asking the browser first, so the gateway refuses it with 415.
+
+## How to fix it
+
+Send `Content-Type: application/json` and a JSON body.
+
+## Hint
+
+Send the body as JSON with `Content-Type: application/json`.

package/dist/reference/errors/MOSTRA_HYGIENE_CSRF_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_CSRF_MISSING
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_CSRF_MISSING
+
+CSRF token missing or wrong. Severity: error. Phase: hygiene.
+
+## What it means
+
+Every request that changes state through a session carries the session's CSRF token in the `X-Mostra-CSRF` header. The token comes only from the session endpoint of the same origin, which no other page can read. A missing or different token is answered with 403.
+
+## How to fix it
+
+Read `csrf` from `GET /_mostra/session` (on the shell, `GET /a/<artifactId>/_mostra/session`) and send it with every POST. Mostra's client runtime and shell do this for you.
+
+## Hint
+
+Send the session's CSRF token from `GET /_mostra/session` in the `X-Mostra-CSRF` header.

package/dist/reference/errors/MOSTRA_HYGIENE_HEADERS_TOO_LARGE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_HEADERS_TOO_LARGE
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_HEADERS_TOO_LARGE
+
+The request's headers are too large. Severity: error. Phase: hygiene.
+
+## What it means
+
+The request's headers passed the gateway's limit of 1 MiB, more than any browser sends for one host's cookies. Every port of the loopback host shares one cookie jar, so a page on any of them can fill it. The gateway answers 431 with `Clear-Site-Data: "cookies"`, which empties the host's cookies, so the next request works. Mostra's sessions go with them and come back when a link is opened again.
+
+## How to fix it
+
+Open the artifact's link again. If it keeps happening, find the page that sets the cookies: it runs on this host.
+
+## Hint
+
+Open the link again: this page cleared the cookies that made the request too large.

package/dist/reference/errors/MOSTRA_HYGIENE_HOST_REFUSED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_HOST_REFUSED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_HOST_REFUSED
+
+Host not served. Severity: error. Phase: hygiene.
+
+## What it means
+
+The request's `Host` header named a host this gateway doesn't serve. Each gateway listener accepts exactly the host and port its capability URLs use, so a page that rebinds its own DNS name to the loopback address can't reach an artifact (DNS rebinding). The gateway answers 421.
+
+## How to fix it
+
+Use the URL from `view/url` or the publish receipt as it is, without replacing `127.0.0.1` by `localhost` or another name. A gateway started with `--bind` and `--url-host` accepts the URL host it was given.
+
+## Hint
+
+Open the artifact through the exact link Mostra gave you.

package/dist/reference/errors/MOSTRA_HYGIENE_NOT_SERVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_NOT_SERVED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_NOT_SERVED
+
+Nothing served here. Severity: error. Phase: hygiene.
+
+## What it means
+
+The gateway serves only published versions' client files and the browser-protocol paths under `/_mostra/`. Everything else in the home, such as sources, server bundles, staging and unpublished builds, has no URL. A path or method nothing answers gets 404 or 405.
+
+## How to fix it
+
+Check the path. Server code runs through the browser protocol, never as a file, and an artifact becomes viewable only once it is published.
+
+## Hint
+
+Request a published version's files or a documented `/_mostra/` path.

package/dist/reference/errors/MOSTRA_HYGIENE_ORIGIN_REFUSED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_ORIGIN_REFUSED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_ORIGIN_REFUSED
+
+Origin refused. Severity: error. Phase: hygiene.
+
+## What it means
+
+A request that changes state, opens a stream or upgrades to a WebSocket must carry an `Origin` header equal to the origin it is sent to. The gateway compares the strings exactly and answers 403 otherwise, so another website, or another artifact on a different port, can't drive this one.
+
+## How to fix it
+
+Call the gateway from the page it serves: the shell from the shell, the artifact from its own frame. Tools outside a browser send the listener's own origin.
+
+## Hint
+
+Send the request from the page's own origin.

package/dist/reference/errors/MOSTRA_HYGIENE_RATE_LIMITED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_RATE_LIMITED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_RATE_LIMITED
+
+Too many failed attempts. Severity: error. Phase: hygiene.
+
+## What it means
+
+More than 30 capability tokens failed for this artifact within a minute, so the gateway refuses every token for it, valid ones included, until the minute has passed. A guess can't succeed while the limit holds, and only this artifact's links wait. The gateway answers 429 with `Retry-After`.
+
+## How to fix it
+
+Wait, then open the link again. Repeated failures usually come from a mistyped link or a script retrying an old one.
+
+## Hint
+
+Wait for the time in `Retry-After`, then open the link again.

package/dist/reference/errors/MOSTRA_HYGIENE_REQUEST_MALFORMED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_REQUEST_MALFORMED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_REQUEST_MALFORMED
+
+Malformed request. Severity: error. Phase: hygiene.
+
+## What it means
+
+The gateway refused a request it can't interpret safely: a repeated `Host` or `Origin` header, a request target that isn't a path, an encoded `/` or `..` that would leave the served tree, a body that isn't valid JSON, or a header with control characters. It answers 400 rather than guess.
+
+## How to fix it
+
+Send a single request with one `Host` header and a plain path. Browsers always do; this usually means a hand-written client or a probe.
+
+## Hint
+
+Send one well-formed HTTP request with a path that starts with `/`.

package/dist/reference/errors/MOSTRA_HYGIENE_SCOPE_DENIED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_SCOPE_DENIED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_SCOPE_DENIED
+
+Not allowed by this link. Severity: error. Phase: hygiene.
+
+## What it means
+
+The session's link doesn't carry the scope this request needs: `draft` to save answers, `submit` to submit, `review` to comment, and `action:*`, `action:<export>` or `action:<module path>#<export>` to run a server function. A view-and-comment link, for example, can't submit or run an action. The gateway answers 403.
+
+## How to fix it
+
+Mint a link with the scopes the viewer needs, such as `view/url` with `scopes: ["view", "draft", "submit"]`. Without `scopes`, a link carries every scope.
+
+## Hint
+
+Open a link minted with this scope (`view/url` with `scopes`).

package/dist/reference/errors/MOSTRA_HYGIENE_SESSION_CONFLICT.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_SESSION_CONFLICT
+severity: warning
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_SESSION_CONFLICT
+
+Another link is already open for this artifact. Severity: warning. Phase: hygiene.
+
+## What it means
+
+This browser already has a live session for the artifact from a different link. Opening a link never silently replaces it, because a page elsewhere could send the viewer to its own, narrower link and take over their tabs (D98). The shell shows both links' access and lets the viewer choose; the answer is 409 with `current` and `offered`.
+
+## How to fix it
+
+In the shell, choose the link to keep. A client exchanging tokens itself sends `replace: true` to replace the session.
+
+## Hint
+
+Choose which link to keep; send `replace: true` to use the new one.

package/dist/reference/errors/MOSTRA_HYGIENE_SESSION_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_SESSION_MISSING
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_SESSION_MISSING
+
+No session. Severity: error. Phase: hygiene.
+
+## What it means
+
+The request carried no valid session for this origin. Sessions start when a capability link is opened: the shell exchanges the link's token for a session cookie, and gives the artifact frame a single-use ticket for its own. A session issued for another origin never counts, because every port of the host shares the browser's cookies. The gateway answers 401.
+
+## How to fix it
+
+Open the full capability link, including the part after `#`. A bookmark of the page without it works while the browser keeps the session cookie (400 days).
+
+## Hint
+
+Open the artifact's capability link again to start a session.

package/dist/reference/errors/MOSTRA_HYGIENE_TOKEN_INVALID.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_TOKEN_INVALID
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_TOKEN_INVALID
+
+Unknown capability token. Severity: error. Phase: hygiene.
+
+## What it means
+
+The capability token or frame ticket matched nothing in this home: it was mistyped, cut short, belongs to another home or artifact, or the ticket was already used or expired (tickets last 60 seconds and work once). Over the host protocol, the token ID named in `view/revoke` or `view/rotate` doesn't exist. The gateway answers 401, and failed attempts count towards the rate limit.
+
+## How to fix it
+
+Copy the whole link again. An agent or host mints a fresh one with `view/url`; the shell gets a new frame ticket by reloading.
+
+## Hint
+
+Use the complete capability link Mostra gave you, or mint a new one with `view/url`.

package/dist/reference/errors/MOSTRA_HYGIENE_TOKEN_REVOKED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HYGIENE_TOKEN_REVOKED
+severity: error
+phase: hygiene
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HYGIENE_TOKEN_REVOKED
+
+Link revoked or expired. Severity: error. Phase: hygiene.
+
+## What it means
+
+The capability link was revoked (`view/revoke`), replaced (`view/rotate`), or reached the end of its `ttl`. Every session started from it ends too. The gateway answers 410. Local links have no expiry unless one was asked for.
+
+## How to fix it
+
+Get a new link from whoever shared this one. An agent mints it with `view/url`, or rotates the old one with `view/rotate`, and shares the new URL.
+
+## Hint
+
+Ask for a new link: `view/url` mints one, or `view/rotate` replaces this one.

package/dist/reference/errors/MOSTRA_LIVE_SOURCE_FAILED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_LIVE_SOURCE_FAILED
+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_LIVE_SOURCE_FAILED
+
+Live source failed. Severity: error. Phase: runtime.
+
+## What it means
+
+A live source's `load` or `stream` threw, or its value was outside the serializable types. Pages keep showing the last good value with `useLive`'s `error` set, and the producer tries again on its schedule (FAILURE_MODEL §6).
+
+## How to fix it
+
+Fix the producer in `live.ts`, or catch transient failures there and return the previous value.
+
+## Hint
+
+Read the message, fix the live source's loader or stream, and publish again; the last good value stays meanwhile.

package/dist/reference/errors/MOSTRA_LIVE_TOO_LARGE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_LIVE_TOO_LARGE
+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_LIVE_TOO_LARGE
+
+Live value too large. Severity: error. Phase: runtime.
+
+## What it means
+
+A live value, pushed or produced, is over 4 MiB once serialized (DATA_MODEL §5). It is refused and the last good value stays.
+
+## How to fix it
+
+Send a smaller window of the data, or split it across several live sources. For high-rate series, push single points in append mode and let the page keep the window.
+
+## Hint
+
+Push or produce a smaller value: at most 4 MiB serialized.

package/dist/reference/errors/MOSTRA_MANIFEST_INVALID.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_MANIFEST_INVALID
+severity: error
+phase: manifest
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_MANIFEST_INVALID
+
+Manifest value is invalid. Severity: error. Phase: manifest.
+
+## What it means
+
+The manifest was read, but a field has a value the manifest doesn't allow: a missing `title`, a wrong type, an `id` that isn't an artifact ID (`art_` followed by a ULID), a `mode` this runtime doesn't build (`spa` is the only one), or frontmatter that isn't valid YAML. The message names the field and what was expected.
+
+## How to fix it
+
+Correct the field the message names. Leave `id` out to let Mostra bind the artifact to its source path at first publish, or keep the `id` that `mostra new` wrote. Every field except `title` is optional.
+
+## Hint
+
+Fix the manifest field named in the message so it matches the manifest's documented shape.

package/dist/reference/errors/MOSTRA_MANIFEST_NOT_LITERAL.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_MANIFEST_NOT_LITERAL
+severity: error
+phase: manifest
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_MANIFEST_NOT_LITERAL
+
+Manifest isn't a literal. Severity: error. Phase: manifest.
+
+## What it means
+
+Mostra reads an artifact's manifest without running its code: the `export const artifact = defineArtifact({...})` in a TSX entry, or the frontmatter of an MDX entry. It reports this code when the exported `artifact` isn't a `defineArtifact(...)` call with one object literal, or when a value inside it needs evaluation (an identifier, a function call, a spread, a computed key, a template literal with a placeholder). The location points at the first such value.
+
+## How to fix it
+
+Replace the value with the literal it stands for, for example `title: "Q3 review"` instead of `title: TITLE`. Keep computed values in the page code, where they can use anything. `as const` and `satisfies` on the object are fine.
+
+## Hint
+
+Write the manifest as plain values: strings, numbers, booleans, null, arrays and objects, with no variables, calls, spreads or computed keys.

package/dist/reference/errors/MOSTRA_MANIFEST_UNKNOWN_KEY.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_MANIFEST_UNKNOWN_KEY
+severity: warning
+phase: manifest
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_MANIFEST_UNKNOWN_KEY
+
+Unknown manifest key. Severity: warning. Phase: manifest.
+
+## What it means
+
+The manifest has a key this runtime doesn't know. Mostra ignores it, so manifests written for a newer release still publish, but a misspelled key (`familly`, `decription`) silently has no effect.
+
+## How to fix it
+
+Check the key against the manifest fields (`id`, `title`, `description`, `family`, `links`, `mode`, `submission`, `kit`, `terminals`, `demos`, `limits`, `verify`) and fix the spelling, or remove it.
+
+## Hint
+
+Remove the key or correct its spelling; a newer Mostra may support it.

package/dist/reference/errors/MOSTRA_NETWORK_EXTERNAL_FAILED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_NETWORK_EXTERNAL_FAILED
+severity: warning
+phase: network
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_NETWORK_EXTERNAL_FAILED
+
+Request to another origin failed. Severity: warning. Phase: network.
+
+## What it means
+
+A request the page made to another origin failed or answered 4xx or 5xx. It may be the environment (no network, a service that is down, a request the service refuses from this origin) rather than the code, so it is a warning.
+
+## How to fix it
+
+Check the URL and the service. If the page depends on it, show a fallback when it fails.
+
+## Hint
+
+A request to another origin failed while verify ran; check the URL and whether that service was reachable.

package/dist/reference/errors/MOSTRA_NETWORK_REQUEST_FAILED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_NETWORK_REQUEST_FAILED
+severity: error
+phase: network
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_NETWORK_REQUEST_FAILED
+
+Request for the page's own resource failed. Severity: error. Phase: network.
+
+## What it means
+
+A resource the page loaded from the artifact's own origin (the document, a script, a style, an image, a font, or a fetch by artifact code) failed or answered 4xx or 5xx. Requests the browser makes on its own, such as `/favicon.ico`, and Mostra's own protocol aren't counted.
+
+## How to fix it
+
+Put the file in `public/` (served at the root) or import it from the code so the build includes it, and check the path's spelling.
+
+## Hint
+
+Check the path: a file the page loads from the artifact itself failed to load.

package/dist/reference/errors/MOSTRA_PLATFORM_UNSUPPORTED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_PLATFORM_UNSUPPORTED
+severity: error
+phase: platform
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_PLATFORM_UNSUPPORTED
+
+Unsupported platform. Severity: error. Phase: platform.
+
+## What it means
+
+Mostra 1.0 runs on macOS and Linux, on x64 and arm64. On any other operating system or architecture, Windows included, every entry point stops with this code before it creates or changes anything, because the process model, sockets and storage are built and tested only on those platforms. The message names the platform that was detected.
+
+## How to fix it
+
+Run Mostra on a macOS or Linux machine with an x64 or arm64 processor. Windows support is planned for a release after 1.0.
+
+## Hint
+
+Run Mostra on macOS or Linux, on an x64 or arm64 machine.

package/dist/reference/errors/MOSTRA_PUBLISH_ID_CONFLICT.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_PUBLISH_ID_CONFLICT
+severity: error
+phase: publish
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_PUBLISH_ID_CONFLICT
+
+Artifact ID claimed by two sources. Severity: error. Phase: publish.
+
+## What it means
+
+An artifact's `id` names exactly one source. Mostra reports this code when a manifest claims an `id` that is already bound to another source path whose entry still claims it, which usually means a directory was copied. A source that moved, so that the old path no longer claims the `id`, is rebound instead. The message names both paths.
+
+## How to fix it
+
+Decide which source is the artifact. In the other one, remove the `id` from the manifest (it is then bound to its own path at its first publish) or replace it with a new ID from `mostra new`.
+
+## Hint
+
+Give one of the two sources a different `id`, or delete the `id` line from the copy so it becomes a new artifact.

package/dist/reference/errors/MOSTRA_PUBLISH_SOURCE_CHANGED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_PUBLISH_SOURCE_CHANGED
+severity: error
+phase: publish
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_PUBLISH_SOURCE_CHANGED
+
+Source changed during the publish. Severity: error. Phase: publish.
+
+## What it means
+
+Publishing reads the entry's manifest twice: once to find the artifact, and again from the snapshot it builds. Mostra reports this code when the two disagree about which artifact the source is, because the manifest `id` or the source's binding changed while the publish ran, for example when an editor saved the entry mid-publish or another publish rebound the path. Nothing was published.
+
+## How to fix it
+
+Wait until the files are saved and nothing else is publishing the same source, then publish again. If the manifest `id` was changed on purpose, the next publish uses the new one.
+
+## Hint
+
+Publish again once the artifact's files have stopped changing.

package/dist/reference/errors/MOSTRA_PUBLISH_VERIFY_FAILED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_PUBLISH_VERIFY_FAILED
+severity: error
+phase: publish
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_PUBLISH_VERIFY_FAILED
+
+Verify found errors. Severity: error. Phase: publish.
+
+## What it means
+
+Publish runs verify (or reuses the verdict it cached for the same source and environment) and refuses when the verdict has errors (D41). The message lists their codes. Nothing was published. With `--force`, publish goes ahead and records the codes in the version, where hosts read them; a source that doesn't build can't be published either way.
+
+## How to fix it
+
+Fix the errors `mostra verify` reports and publish again, or publish with `--force` if the version must ship as it is.
+
+## Hint
+
+Run `mostra verify` to see the errors and fix them, or publish with `--force` to record them in the version.

package/dist/reference/errors/MOSTRA_REGRESSION_ACTION_REMOVED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_REGRESSION_ACTION_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_ACTION_REMOVED
+
+Server function gone since the last passing version. Severity: warning. Phase: contract.
+
+## What it means
+
+A `"use server"` export the last passing version had is gone. Pages of the older version still call it while they are open, and keyed runs started by it can't be started again.
+
+## 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 server function and this source doesn't; one removed on purpose needs nothing more.