@mostra/cli 0.1.0 → 0.3.0

package/dist/bin.js

@@ -54,7 +54,7 @@ async function start() {
 		},
 		stderrTty: process.stderr.isTTY === true,
 		terminal: process.stdin.isTTY === true || process.stdout.isTTY === true || process.stderr.isTTY === true
-	}) ?? await (await import("./run-D1gRM6Bm.js")).run({
+	}) ?? await (await import("./run-CMyjOm0Q.js")).run({
 		argv: process.argv.slice(2),
 		env: process.env,
 		cwd: process.cwd(),

package/dist/index.js

@@ -1,3 +1,3 @@
-import { a as COMMANDS, i as referenceMarkdown, n as commandDefinition, r as commandHelp, t as run } from "./run-Du266XjI.js";
+import { a as COMMANDS, i as referenceMarkdown, n as commandDefinition, r as commandHelp, t as run } from "./run-BJaRnz-Q.js";
 import { n as exitCodeFor, t as EXIT } from "./exit-CBIf8nAU.js";
 export { COMMANDS, EXIT, commandDefinition, commandHelp, exitCodeFor, referenceMarkdown, run };

package/dist/reference/cli.md

@@ -798,7 +798,7 @@ Exit codes:
   3  environment error (no runtime, browser or socket; the home; an unsupported platform)
 
 Example:
-  mostra host --home ~/.jcode/mostra
+  mostra host --home ~/.my-host/mostra
 ```
 
 ## mostra docs

package/dist/reference/diagnostics.json

@@ -378,6 +378,15 @@
       "explanation": "Mostra runs on its own runtime bundle, found in the local cache, beside the installed package or at `MOSTRA_BUNDLE`. None was there, and no download could start: Mostra is offline (`MOSTRA_OFFLINE`), this build of the package pins no bundle for this platform, or the platform has none.",
       "fix": "Run the command once with network access and without `MOSTRA_OFFLINE`, so the pinned bundle is fetched and cached; later runs work offline. On a machine without network access, extract the release's archive for the platform and set `MOSTRA_BUNDLE` to its directory. A development checkout uses its own built runtime instead."
     },
+    {
+      "code": "MOSTRA_ENV_HELPER_MISSING",
+      "severity": "error",
+      "phase": "platform",
+      "title": "Windows helper missing",
+      "hint": "Reinstall Mostra, or set `MOSTRA_WIN_HELPER` to its `mostra-win.exe`.",
+      "explanation": "On Windows the runtime runs `mostra-win.exe`, a helper that ships with it, for what Node.js can't do there: owner-only access to the home, the home's control pipe, and every child process in a Job Object. The runtime looked for it at `MOSTRA_WIN_HELPER`, in its runtime bundle, and in a development checkout's Cargo build, and found none, so it stopped before touching the home.",
+      "fix": "Reinstall Mostra so the runtime bundle is complete. In a development checkout, build the helper with `cargo build -p mostra-win`. A custom layout can point the runtime at the helper with `MOSTRA_WIN_HELPER`."
+    },
     {
       "code": "MOSTRA_ENV_NODE_UNSUPPORTED",
       "severity": "error",
@@ -621,6 +630,15 @@
       "explanation": "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.",
       "fix": "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."
     },
+    {
+      "code": "MOSTRA_HOST_IDENTITY_UNAVAILABLE",
+      "severity": "error",
+      "phase": "host",
+      "title": "The host that identifies viewers didn't answer",
+      "hint": "Start the host that serves this home's identity port, then open the link again.",
+      "explanation": "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.",
+      "fix": "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: []`)."
+    },
     {
       "code": "MOSTRA_HOST_INITIALIZE_ORDER",
       "severity": "error",
@@ -924,8 +942,8 @@
       "phase": "platform",
       "title": "Unsupported platform",
       "hint": "Run Mostra on macOS or Linux, on an x64 or arm64 machine.",
-      "explanation": "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.",
-      "fix": "Run Mostra on a macOS or Linux machine with an x64 or arm64 processor. Windows support is planned for a release after 1.0."
+      "explanation": "Mostra runs on macOS and Linux, on x64 and arm64. On any other operating system or architecture every entry point stops with this code before it creates or changes anything, because the process model, the control endpoint and storage are built and tested only there. Windows on x64 and arm64 is being added and runs only in Mostra's own development builds until it is complete; a release stops there with this code too. The message names the platform that was detected.",
+      "fix": "Run Mostra on a macOS or Linux machine with an x64 or arm64 processor. Windows support arrives in a 1.0 release."
     },
     {
       "code": "MOSTRA_PUBLISH_ID_CONFLICT",

package/dist/reference/errors/MOSTRA_ENV_HELPER_MISSING.md

@@ -0,0 +1,23 @@
+---
+code: MOSTRA_ENV_HELPER_MISSING
+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_ENV_HELPER_MISSING
+
+Windows helper missing. Severity: error. Phase: platform.
+
+## What it means
+
+On Windows the runtime runs `mostra-win.exe`, a helper that ships with it, for what Node.js can't do there: owner-only access to the home, the home's control pipe, and every child process in a Job Object. The runtime looked for it at `MOSTRA_WIN_HELPER`, in its runtime bundle, and in a development checkout's Cargo build, and found none, so it stopped before touching the home.
+
+## How to fix it
+
+Reinstall Mostra so the runtime bundle is complete. In a development checkout, build the helper with `cargo build -p mostra-win`. A custom layout can point the runtime at the helper with `MOSTRA_WIN_HELPER`.
+
+## Hint
+
+Reinstall Mostra, or set `MOSTRA_WIN_HELPER` to its `mostra-win.exe`.

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_PLATFORM_UNSUPPORTED.md

@@ -12,11 +12,11 @@ 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.
+Mostra runs on macOS and Linux, on x64 and arm64. On any other operating system or architecture every entry point stops with this code before it creates or changes anything, because the process model, the control endpoint and storage are built and tested only there. Windows on x64 and arm64 is being added and runs only in Mostra's own development builds until it is complete; a release stops there with this code too. 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.
+Run Mostra on a macOS or Linux machine with an x64 or arm64 processor. Windows support arrives in a 1.0 release.
 
 ## Hint
 

package/dist/{run-Du266XjI.js → run-BJaRnz-Q.js}

@@ -1802,7 +1802,7 @@ const hostCommand = defineCommand({
 		topic: "cli"
 	},
 	exits: [],
-	example: "host --home ~/.jcode/mostra",
+	example: "host --home ~/.my-host/mostra",
 	local: true,
 	quiet: true,
 	readsStdin: true,
@@ -3821,4 +3821,4 @@ async function runRuntime(io, args, stdio) {
 //#endregion
 export { COMMANDS as a, referenceMarkdown as i, commandDefinition as n, commandHelp as r, run as t };
 
-//# sourceMappingURL=run-Du266XjI.js.map
+//# sourceMappingURL=run-BJaRnz-Q.js.map