@mmmbuto/nexuscrew 0.9.58 → 0.9.60

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to NexusCrew are tracked here.
 
+## 0.9.60 — 2026-10-06
+
+- **Managed Codex cells keep their own identity on every platform.** Legacy launches isolate supported Codex and Codex-VL clients from a shared daemon and preserve the cell's MCP context. Conflicting identity overrides and unavailable authority are refused with an actionable update message; verified authority launches retain their existing behavior.
+- **New questions remain distinct and alert once per generation.** Push notifications carry an owner-qualified question tag, and fan-out and event-feed deliveries share bounded alert admission. Replayed questions do not repeat the alert, while delivery responses retain compatibility and report channel outcomes.
+- **Question cards follow authoritative owner views.** Correlated notifications do not add a second card or voice alert. Reconnects refresh the panel, stale reads preserve newer live questions, and generation-qualified closures cannot remove a replacement question.
+- **Locally defined sessions retain question permissions regardless of their prefix or activity.** Capability checks, event feeds and snapshots use an exact, unique Fleet session mapping before the legacy codec. Unavailable or invalid enabled Fleet definitions fail closed, and snapshots return an error instead of certifying an empty view; disabled Fleet retains legacy resolution.
+- **Fleet polling does less repeated work.** Visible panels share polling requests, hidden views suspend their polling, session reads coalesce within a bounded window, and validated definition and credential reads reuse bounded caches while preserving invalidation checks.
+- **Frontend tests wait for asynchronous controls to appear.** Question relay and cell switching checks retain their original assertions without racing capability reads.
+
+## 0.9.59 — 2026-10-05
+
+- Delayed question events retain the original question generation separately from their emission time. Local dismissal follows the current visible generation, refuses conflicting views, and preserves historical aliases. Imported closure events identify the owner question while mixed-node clients can still resolve older alias-only closures.
+
+- Imported questions can be dismissed locally while their owner is unavailable. Cards offer an explicit local action after capability checks, remain visible on errors, and distinguish pending origin closure from unauthorized remote closure. Local dismissals survive restarts and feed refreshes, and synchronize with the owner through authorized routes using generation checks, bounded retries, and durable history. Retry bindings use public pairing rotation counters rather than credential hashes.
+- **VL nodes no longer blink away when their owner read fails.** The sidebar keeps the last known VL directory per owner, republished on every update and marked as not verified; entries survive skipped or failed reads and owners that temporarily drop out of the topology, within the same grace window used for owners. A confirmed read — even an empty one — replaces the cached entry for that owner alone, and a token or instance change drops it. Cache writes, publications, backoff successes and backoff failures are all scoped to the route's current owner: a late reply from a superseded owner (or from a route whose owner is no longer identifiable) touches neither the cache nor the backoff.
+
 ## 0.9.58 — 2026-10-03
 
 - **Reply to questions across connected hubs.** Replies and dismissals follow the question's owner through the network. Reply availability is checked separately from the notification feed, and an uncertain reply can be verified before another is sent.

package/README.md

@@ -47,19 +47,31 @@ a quick switch.
 
 ## Install in 30 seconds
 
+Install the package globally:
+
+```bash
+npm install -g @mmmbuto/nexuscrew@latest
+```
+
+Start it — the first run creates a loopback-only runtime, starts it in the
+background and opens the authenticated PWA:
+
 ```bash
-npm install -g @mmmbuto/nexuscrew
 nexuscrew
 ```
 
-The first run creates a loopback-only runtime, starts it in the background and
-opens the authenticated PWA.
+Prerequisites: Linux needs Node.js 18+, tmux (3.4+ recommended) and OpenSSH,
+installed with your distribution package manager. On macOS:
 
-| Platform | Prerequisites |
-|---|---|
-| Linux | Node.js 18+, tmux (3.4+ recommended), OpenSSH |
-| macOS | `brew install node tmux` |
-| Android / Termux | `pkg install nodejs-lts tmux openssh` |
+```bash
+brew install node tmux
+```
+
+On Android / Termux:
+
+```bash
+pkg install nodejs-lts tmux openssh
+```
 
 NexusCrew ships scriptless PTY prebuilds for Linux x64/ARM64, macOS x64/ARM64
 and Android ARM64. A normal global install does not need a compiler or native
@@ -183,9 +195,21 @@ devices.
 
 ## Development
 
+Run the test suite:
+
 ```bash
 npm test
+```
+
+Build the frontend assets:
+
+```bash
 npm run build
+```
+
+Run the runtime in the foreground:
+
+```bash
 node bin/nexuscrew.js serve
 ```