@mmmbuto/nexuscrew 0.9.0 → 0.9.2

package/CHANGELOG.md

@@ -2,6 +2,97 @@
 
 All notable changes to NexusCrew are tracked here.
 
+## 0.9.2 — 2026-08-16 — "Offered and Then Refused"
+
+Both defects in this release were found by using the product, not by a test —
+and both were invisible to the suite for the same reason: each test exercised
+one piece in isolation, and neither defect exists in isolation.
+
+- **The Desktop engine could be selected but never saved.** It declared
+  `command: 'docker'` — a bare name — while engine validation requires an
+  absolute path, so it appeared in the list and was rejected on save with
+  *"command must be an absolute path"*: a message describing the shape of the
+  value instead of saying the command had not been resolved. The path is now
+  resolved from `PATH` through `realpath`, which matters because validation
+  uses `lstat` and rejects symlinks — and in many installs the first hit on
+  `PATH` is exactly that. Where Docker is absent the fallback makes the
+  refusal say *"not accessible (ENOENT)"*, naming the real cause.
+
+  Installations that already had the engine are **repaired**: the backfill
+  skips what already exists, so fixing the default alone would have changed
+  nothing precisely where the defect was seen. The repair only touches a
+  command that is both non-absolute and still named `docker` — an absolute
+  path, or a command you changed yourself, is left alone.
+
+- **The panel reloaded without pause, leaving no time to interact with it.**
+  A panel behind a login was unusable: the sign-in prompt appeared and the
+  frame remounted before it could be completed. `route` is an array, so it was
+  a new prop on every parent render — and the parent re-renders continuously
+  to poll the fleet. With the array among the effect's dependencies, every
+  render requested a fresh ticket and remounted the iframe. The dependency is
+  now keyed on content, so the panel reopens when the route actually changes
+  and not otherwise.
+
+## 0.9.1 — 2026-08-16 — "What the Guard Was Not Guarding"
+
+- **The panel now lives on its own origin, so its JavaScript can no longer
+  reach the operator's token.** The panel was served from the same origin as
+  the control plane, in an iframe with no `sandbox` and no CSP, while the
+  token sat in `localStorage` — meaning a panel's own scripts could take it
+  and act as the operator. It is now served by a second loopback listener
+  (`NEXUSCREW_PANEL_PORT`, default 41821) that mounts `/panel/*` and nothing
+  else: no control API, no bearer. The port is part of the origin, so the
+  browser's same-origin policy does the enforcing rather than a convention.
+  For a **remote** node the port is negotiated during pairing
+  (`panelLocalPort`/`panelRemotePort`, as an obligatory pair) and travels on
+  its own forward. A node paired before this release keeps working on the old
+  path, and a remote cell without a negotiated port gets none — never a
+  borrowed local one.
+
+- **A cookie set by a panel no longer reaches our origin — including through
+  the WebSocket handshake.** `Set-Cookie` was stripped on the HTTP path but
+  copied verbatim on the `101` upgrade, so the same property held on one route
+  and not the other. A panel could overwrite the legitimate viewing cookie and
+  break the user's own panel from the inside. Hop-by-hop headers still pass on
+  the upgrade — there they *are* the response.
+
+- **Designating the Live cell works from a remote node.** The star now
+  commands the node that *owns* the cell rather than the one serving the page,
+  which was the main defect of 0.9.0. `liveHostAccess` is a per-peer
+  permission, denied by default, granted with `nexuscrew nodes live-host <node>
+  on`, and a refusal names its cause instead of failing silently. Turning the
+  star **off** across federation is now covered end to end, not just turning
+  it on.
+
+- **"Retry" is offered only where retrying can change the outcome.** Any `403`
+  without a named reason — a read-only node refusing a federated mutation, for
+  instance — was classified as an expired ticket, so the interface said "your
+  ticket is no longer valid" and offered a button that could not succeed.
+  Permanent refusals and invalid credentials now have their own causes and
+  messages, with no button; transient ones keep it.
+
+- **The published-tree guard no longer reports "clean" without having
+  looked.** Any blob it failed to read was silently skipped: with reads
+  failing, the gate stayed green having inspected nothing at all. An unreadable
+  blob is now a failure, and the number of inspected files must match the
+  tree — an empty result no longer counts as "no traces found".
+
+- **The test suite stopped measuring the machine.** Five tests that raced a
+  millisecond budget turned red under load and green in isolation; each false
+  alarm cost three isolated re-runs to dismiss, and a gate that is sometimes
+  red for no reason teaches people to distrust red. They now wait for an
+  observable condition instead. Where time *is* the property — deadlines,
+  grace periods — the clock was already injectable and those tests were left
+  alone. No timeout was raised and no assertion was loosened.
+
+- **New skills: `live`, `aidesktop`, and `nexuscrew` as the entry point.**
+  `aidesktop` ships a Docker recipe — Dockerfile, CDP relay, example compose —
+  for a desktop a browser-driving MCP can attach to. It documents the security
+  trade it makes rather than implying one it does not: the browser inside runs
+  unsandboxed, because the changes that would sandbox it are exactly the ones
+  that weaken the container, and on a loopback-only desktop the container is
+  the stronger boundary. What that costs you is stated plainly.
+
 ## 0.9.0 — 2026-08-15 — "The Star Keeps Its Promise"
 
 - **A cell panel finally opens — through our own route, not the raw URL.** An

