@mmmbuto/nexuscrew 0.9.27 → 0.9.29

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 All notable changes to NexusCrew are tracked here.
 
+## 0.9.29 — 2026-09-15
+
+- **The Live host of a node is chosen with an explicit command.** `Use as Live host` and `Remove Live host` sit in the cell menu and in the cell selector: the star is a pin only, and a small indicator shows the current host, so the choice and its outcome stay in sight.
+- **A designated Live host that lives on another node is reached through its owner.** The bridge is forwarded to the owner node and its answer — or a named refusal — comes back as it is, with no silent fallback to a local cell; federated bridge calls are rate-limited per sending node.
+- **`nexuscrew init` does not restart a service it does not own.** Run from a HOME that does not own the running service it warns and skips the activation instead of restarting someone else's service (`--no-activate` skips the activation on purpose).
+- **A federated request whose body was already read is refused by name.** A named 502 at once, instead of waiting 30 seconds for a body that nothing will send.
+
+## 0.9.28 — 2026-09-15
+
+- **The terminal renderer toggle is an icon button** (GPU/DOM stay in the tooltip and in the accessible label), so it no longer widens the bar and squeezes the cell name on phones.
+
 ## 0.9.27 — 2026-09-14
 
 - **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.

package/docs/OPERATIONS.md

@@ -41,6 +41,26 @@ Termux pidfiles include process identity data. If Android reuses a PID under
 another app UID, NexusCrew removes only the stale pidfile, never signals the
 foreign process, and restarts only the configured OpenSSH supervisor.
 
+## Smoke runs and temporary prefixes
+
+The user service manager (systemd `--user`, launchd) is **per-UID, not
+per-HOME**: it resolves `nexuscrew` by name inside the namespace of the
+logged-in user. `init` writes the boot definition under the HOME it was given,
+so a run against a temporary HOME would otherwise install a definition the
+manager never loads while the activation commands still acted on the real
+installation -- restarting the production service.
+
+For a smoke run or a throwaway prefix, use one of:
+
+- `nexuscrew serve` -- start the runtime without touching the service manager;
+- `nexuscrew init --no-activate` -- write config, token and boot definitions but
+  run no service manager command at all.
+
+Without `--no-activate`, `init` reads back which definition the manager has
+loaded and skips activation with an explicit warning when that definition is not
+the one just written. `nexuscrew restart` from the owning HOME activates it
+afterwards.
+
 ## Backup and restore
 
 **Settings → Fleet** can export and restore selected cells, system prompts and