@mostra/cli 0.0.0-stage → 0.2.0

package/dist/reference/errors/MOSTRA_FIELD_TOO_LARGE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_FIELD_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_FIELD_TOO_LARGE
+
+Field value too large. Severity: error. Phase: runtime.
+
+## What it means
+
+A field value is at most 1 MiB of JSON and a draft or artifact state at most 16 MiB in all (DATA_MODEL §5). This write would pass one of those limits, so Mostra refused it whole: nothing was truncated, and the page keeps the value locally.
+
+## How to fix it
+
+Split the value across several fields under one dotted prefix (`report.part1`, `report.part2`); they nest again in results.
+
+## Hint
+
+Split large data across fields, keeping each value under 1 MiB and the whole document under 16 MiB.

package/dist/reference/errors/MOSTRA_FIELD_UNBOUND.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_FIELD_UNBOUND
+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_FIELD_UNBOUND
+
+Input not bound to a field. Severity: hint. Phase: smoke.
+
+## What it means
+
+Verify's smoke test typed into an input and the page saved nothing: the input isn't bound to a field, so what a viewer types there is lost on reload and isn't part of a submission. A search box or a filter may be meant that way.
+
+## How to fix it
+
+Use `const [value, setValue] = useField("<id>", "")` for the input's value, or leave it if it isn't meant to persist.
+
+## Hint
+
+Bind the input with `useField` (or a kit input with an `id`) if its value should be saved and submitted.

package/dist/reference/errors/MOSTRA_HOME_DISK_FULL.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_DISK_FULL
+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_HOME_DISK_FULL
+
+Disk full. Severity: error. Phase: host.
+
+## What it means
+
+A ledger write failed because the disk holding the home is full. The transaction was rolled back, so nothing partial was saved and nothing that was acknowledged earlier is lost. Viewers keep unsaved edits in their browser until a retry succeeds.
+
+## How to fix it
+
+Free space on that disk (`mostra gc` removes unreferenced versions; build caches can be deleted), then retry the operation. Retries with the same request or mutation ID are safe.
+
+## Hint
+
+Free space on the disk that holds the Mostra home, then retry.

