@mmmbuto/nexuscrew 0.9.61 → 0.9.62
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
CHANGED
|
@@ -2,6 +2,12 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to NexusCrew are tracked here.
|
|
4
4
|
|
|
5
|
+
## 0.9.62 — 2026-10-06
|
|
6
|
+
|
|
7
|
+
- **Desktop cell actions refresh the route they touched.** Kill, visibility toggle, boot preference and the power sheet confirmation used to end with a reference error (a removed polling helper was still called there): the action succeeded on the backend but the sheet showed an error and the list stayed still. They now ask the shared fleet poll to refresh the touched route (same guard and train coalescing as the rest of the reads), covered by a render test on all four actions.
|
|
8
|
+
- **The quick cell switcher follows the normal list ordering.** The node groups come in the user-chosen node order (the same preference the decks grid follows) and each group keeps that node's own mode and manual/pinned cell order from the normal list; rows beyond the node's mode stay visible at the end of their group. Cells of a directly connected hub stay selectable and open even while that node's reads are unverified: opening follows the normal list (no fresh-verification requirement), with the server answering the real state. A local dismissal recorded while the owner is reachable is never queued back to the owner even with asymmetric grants (sync stays blocked without the reply grant).
|
|
9
|
+
- **The federated-ask close button always works on the viewing node.** Removing a card is a local intent and no longer requires the owner to be unreachable or to grant anything: the capability offers the local dismissal for any visible, quiet ask, the dismiss endpoint persists it durably on the receiving node without the former "owner channel availability" refusal (sync stays `blocked` without the reply grant — removing is not answering), and the close button stays enabled with reachable owners, older owner versions and missing grants. A locally dismissed card stays hidden across reloads and snapshots, while a newer generation of the same ask comes back; the owner-side alerts, feed watermark and owner closures are untouched, and a remote grant still dismisses on the owner as before.
|
|
10
|
+
|
|
5
11
|
## 0.9.61 — 2026-10-06
|
|
6
12
|
|
|
7
13
|
- **Fix startup crash when no explicit home is configured.** The owner question scope and the Fleet runtime now derive the fleet definitions path from one canonical helper, so a missing cfg.home falls back to os.homedir() like every other server path.
|