@mmmbuto/nexuscrew 0.9.25 → 0.9.27

package/CHANGELOG.md

@@ -2,12 +2,23 @@
 
 All notable changes to NexusCrew are tracked here.
 
-## 0.9.25 - 2026-09-13
+## 0.9.27 — 2026-09-14
 
-- **Compatibility note**: codex-vl >= 0.154.0-vl.3 inside a bound Fleet cell
-  requires NexusCrew >= 0.9.25 for the `nc_*` tools; NexusCrew 0.9.24 only
-  reads the legacy identity variables, which vl.3 removes from MCP children on
-  verified bindings. Standalone (legacy) cells keep working with both.
+- **The terminal counts columns the way tmux and glibc do.** Emoji and East Asian wide characters take two cells, so the glyphs after a wide character are no longer stale on phones; the terminal can also paint through a GPU (WebGL) renderer, with the DOM renderer as the floor and a GPU/DOM switch in the terminal bar to compare the two.
+- **The update banner never announces the version that is already running.** A served interface newer than the loaded bundle gets one silent, cache-bypassing reload and then a diagnostic banner (interface loaded vs interface served); a newer package on disk asks for a node restart instead of offering a reload that cannot help; a banner the user closes stays closed for the same versions; a second reload guard lives in the URL, so a storage that accepts a write and loses it at the next load cannot loop.
+- **The star (pin, then live designation) is in the compact cell selector too.** One implementation now serves the home, the desktop sidebar and the selector, with the same cycle, labels and tap target.
+- **The published entrypoint starts on Android/Termux, where `/usr/bin/env` does not exist.** `bin/nexuscrew.js` is a shell/JavaScript polyglot: it finds node next to the launcher first, then in `PATH`, and fails with a clear message and exit 127 when neither exists.
+- **A deck of this node opens by its owner-qualified URL too.** A new tab on `/deck/<node>/<name>` used to show an empty grid, and the tab could not save: the two ids of the same local deck (the local one and the owner-qualified one) are now resolved in one place by every lookup.
+- **The bundle version gate is line-agnostic and provable.** It works for 0.10 and beyond instead of being tied to the current release line, and it has cases that show a stale bundle failing.
+
+## 0.9.26 — 2026-09-13
+
+- rebuilt the frontend bundle for the shipped version (the 0.9.25 package carried a 0.9.24 bundle, so the UI kept showing the update banner); the publish gate now fails when the bundle version differs from the package version.
+
+## 0.9.25 — 2026-09-13
+
+- **Deprecated on npm**: the published package shipped a 0.9.24 bundle, so the
+  UI kept announcing an update that was already running; superseded by 0.9.26.
 
 - **MCP identity reads the verified binding metadata first (fail-closed).**
   `nexuscrew mcp` now evaluates the `NEXUSCREW_VERIFIED_*` metadata delivered

package/bin/nexuscrew.js

@@ -1,5 +1,23 @@
-#!/usr/bin/env node
+#!/bin/sh
+':' //; d=$(dirname "$0"); if [ -x "$d/node" ]; then exec "$d/node" "$0" "$@"; fi; n=$(command -v node) || { echo "nexuscrew: node not found next to the launcher or in PATH" >&2; exit 127; }; exec "$n" "$0" "$@"
+//: <<'0;'
 'use strict';
+// This file is TWO languages at once, and it has to be: the shebang `#!/bin/sh`
+// exists on Android as well, while `#!/usr/bin/env node` only resolves when the
+// Termux extension that rewrites /usr/bin/env happens to be loaded (a boot
+// script or a tmux session started elsewhere does not load it — measured:
+// "/bin/sh: .../usr/bin/nexuscrew: No such file or directory").
+//
+// Line 2 is the trick: `':'` is the sh no-op and a JavaScript string, and the
+// rest of the line is a sh statement inside a JavaScript comment. It execs the
+// same file with node, so the rest of this file is ordinary JavaScript and
+// `bin/nexuscrew.js` stays the single entrypoint npm links and Windows shims.
+//
+// node is resolved where it actually lives next to a launcher: `$PREFIX/bin`
+// on Termux and `.../bin` under nvm both keep `node` and `nexuscrew` in the
+// same directory, which is the node the launcher was installed with. PATH is
+// the fallback, and `$0` is used as given — `dirname` of a symlink is already
+// the right directory, and `readlink -f` is not portable.
 // The normal product surface is the PWA. `nexuscrew` starts it in background;
 // `nexuscrew show` starts it when needed and opens it.
 const { dispatch } = require('../lib/cli/commands.js');
@@ -11,3 +29,4 @@ Promise.resolve(dispatch(process.argv.slice(2)))
     process.stderr.write(`nexuscrew: ${String((e && e.message) || e)}\n`);
     process.exitCode = 1;
   });
+0;