package/README.md

@@ -11,6 +11,12 @@ NexusCrew turns live tmux sessions, AI CLI workers and connected machines into
 one local-first browser control plane. Your terminals stay real, your tools
 stay yours, and your infrastructure stays under your control.
 
+> **Reading this as an AI agent?** Start with
+> **[`skills/nexuscrew`](skills/nexuscrew/SKILL.md)**. It is the entry point:
+> what the system is, what you can actually do through it, which companion
+> skill covers which capability, where the trust boundaries are, and the rules
+> that hold across all of them. Every other NexusCrew skill assumes it.
+
 <p align="center">
   <img src="docs/img/fleet-deck-desktop.png" width="960" alt="NexusCrew desktop deck with multiple live tmux sessions">
 </p>
@@ -143,10 +149,22 @@ product verifies a configured pool before it can rotate within it. See
 | [Operations](docs/OPERATIONS.md) | CLI, boot, backup, updates and diagnostics |
 | [Security](docs/SECURITY.md) | Trust boundaries, tokens and credential handling |
 
-The repository also includes [MCP companion guidance](MCP_COMPANIONS.md),
-the machine-readable [`mcp-companions.json`](mcp-companions.json), and portable
-skills for memory, searchable document memory, bounded worker delegation,
-mail assistance and form filling.
+The repository also includes [MCP companion guidance](MCP_COMPANIONS.md) and
+the machine-readable [`mcp-companions.json`](mcp-companions.json).
+
+Portable skills ship with the package, and
+[`nexuscrew`](skills/nexuscrew/SKILL.md) is the one to read first:
+
+| Skill | Covers |
+|---|---|
+| [`nexuscrew`](skills/nexuscrew/SKILL.md) | **Start here** — the whole system and the rules across it |
+| [`nexuscrew-agent`](skills/nexuscrew-agent/SKILL.md) | Talking to the human, runtime discovery, delivery to cells |
+| [`live`](skills/live/SKILL.md) | Designating and permitting a node's Live host cell |
+| [`aidesktop`](skills/aidesktop/SKILL.md) | A cell's web panel, and the AI Desktop container recipe |
+| [`memory`](skills/memory/SKILL.md) | Persistent agent state |
+| [`vl-msa`](skills/vl-msa/SKILL.md) | Searchable document memory |
+| [`crew`](skills/crew/SKILL.md) | Bounded worker delegation |
+| [`mail-assistant`](skills/mail-assistant/SKILL.md) | Mailbox discovery, triage and reading |
 
 ## Platforms