workbite 0.1.21 → 0.1.24

package/README.md

@@ -3,18 +3,15 @@
 WorkBite installs and opens **Work Stack** (organizes the work) and
 **StackBite** (gets it moving) as one native suite.
 
-Launcher 0.1.21 is a **sealed Windows x64 and Linux x64 release candidate**.
-Both native bundles were built from source
-`e3fddfbdca1206e16281014b4c04935d206563c9`, tree
-`ca0d86685adff33143fac209748d5d77b854f8da`. Actual sizes, SHA-256 hashes
-and embedded bundle digests are pinned in `release.json`; full archive audits,
-packaged probes and the paired candidate gate passed. Intended delivery is
-`workbite-0.1.21-windows-x64.zip` and `workbite-0.1.21-linux-x64.tar.gz`
-under tag `v0.1.21` in `Shinick-Han/WorkBite-releases`.
-Publication and installation remain separate maintainer steps; this record
-makes no public delivery or registry acceptance claim. The operator selected
-manual publication because hosted Actions quota is exhausted; no hosted CI or
-OIDC success is claimed and the existing CI publication helper is unchanged.
+Launcher 0.1.24 pins qualified Windows x64 and Linux x64 native archives.
+TypeScript TUI remains 1.0.38 and the embedded StackBite is 0.5.39.
+Both archives use build source `ba44d63cb89c9f979c236a2df6a7dcf73228a129`,
+tree `15c07e0d5de33440422210675855c73c8de8a0b9`. Their actual archive hashes,
+embedded bundle digests and sizes are sealed in `release.json` for `v0.1.24`
+in `Shinick-Han/WorkBite-releases`. Publication, registry delivery and installed
+runtime handover are separately verified maintainer operations. The maintainer
+uses the selected manual publication path because hosted Actions quota is
+exhausted; no hosted CI/OIDC success is claimed.
 It opens the familiar TypeScript Work Stack UI by default, which
 has one Tasks workbench: switch Focus/Table/Board without losing your selected
 Task, open its persistent Room's plain terminal, and control it beside or below
@@ -32,17 +29,22 @@ an explicit alternative per open: `workbite open --frontend rust` (or bare
 StackBite backend; the choice is not saved. Leaving the view or closing the UI
 keeps the agent running, and Task completion stays an explicit action.
 
-The 0.1.21 pair passed fresh native archive/runtime qualification: Windows
-10 stages and 17 packaged probes; Linux 15 stages, all 12 packaged ELF
-version-needs checks and 29 AlmaLinux 8.10 userspace probes, preserving the
-glibc 2.28 floor. Alma8 userspace ran under bwrap on WSL. Linux frozen mandatory
-UX modules and symbols passed; two unwired source helpers (grok_hooks and
-input_evidence) are excluded, so this is not full tracked PYZ or native Grok
-hook qualification. See the [qualification record](../../docs/releases/0.1.21/README.md).
-Source fixtures do not prove real agent turns, a booted AlmaLinux 8 kernel,
-SSH/VM, NFS or physical-phone behavior. Updating an existing native bundle
-requires an operator handover of existing backend processes; the launcher does not
-stop them or clear startup records automatically.
+The 0.1.24 pair passed independent archive/runtime review: all 17 Windows probes,
+all 12 Linux ELF version-needs audits at GLIBC <= 2.28, and 29 AlmaLinux 8.10
+userspace probes. Fresh bounded lifecycle source checks passed on Windows and
+Linux; Windows-only checks skipped on Linux remain explicit. These checks do
+not claim a real provider turn, interactive-screen acceptance, booted AlmaLinux,
+baseline CPU, SSH/VM, NFS or physical Phone behavior. Linux Phone is unsupported.
+See the [0.1.24 release notes](../../docs/RELEASE-0.1.24.md) and
+[qualification record](../../docs/releases/0.1.24/README.md) for pins and limits.
+
+The Rust frontend highlights the active Room and Seat with a background.
+Optional Claude/Codex lifecycle hooks add observed work status for CLIs started
+manually inside shell Seats. Stop means idle, never verified completion. Hook
+installation and an existing CLI's normal restart/resume may be required; Codex
+retains its normal hook trust review. Current owners and Seats remain on their
+existing runtime until a safe operator handover; updates do not stop them or
+clear unknown startup records automatically.
 
 The candidate keeps a stable Seat across explicit shell restarts, with a fresh
 generation and no inferred previous CLI/provider resume. Stop retains the Seat;
@@ -54,10 +56,18 @@ verified spawned children default to temporary, with recorded parent provenance.
 Bulk cleanup preserves pinned, live, stale and unknown targets; explicit removal
 of a finalized pinned Seat is a separate user choice.
 
-Arrow navigation previews; Enter or click requests the current exact Seat's
-writer claim, and input begins only after acknowledgement. One Ctrl+] returns
-to the UI. Native semantic instructions and mobile terminals remain unsupported
-and unadvertised.
+Arrow navigation now reaches the sidebar, header, Tasks, Seat previews and
+visible execution actions. Sidebar Up/Down previews; Enter/Space commits;
+Right returns to content. Execution Right enters actions and Left returns to
+Seats/Tasks. Pickers distinguish choices from filter text; forms and confirmations
+show focused buttons, including default Cancel. Hidden or clipped controls must
+be revealed before activation; arrow movement alone does not dispatch actions.
+Enter or click on a Seat requests its exact writer claim; input begins only
+after acknowledgement. Pending and granted raw CLI modes keep keys in the
+terminal path without replay; one Ctrl+] returns to the UI. Text fields keep
+caret arrows and literal Space; multiline Enter stays newline. Existing F6,
+Ctrl+B, Alt+Shift+Z and command shortcuts remain available. Native semantic
+instructions and mobile terminals remain unsupported and unadvertised.
 
 Mobile execution is source-qualified only: explicit PC execution permission is
 separate from read pairing; deployment uses the PC's saved provider, folder,
