@mmmbuto/nexuscrew 0.9.59 → 0.9.60
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -0
- package/frontend/dist/assets/index-D42BJVwr.js +169 -0
- package/frontend/dist/index.html +1 -1
- package/frontend/dist/sw.js +18 -4
- package/frontend/dist/version.json +1 -1
- package/lib/audio/dispatch.js +5 -0
- package/lib/fleet/builtin.js +10 -4
- package/lib/fleet/managed.js +76 -47
- package/lib/fleet/runtime.js +15 -1
- package/lib/mcp/tools.js +1 -0
- package/lib/notify/ask-alert-identity.js +24 -0
- package/lib/notify/ask-alert-registry.js +96 -0
- package/lib/notify/asks.js +8 -2
- package/lib/notify/closure-retry.js +5 -4
- package/lib/notify/event-feed-client.js +140 -15
- package/lib/notify/event-feed-producers.js +4 -0
- package/lib/notify/event-feed-routes.js +2 -1
- package/lib/notify/notifier.js +19 -7
- package/lib/notify/owner-ask-scope.js +35 -0
- package/lib/notify/push-relay.js +10 -1
- package/lib/notify/routes.js +26 -16
- package/lib/server.js +70 -20
- package/lib/tmux/list.js +45 -0
- package/lib/tmux-reads.js +44 -0
- package/package.json +1 -1
- package/frontend/dist/assets/index-CZFJnks_.js +0 -169
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to NexusCrew are tracked here.
|
|
4
4
|
|
|
5
|
+
## 0.9.60 — 2026-10-06
|
|
6
|
+
|
|
7
|
+
- **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.
|
|
8
|
+
- **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.
|
|
9
|
+
- **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.
|
|
10
|
+
- **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.
|
|
11
|
+
- **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.
|
|
12
|
+
- **Frontend tests wait for asynchronous controls to appear.** Question relay and cell switching checks retain their original assertions without racing capability reads.
|
|
13
|
+
|
|
5
14
|
## 0.9.59 — 2026-10-05
|
|
6
15
|
|
|
7
16
|
- 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.
|