@mmmbuto/nexuscrew 0.9.42 → 0.9.43

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to NexusCrew are tracked here.
 
+## 0.9.43 — 2026-09-24
+
+- **On the phone, the first tap previews a cell and the second opens it.** A tap on a row now shows that cell's stream in the upper half of the screen, read-only and in the same font as the main terminal, and the preview's − and + move that one value; the second tap on the same row opens the cell, after a fresh re-read that still refuses a cell which died between the two taps. Rows have a fixed height and clip what is inside them, so a long name, both badges and the telemetry stay within their own row and a tap cannot land on the row below any more; a cell states **one** condition instead of showing two at once, and the node name rises once into the group header instead of repeating on every row. The dot only reports the state — looking live is the row's first tap, and the preview replaces it on this surface. A scroll is not a tap, and a gesture that is cancelled, started by a second finger, or dragged past its threshold neither selects nor opens, while Enter and Space keep working as the keyboard activation. The selection dies with its row: a cell that disappears, stops, or leaves the active filter closes the preview, and when it comes back it must be selected again rather than reopening on its own. (commits f0c0638, 20f6fea, 2dd71d0, 9678c34, 48c66ae, 1a22171, 73e218e)
+- **The mobile top bar keeps the zoom controls and gathers the rest into one menu.** The keyboard, files, panel and renderer switches leave the bar and move into the ⋯ menu, which is the same actions menu the cell rows already use, in its two existing shells — the bottom sheet on the phone and the anchored popover on the desktop: no second menu to learn, and the panel entry appears only for a cell that publishes one. The centre of the bar now carries both the engine and the state, and its subtitle truncates instead of sliding under the buttons on a narrow screen. (commit f0c0638)
+- **A federated question that cannot be answered now says which of the two reasons it is.** The read-only card showed one message even when the cause was not the grant but a missing feed of the owner's node — the card had arrived over push while the subscription was never activated — so the button that was offered could not have fixed anything. The state of that view is now kept next to the grants: without it the card says to enable reception, with a live view and a denied grant the message stays what it was. Permissions are unchanged; only the text is. (commit 3b06b91)
+- **codex-vl 0.156.1 is accepted by the cell hooks guard.** The fork's binary after the upstream merge reports itself as 0.156.1, and the table of proven versions admits it next to 0.155.1, with a test that covers acceptance and refusal — trust stays per exact hash, never per prefix, so any other version is still turned away. (commit b544f4f)
+
 ## 0.9.42 — 2026-09-23
 
 - **A cell that has finished stays "stopped" instead of turning unverified.** The expiry window applied to every state, so a cell whose turn had ended more than five minutes earlier fell back to "unverified": the UI showed an uncertain cell while it was simply stopped, with the right generation. Expiry exists for one case only — a turn interrupted with Ctrl-C emits no event and would stay "working" forever — and it no longer applies to "stopped", a state that stays true and that the process ending already invalidates. (commit 3594905)