package/dist/reference/errors/MOSTRA_HOME_GC_INCOMPLETE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_GC_INCOMPLETE
+severity: warning
+phase: host
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HOME_GC_INCOMPLETE
+
+gc didn't finish a step. Severity: warning. Phase: host.
+
+## What it means
+
+`mostra gc` removes what nothing references in steps: version files, source snapshots, lock layouts, the package store, verify's caches and, when asked, events. One step failed (the message names it and why), so it left that step's files in place. Everything an earlier step removed is listed in the result, and the versions it collected stay collected. The home is consistent: what gc left is still recorded as there.
+
+## How to fix it
+
+Run `mostra gc` again; a failure that repeats names its cause in the message (for example, a file the user can't remove).
+
+## Hint
+
+Run `mostra gc` again: what this run removed is in its result, and the next run picks up what it left.

package/dist/reference/errors/MOSTRA_HOME_GONE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_GONE
+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_HOME_GONE
+
+Home directory removed. Severity: error. Phase: host.
+
+## What it means
+
+The instance's home directory disappeared or was replaced while the instance was running. Writing anywhere else could split the home's data, so the instance stops accepting requests, stops its child processes and exits.
+
+## How to fix it
+
+Put the home back (or choose a new one with `--home` or `MOSTRA_HOME`) and start Mostra again. Clients reconnect and retry their requests by ID.
+
+## Hint
+
+Restore or recreate the home directory, then start Mostra again.

package/dist/reference/errors/MOSTRA_HOME_INTEGRITY.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_INTEGRITY
+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_HOME_INTEGRITY
+
+Stored version or file damaged. Severity: error. Phase: host.
+
+## What it means
+
+Mostra checks stored versions, source snapshots and blobs against their recorded content digests before using them. This code means a stored object is missing or its content changed after it was written, for example after a disk error or a manual edit inside the home. The message names the object.
+
+## How to fix it
+
+Leave files inside the home unchanged. To repair a version, publish the same source again: Mostra rebuilds the version's directory and puts it back under the same version ID, and the artifact keeps its version number. If the source has changed since, the publish makes a new version and the damaged one stays as it is; its source snapshot in the home holds the original files. `mostra doctor` lists other damaged objects.
+
+## Hint
+
+Publish the version's source again to rebuild a damaged version in place, and run `mostra doctor` for other damaged objects.

package/dist/reference/errors/MOSTRA_HOME_LEDGER_UNREADABLE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_LEDGER_UNREADABLE
+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_HOME_LEDGER_UNREADABLE
+
+Ledger can't be read. Severity: error. Phase: host.
+
+## What it means
+
+The ledger (`store/ledger.sqlite` in the home) holds drafts, submissions, events and the rest of the home's interaction data. Mostra reports this code when the file can't be opened, isn't a SQLite database, isn't a Mostra ledger, or fails SQLite's integrity check. Mostra never replaces an existing ledger with an empty one.
+
+## How to fix it
+
+Stop every Mostra process for this home. Copy `store/ledger.sqlite` somewhere safe, then restore the newest `store/ledger.sqlite.bak-<from>-<to>` in its place, or move the damaged file aside to start an empty ledger. Versions, sources and blobs in the home are untouched either way.
+
+## Hint
+
+Restore the ledger from the latest `ledger.sqlite.bak-*` backup in the home's `store/` directory, or move the damaged file aside.

package/dist/reference/errors/MOSTRA_HOME_LOCKED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_LOCKED
+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_HOME_LOCKED
+
+Home in use by another instance. Severity: error. Phase: host.
+
+## What it means
+
+One Mostra instance owns a home at a time. It holds an exclusive lock on the home's ledger, and the operating system releases that lock when the process exits. Mostra reports this code in two cases: `mostra host` was started for a home another instance already owns, or a starter found the owner but couldn't reach its control socket. The message names the owner's process ID.
+
+## How to fix it
+
+To share the running instance, attach to it: start the client with the same home (`MOSTRA_HOME` or `--home`) instead of starting a second instance. To replace it, stop it with `mostra daemon stop`, or end the process named in the message, and start again. A host that needs its own instance gives it its own home.
+
+## Hint
+
+Use the instance that already owns this home, or stop it (`mostra daemon stop`, or end the process named in the message) and start again.

package/dist/reference/errors/MOSTRA_HOME_MISMATCH.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_MISMATCH
+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_HOME_MISMATCH
+
+Instance serves a different home. Severity: error. Phase: host.
+
+## What it means
+
+A client sent `home.path` in `mostra/initialize`, and it names a different home from the one the instance locked at start-up. The home is chosen when the instance starts (`--home`, then `MOSTRA_HOME`, then the platform default), so `home.path` is a check: it stops a client from writing to a home it didn't mean.
+
+## How to fix it
+
+Start the instance with `--home` set to the home the client expects, or connect to the socket of the instance that serves it. Leave `home.path` out to accept whichever home the instance serves.
+
+## Hint
+
+Connect to the instance for the home you expect, or start it with `--home` set to that home.

package/dist/reference/errors/MOSTRA_HOME_NOT_ALWAYS_ON.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_NOT_ALWAYS_ON
+severity: warning
+phase: host
+---
+
+<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
+
+# MOSTRA_HOME_NOT_ALWAYS_ON
+
+Long-lived artifacts without an always-on daemon. Severity: warning. Phase: host.
+
+## What it means
+
+The home has artifacts with submission policy `none`, which are meant to stay open (dashboards, task managers, D63), but no login service runs its daemon. Without one, the daemon exits after 30 idle minutes and their links stop answering until a command starts it again.
+
+## How to fix it
+
+Run `mostra daemon install`. It registers a launchd or systemd user service that keeps the home's daemon running; `mostra daemon uninstall` removes it.
+
+## Hint
+
+Run `mostra daemon install` so the home's daemon runs as a login service and these artifacts answer at any hour.

package/dist/reference/errors/MOSTRA_HOME_NOT_OWNED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_NOT_OWNED
+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_HOME_NOT_OWNED
+
+Directory not owned by you. Severity: error. Phase: host.
+
+## What it means
+
+Mostra keeps secrets, answers and its ledger in the home, and its control socket in a runtime directory, so it uses only directories that belong to the user running it. It reports this code when the home or the runtime directory is owned by another user, or when the path exists but isn't a directory. Mostra changes nothing in that case.
+
+## How to fix it
+
+Point Mostra at a directory you own: `--home <dir>` or `MOSTRA_HOME` for the home, `MOSTRA_RUNTIME_DIR` for the runtime directory. If the directory should be yours, change its owner with `chown`. Mostra tightens a directory you own to mode 0700 by itself.
+
+## Hint
+
+Choose a home you own with `--home` or `MOSTRA_HOME`, or give the directory named in the message back to your user with `chown`.

package/dist/reference/errors/MOSTRA_HOME_SOCKET_TOO_LONG.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_SOCKET_TOO_LONG
+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_HOME_SOCKET_TOO_LONG
+
+Control socket path too long. Severity: error. Phase: host.
+
+## What it means
+
+Clients reach an instance through a Unix socket in a per-user runtime directory. The operating system limits a socket path to 103 bytes on macOS and 107 on Linux, and the path Mostra computed is longer, usually because the home directory's path is long. Mostra stops instead of using a different place that clients couldn't find.
+
+## How to fix it
+
+Set `MOSTRA_RUNTIME_DIR` to a short directory you own, such as `/tmp/mostra-$USER`, in the environment of every Mostra client and host that uses this home. Mostra creates it with mode 0700 and re-creates its socket if a temporary-file cleanup removes it.
+
+## Hint
+
+Set `MOSTRA_RUNTIME_DIR` to a short directory you own, for example `/tmp/mostra-$USER`, and start again.

package/dist/reference/errors/MOSTRA_HOME_TOO_NEW.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOME_TOO_NEW
+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_HOME_TOO_NEW
+
+Home written by a newer Mostra. Severity: error. Phase: host.
+
+## What it means
+
+A newer Mostra migrated this home's ledger to a schema version this runtime doesn't know. Reading it could misinterpret or lose data, so this runtime refuses to open it. The message names the schema version and the release that wrote it.
+
+## How to fix it
+
+Upgrade the runtime (or the host or CLI that bundles it) to at least the release named in the message. Mostra never migrates a ledger backwards; to keep an older release, give it a separate home with `--home` or `MOSTRA_HOME`.
+
+## Hint
+
+Run a Mostra release at least as new as the one named in the message, or use another home with `--home`.

package/dist/reference/errors/MOSTRA_HOST_CONNECTION_CLOSED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_CONNECTION_CLOSED
+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_CONNECTION_CLOSED
+
+Connection closed. Severity: error. Phase: host.
+
+## What it means
+
+The connection to the other side closed before a response arrived, for example because the instance exited or restarted. The request may or may not have taken effect.
+
+## How to fix it
+
+Reconnect and send `mostra/initialize` again, then retry the request with the same request ID. Mutating methods are idempotent by request ID, so a retry never applies twice.
+
+## Hint
+
+Reconnect, then retry the request with the same request ID.

package/dist/reference/errors/MOSTRA_HOST_CURSOR_COMPACTED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_CURSOR_COMPACTED
+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_CURSOR_COMPACTED
+
+Events compacted. Severity: error. Phase: host.
+
+## What it means
+
+Events before a cursor were compacted on request (`mostra gc --compact-events`, DATA_MODEL §4): an artifact's old events were replaced by one `artifact.compacted` event that summarizes them. A reader asking for events after an earlier cursor would miss some, and Mostra never leaves a silent gap.
+
+## How to fix it
+
+Read again with `after` set to the cursor the message names: the next event is the `artifact.compacted` summary. Rebuild what you track from it and continue as usual.
+
+## Hint
+
+Read from the cursor in the message to receive the compaction summary, then continue from there.

package/dist/reference/errors/MOSTRA_HOST_IDENTITY_UNAVAILABLE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_IDENTITY_UNAVAILABLE
+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_IDENTITY_UNAVAILABLE
+
+The host that identifies viewers didn't answer. Severity: error. Phase: host.
+
+## What it means
+
+A host registered the `identity` port, so it decides who opens this home's links. When a link minted without a viewer was opened, that host failed, didn't answer within 5 seconds, gave an answer its schema refuses, or is expected (it lists `identity` in `HomeConfig.ports`) but not connected. Mostra refuses the link rather than let the session act as someone else.
+
+## How to fix it
+
+Start or reconnect the host, then open the link again. A link minted with `view/url`'s `viewer` names its person itself and never needs the port. To return the home to Mostra's own identity, have the host register without the port and clear its expected ports (`HomeConfig.ports: []`).
+
+## Hint
+
+Start the host that serves this home's identity port, then open the link again.

package/dist/reference/errors/MOSTRA_HOST_INITIALIZE_ORDER.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_INITIALIZE_ORDER
+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_INITIALIZE_ORDER
+
+Initialize first, and only once. Severity: error. Phase: host.
+
+## What it means
+
+Every connection starts with `mostra/initialize`, which agrees the protocol revision and registers the client's ports. The instance received another request before it, or a second `mostra/initialize` on the same connection.
+
+## How to fix it
+
+Send `mostra/initialize` first and wait for its result before any other request. To renegotiate, open a new connection.
+
+## Hint
+
+Send `mostra/initialize` as the first request on the connection, and only once.

package/dist/reference/errors/MOSTRA_HOST_INTERNAL_ERROR.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_INTERNAL_ERROR
+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_INTERNAL_ERROR
+
+Unexpected failure in the instance. Severity: error. Phase: host.
+
+## What it means
+
+The instance failed while handling the request, for a reason that isn't one of its known conditions. Durable state is unaffected: a request is acknowledged only after its ledger transaction commits. The details are in the instance's log (`logs/supervisor.log` in the home), not in the response.
+
+## How to fix it
+
+Retry the request with the same request ID; retries are idempotent. If the failure repeats, report it with the relevant lines of `logs/supervisor.log`.
+
+## Hint
+
+Retry the request with the same request ID; if it fails again, report it with the instance's log.

package/dist/reference/errors/MOSTRA_HOST_INVALID_PARAMS.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_INVALID_PARAMS
+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_INVALID_PARAMS
+
+Invalid method params. Severity: error. Phase: host.
+
+## What it means
+
+The request's `params` don't match the method's published schema: a required field is missing, a value has the wrong type, or a value is outside its allowed range. The message names the first problem found.
+
+## How to fix it
+
+Compare the request with the method's schema in `@mostra/protocol` (or the published JSON Schema) and correct the field named in the message.
+
+## Hint
+
+Fix the params named in the message so they match the method's schema.

package/dist/reference/errors/MOSTRA_HOST_MALFORMED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_MALFORMED
+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_MALFORMED
+
+Malformed protocol message. Severity: error. Phase: host.
+
+## What it means
+
+Every message on a Mostra connection is one line of JSON with one JSON-RPC 2.0 object. This code means a line wasn't valid JSON, wasn't a JSON-RPC 2.0 request or response, or was a batch (a JSON array), which revision `2026-10-10` doesn't accept. A client also reports it when a response doesn't match the method's result schema.
+
+## How to fix it
+
+Encode one request per line with `"jsonrpc": "2.0"`, a `method`, an `id` for requests, and `params` as an object. Send several requests as separate lines instead of a batch.
+
+## Hint
+
+Send each message as one line of JSON holding a single JSON-RPC 2.0 request or notification.

package/dist/reference/errors/MOSTRA_HOST_MESSAGE_TOO_LARGE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_MESSAGE_TOO_LARGE
+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_MESSAGE_TOO_LARGE
+
+Message too large for the protocol. Severity: error. Phase: host.
+
+## What it means
+
+One host-protocol message is one line of JSON, and a line holds at most 64 Mi characters (`MAX_LINE_LENGTH`), so neither side buffers without bound. Mostra checks every message before it writes it: an answer that would be longer is replaced by this error, and a delivery whose envelope would be longer is recorded as undeliverable instead of being sent and retried forever.
+
+## How to fix it
+
+Read less per request (`events/read` with a smaller `limit`, `results/get` for one submission), and keep artifacts' values within the field and document limits.
+
+## Hint
+
+Ask for less at once: a specific submission, fewer events, or smaller values.

package/dist/reference/errors/MOSTRA_HOST_METHOD_UNKNOWN.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_METHOD_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_METHOD_UNKNOWN
+
+Unknown protocol method. Severity: error. Phase: host.
+
+## What it means
+
+The instance doesn't serve the method that was called. Either the name is misspelled, or the client is newer than the instance and calls a method the instance's release doesn't have.
+
+## How to fix it
+
+Check the method name against INTERFACES §6, and against `capabilities.methods` in the `mostra/initialize` result, which lists every method this instance serves. Upgrade the instance if the client needs a newer method.
+
+## Hint
+
+Call only the methods listed in `capabilities.methods` of the `mostra/initialize` result.

package/dist/reference/errors/MOSTRA_HOST_NOTIFICATION_UNSUPPORTED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_NOTIFICATION_UNSUPPORTED
+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_NOTIFICATION_UNSUPPORTED
+
+Notification not accepted. Severity: error. Phase: host.
+
+## What it means
+
+Mostra sends a client only the notifications it listed in `mostra/initialize` (D84). This method would send one the client didn't list, such as `events/notify` for `events/subscribe`.
+
+## How to fix it
+
+Reconnect and initialize with `capabilities: { notifications: ["events/notify"] }`, or poll with `events/read` instead.
+
+## Hint
+
+List the notification in `capabilities.notifications` when you initialize.

package/dist/reference/errors/MOSTRA_HOST_PORT_UNSUPPORTED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_PORT_UNSUPPORTED
+severity: warning
+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_PORT_UNSUPPORTED
+
+Port not supported by this instance. Severity: warning. Phase: host.
+
+## What it means
+
+The client registered a port this instance doesn't call, so registering it has no effect. The port may be reserved for a later release (such as `ai`), or the client may be newer than the instance. The session continues without the port, and Mostra uses its standalone behavior instead.
+
+## How to fix it
+
+Register only the ports listed in `capabilities.ports` of the `mostra/initialize` result. If the host needs the port, upgrade the instance to a release that supports it.
+
+## Hint
+
+Leave the port out of `mostra/initialize`, or run a Mostra release that lists it in `capabilities.ports`.

package/dist/reference/errors/MOSTRA_HOST_REQUEST_ID_REUSED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_REQUEST_ID_REUSED
+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_REQUEST_ID_REUSED
+
+A requestId was reused with other parameters. Severity: error. Phase: host.
+
+## What it means
+
+A mutating method recorded its result under this `requestId` for different parameters. Replaying that result would answer a request nobody made (a link for another artifact or with other scopes, another source's publish), so the instance refuses (H-03). Retries with the same parameters still return the recorded result.
+
+## How to fix it
+
+Generate a fresh `requestId` for every new request, and reuse one only to retry the same request after a timeout or a lost connection.
+
+## Hint
+
+Send a new `requestId` for a new request; repeat the exact parameters only to retry one.

package/dist/reference/errors/MOSTRA_HOST_REVISION_UNSUPPORTED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_REVISION_UNSUPPORTED
+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_REVISION_UNSUPPORTED
+
+No common host protocol revision. Severity: error. Phase: host.
+
+## What it means
+
+A client and a Mostra instance agree on a host protocol revision when they connect (`mostra/initialize`). The client offers the revisions it speaks, and the instance picks the newest one it also supports. This code means the two lists have nothing in common, usually because the client and the running daemon come from Mostra releases far apart.
+
+## How to fix it
+
+Restart the daemon so it runs the same release as the client: `mostra daemon restart`. Durable state survives the restart, and open views reconnect. A host that embeds Mostra updates its pinned Mostra runtime or its host library until both support a common revision.
+
+## Hint
+
+Run the client and the instance from the same Mostra release, for example with `mostra daemon restart`.

package/dist/reference/errors/MOSTRA_HOST_SHUTDOWN_REFUSED.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_HOST_SHUTDOWN_REFUSED
+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_SHUTDOWN_REFUSED
+
+Only the spawning host can stop this instance. Severity: error. Phase: host.
+
+## What it means
+
+An instance started by a host over stdio (`mostra host`) lives as long as that host's connection, so only the host may stop it with `mostra/shutdown`. A client that attached through the home's socket asked it to stop. A daemon (`mostra daemon`) accepts `mostra/shutdown` from every attached client (D87).
+
+## How to fix it
+
+Close your own connection when you are done. To stop the instance, stop the host that spawned it, or have the host send `mostra/shutdown` or close its stdio.
+
+## Hint
+
+Ask the host that started this instance to stop it, or end the connection you opened instead.