@mostra/cli 0.0.0-placeholder → 0.1.0

package/dist/reference/errors/MOSTRA_VERIFY_NO_BASELINE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_NO_BASELINE
+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_NO_BASELINE
+
+No earlier passing version. Severity: hint. Phase: regression.
+
+## What it means
+
+Verify compares a source with the newest published version of its artifact whose verdict passed. This artifact has none yet (it is new, or every earlier version was published with `--force`), so no regression stage ran.
+
+## How to fix it
+
+Nothing is required.
+
+## Hint
+
+Nothing to fix: the next version will be compared with this one once it is published.

package/dist/reference/errors/MOSTRA_VERIFY_SECRET_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_SECRET_MISSING
+severity: warning
+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_SECRET_MISSING
+
+Secret missing during verify. Severity: warning. Phase: runtime.
+
+## What it means
+
+Server code asked for a secret (`secret()`) that neither the host, the artifact's secrets nor the home's hold, while verify ran it. Secrets are part of the environment, so verify reports this as a warning rather than an error.
+
+## How to fix it
+
+Run `mostra secret set <NAME>` (for the artifact or the home) with the value the code needs, then verify again.
+
+## Hint
+
+Set the secret with `mostra secret set <NAME>` if the artifact needs it; verify reports it as the environment, not the code.

package/dist/reference/errors/MOSTRA_VERIFY_SKIP_CONSEQUENCE.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_SKIP_CONSEQUENCE
+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_SKIP_CONSEQUENCE
+
+Page reaction to a skipped action. Severity: hint. Phase: smoke.
+
+## What it means
+
+After verify refused a server function that doesn't check `dryRun()`, the page reported an error: an unhandled rejection, an error a boundary caught, or a console error while it settled. It follows from verify's synthetic refusal, not from a defect a viewer would meet, so it is reported as a hint naming the skipped action.
+
+## How to fix it
+
+Nothing is required. To let verify see the action's real result, opt it into the smoke test with `dryRun()`.
+
+## Hint
+
+Nothing to fix: this followed from verify skipping an action, which a viewer's page never meets.

package/dist/reference/errors/MOSTRA_VERIFY_TIMEOUT.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_VERIFY_TIMEOUT
+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_TIMEOUT
+
+Verify ran out of time. Severity: error. Phase: runtime.
+
+## What it means
+
+Verify allows 120 s for everything after the build: booting the sandbox, rendering each viewport, the smoke test and the regression stage. This run went past it, so its verdict is partial: the message names the stage it reached. A partial run can't vouch for the page, so this is an error, and the verdict isn't cached.
+
+## How to fix it
+
+Look for work the page does at load that takes long (large data, long animations, requests that never answer) and defer it, then verify again. On a heavily loaded machine, verifying again may be enough.
+
+## Hint
+
+Make the page render without waiting on slow work at load, then verify again.

package/dist/reference/telemetry.md

@@ -0,0 +1,82 @@
+# Telemetry
+
+The standalone `mostra` CLI can send anonymous usage events, so we can see which commands work,
+which fail, and which agents people use Mostra with. This page lists every event and every field.
+If it isn't on this page, Mostra doesn't send it.
+
+## What Mostra never sends
+
+- Artifact content, source code, answers or submissions
+- File paths, project or artifact names, URLs, capability links or tokens
+- Names, emails, usernames, hostnames or account identifiers
+- Your time zone, locale or anything typed on the command line
+
+The collector doesn't store IP addresses.
+
+## When it is on
+
+- **In the EU, the EEA, the UK, Switzerland and nearby countries, and when the time zone is UTC or
+  unknown,** Mostra asks first. Nothing is sent until you answer yes or run `mostra telemetry on`.
+  Pressing Enter or not answering means no. Where no one can answer (CI, an agent's shell, `--json`),
+  Mostra doesn't ask and sends nothing. Mostra checks the time zone on your machine and never
+  sends it.
+- **Elsewhere,** telemetry is on by default. Mostra prints a notice once before it sends anything.
+
+## When it is off
+
+- `mostra telemetry off`, `MOSTRA_TELEMETRY=0` or `DO_NOT_TRACK=1`. Any of these wins over every
+  setting that turns it on.
+- Embedded use never sends anything: the TypeScript SDK, the Rust crate, an instance a host starts
+  (`mostra host`) and any home a host has configured.
+- A build without a telemetry endpoint sends nothing.
+
+`mostra telemetry status` shows whether telemetry is on, why, your install ID and how many
+events are waiting to be sent. `MOSTRA_TELEMETRY_DEBUG=1` prints every event to stderr exactly as
+it would be sent, and sends nothing.
+
+## The install ID
+
+On the first run that sends, Mostra creates a random ID and stores it in its config directory
+(`${XDG_CONFIG_HOME:-~/.config}/mostra`, or `MOSTRA_CONFIG_DIR`). It is never derived from your
+machine or from you, and it is the only value Mostra keeps between events. It lets us count
+installs. Turning telemetry off deletes it and any unsent events; turning it on again creates a new
+one.
+
+## Fields on every event
+
+| Field | Example | Why |
+|---|---|---|
+| `schema` | `1` | The version of this list |
+| `event` | `cli.command` | Which event |
+| `at` | `2026-11-10T14:05:00Z` | When, to the minute |
+| `installId` | a random UUID | Count installs without knowing who you are |
+| `version` | `1.0.0` | Know which versions fail |
+| `os`, `arch` | `darwin`, `arm64` | Platform support |
+| `node` | `22` | Which Node versions to support |
+| `harness` | `claude-code`, `codex`, `gemini-cli`, `opencode`, `cursor`, `other`, `none` | Which agents to work with next |
+| `ci` | `false` | Separate CI from people |
+| `consent` | `explicit` or `default` | Whether you said yes or it was on by default |
+
+## Events
+
+| Event | Sent when | Its own fields |
+|---|---|---|
+| `cli.first_run` | The install ID is created | none |
+| `cli.command` | A command finishes | `command` (its name, never its arguments), `exit` (exit code), `duration` (`<1s`, `1-5s`, `5-30s`, `30s-2m`, `2-10m`, `>10m`), `json` (whether `--json` was used), `error` (the diagnostic code, when it failed) |
+| `verify.result` | `mostra verify` finishes | `status` (`pass` or `fail`), `codes` (up to 50 diagnostic codes, never their messages), `codesTruncated` |
+| `publish.done` | A version is published | `reused`, `forced` |
+| `share.done` | A share starts | `kind`: `tailnet`, `funnel`, `cloudflare` or `remote` |
+| `mcp.session` | An MCP client connects to `mostra mcp` | `client` (a known agent's ID, or `other`), `clientVersion` (known agents only) |
+
+## How it is sent
+
+Events wait in a small queue in the config directory and are sent in the background after a
+command finishes, at most 100 per request. No command waits for the network, and the network
+never changes a command's result. Events that can't be sent within 7 days are dropped.
+
+## Retention and your rights
+
+We keep raw events for 12 months, then only aggregated counts. To have your events deleted, send
+your install ID (from `mostra telemetry status`) to the privacy contact in our privacy policy.
+
+Changes to this list are announced in the changelog before they ship.

package/dist/run-D1gRM6Bm.js

@@ -0,0 +1,2 @@
+import { t as run } from "./run-Du266XjI.js";
+export { run };