@@ -77,7 +87,7 @@ new one. A failure can leave the launcher installed without its suite: inspect
 `workbite check`. Never replay an unknown npm install without inspecting it.
 
 ```sh
-npm install -g workbite@0.1.21                             # only after registry publication and public-asset verification
+npm install -g workbite@0.1.24                             # only after registry publication and public-asset verification
 workbite install
 workbite open --workspace /abs/path/new-folder --init      # first time, once
 workbite                                                   # afterwards (TypeScript UI)
@@ -163,12 +173,12 @@ assignment refuses discovery. Standalone/unbound terminals retain the explicit
 workspace/context path. WorkBite does not enable MCP or configure providers
 automatically; source fixture checks do not prove an actual provider turn.
 
-The 0.1.21 candidate also repairs initial Task Room capability discovery and
+The candidate retains the repair for initial Task Room capability discovery and
 recovery notices after overlapping reads. Task Room inventory is filtered to
 the requested Task's Rooms before runtime inventory is read. Selecting a Task
 continues to create no Room, Seat or provider.
 
-The 0.1.21 candidate retains **Connect agent** in Task Execution (`a`),
+The candidate retains **Connect agent** in Task Execution (`a`),
 the global 9 Execution monitor and launch picker (`+`), clickable controls and
 scoped command palettes (`:`). Claude Code, Codex, Cursor and Grok Build use
 their official CLI login and credential storage. Missing CLIs offer install
@@ -190,7 +200,7 @@ Source checks used disposable fixtures, with no live account login, browser
 completion, account-entitlement proof or paid provider turn acceptance. See the
 [source acceptance record](../../docs/WORKBITE-AGENT-CONNECTION-ACCEPTANCE-2026-10-16.md).
 
-The Windows 0.1.21 candidate retains the read-only phone companion pilot from 0.1.14.
+The Windows candidate retains the read-only phone companion pilot from 0.1.14.
 Linux Phone support remains unsupported; paired releases do not imply identical
 platform capabilities.
 Phone actions preserve their selected target during status reads, show pending

package/bin/workbite.js

@@ -1,13 +1,13 @@
-#!/usr/bin/env node
-'use strict';
-const { main } = require('../lib/cli');
-main().then(({ code, signal }) => {
-  if (signal && process.platform !== 'win32') {
-    process.kill(process.pid, signal);
-  } else {
-    process.exitCode = code === null ? 1 : code;
-  }
-}).catch(error => {
-  console.error(`WorkBite: ${error.message}`);
-  process.exitCode = 1;
-});
+#!/usr/bin/env node
+'use strict';
+const { main } = require('../lib/cli');
+main().then(({ code, signal }) => {
+  if (signal && process.platform !== 'win32') {
+    process.kill(process.pid, signal);
+  } else {
+    process.exitCode = code === null ? 1 : code;
+  }
+}).catch(error => {
+  console.error(`WorkBite: ${error.message}`);
+  process.exitCode = 1;
+});