@ucsandman/legcli 0.8.0 → 0.10.0

package/CHANGELOG.md

@@ -1,7 +1,125 @@
 # Changelog
 
+## 0.10.0 (2026-09-17)
+
+- **The board is responsive again, `leg` starts straight away, and the board
+  opens every time.** One running terminal was enough to saturate the board
+  server: it rewrites its record every few seconds and takes a control lock
+  about once a second, and the watcher over the sessions directory rebuilt the
+  whole terminals view — over a second of `git` — for every one of those
+  touches, including the lock files and the temp files atomic writes leave
+  behind. The server spent all its time in that loop, so it answered a
+  stylesheet in fourteen seconds and `/api/health` in seven. Four consequences,
+  all fixed:
+  - The watcher now drops locks and temp files by name, and checks the rest
+    against a stat fingerprint of the files the view is actually built from,
+    because a lock taken inside a session directory changes that directory's
+    own mtime and arrives as an event naming nothing else. What survives is
+    floored to one rebuild per interval. `canLand` is cached per record
+    revision with staggered expiries, so twenty worktrees are never re-read in
+    one pass. The terminals view went from 2,000 ms to 115 ms; on a board with
+    66 sessions `/api/health` went from 14.2 s to 2.4 ms and `/board.css` from
+    14.2 s to 1.5 ms.
+  - `leg claude` treated a board too busy to answer a health probe as no board
+    at all, spawned a second server that could only die of `EADDRINUSE`, then
+    polled the dead child for fifteen seconds. A listener on the port is now a
+    board: `leg` attaches to it.
+  - The board is opened whether or not this terminal is the one that started
+    it. Previously the browser was only opened on the path that spawned the
+    server, so with a board already running nothing ever opened.
+  - One push rebuilt the terminals grid three times (two listeners registered
+    for `leg:sessions` and one for the legacy alias, with the payload parsed
+    twice per push and one dispatch outside the staleness guard). Every button
+    was destroyed and recreated several times a second. One push now rebuilds
+    once, and an open confirm row is left alone until it is answered.
+
+- **Remove, Remove record, End and Land work.** Confirming any of them did
+  nothing at all. `confirmRow` clears `pendingConfirm` and then calls its
+  callback, and the callback read `pendingConfirm.action` — off the variable it
+  had just cleared. Every Yes on the Terminals panel threw
+  `TypeError: Cannot read properties of null (reading 'action')` into the
+  console and never reached the request. The callback now closes over a
+  snapshot taken before the row is built.
+
+- **Every conversation on this machine (`leg history`, `leg worktrees`, the
+  board's Conversations cell).** One read-only index over the conversations
+  Claude Code, Codex, Grok, Antigravity and Copilot CLI keep in their own
+  stores, plus Leg's own sessions, deduplicated (a session Leg started and
+  the same conversation in the agent's store are one row, marked `leg`; the
+  rest are `external`). List, filter by agent, repository or text, open one
+  (its last messages, read from the tail of the transcript only when asked),
+  and `leg history continue <id>` to start a supervised leg on it where the
+  installed CLI documents resume-by-id (claude, codex, grok, agy; copilot
+  lists and reads but is not an agent Leg runs). Nothing in an agent's store
+  is moved or written; Leg writes only `~/.leg/history/index.json`, refreshed
+  incrementally by size and mtime, and never opens a SQLite file. Every
+  checkout Leg can see, git's and its own and the ones conversations ran in,
+  with owner, uncommitted count, orphaned, stale and missing verdicts, read
+  only. On a shared board the whole group is the owner's. Redaction learned
+  the shapes another agent's transcript carries (Stripe, Google, xAI, npm,
+  GitLab, Hugging Face keys, JWTs, private-key blocks, basic auth, URL
+  credentials, `password=`), and the board token joined the values it strips.
+  Support matrix and every file read: docs/history.md.
+- **History, after its review.** The board's Conversations cell pages past
+  150 rows (the total no longer shrank with each cursor page); the board
+  refreshes a stale index in a child process instead of its own event loop;
+  a cwd on an unreachable network share no longer stalls a refresh; an
+  Antigravity retitle or a touched presence lock is seen by an incremental
+  refresh, and only that conversation is re-read; an older Leg session id
+  still opens the conversation it was one leg of; `leg history` prints a
+  failed refresh whatever the last index still lists, `refresh` fails cleanly
+  when another Leg holds the lock, `--limit 0` is a usage error (`--all`),
+  `--offset` works, a Leg-only row's id prints whole; a malformed id on
+  `/api/history/<id>` is a 400; an account name that is a path is ignored;
+  titles are cut to 200 as documented and go through the held-value
+  redaction too; the Copilot chip has a colour. Redaction no longer eats
+  `Basic authentication/authorization`, `cache_key = ...` or
+  `refresh_token: string`, and a value never crosses a line break.
+
+## 0.9.0 (2026-09-16)
+
+- **The portable harness (`leg harness`), off by default.** A hand-off can now
+  carry the working environment with the task: the source agent's global rules
+  (imports inlined), identity, hooks, skills, subagents, slash commands, MCP
+  servers and permissions, rendered into the destination client's own files as
+  far as it can represent them, with every dropped item explained.
+  `leg harness enable` detects clients, captures, shows the plan and writes
+  only after consent; `status`, `inspect`, `check`, `explain`, `diff`,
+  `history` and `doctor` are read-only; `sync`, `capture`, `source`, `policy`
+  and `disable` are the writes. Policies `warn`, `sync` and `strict` decide
+  what an unattended hand-off may do; strict refuses a destination it cannot
+  make safe and tries the next option. Every written file carries
+  `GENERATED by Leg harness`, lives in a marked region or owned key inside
+  files you also own, is backed up before an overwrite and skipped when
+  hand-edited. Credentials never move (`${NAME}` references). The session
+  record, its timeline (`harness`, `harness_blocked`), the card ledger and the
+  board (a chip on the row, a **Harness** section in the drawer) show what
+  transferred. Source changes are fingerprinted so an unchanged environment
+  costs a few stat calls at a hand-off. Docs: `docs/harness.md`.
+- **Engine.** The capture, bundle and apply engine is the Agnostic AI port
+  engine (MIT), vendored byte for byte under `src/harness/vendor/agnostic-ai/`
+  with its upstream commit and per-file hashes pinned; `npm test` refuses a
+  local edit. Attribution in `NOTICE`.
+- **Existing installs are unchanged.** No client file is touched until
+  `leg harness enable`; `preferences.json` gains a `harness` key that reads as
+  off when absent.
+
+## 0.8.1 (2026-09-16)
+
+- **Antigravity CLI (`agy`) workspace trust in worktrees and repos.** Leg writes
+  the folder trust record to `~/.gemini/antigravity-cli/settings.json`'s
+  `trustedWorkspaces` for both the repo root and the worktree directory, with
+  exact Windows drive and separator normalization matching Go's `runtime.memequal`
+  check so `leg agy` runs completely unattended without interactive trust prompts.
+- **Board server resolution in worktrees.** Fixed board asset resolution when
+  Leg is executed from within a git worktree.
+
 ## 0.8.0 (2026-09-16)
 
+- **The product is called Leg.** Website, CLI help, board logs and onboarding
+  copy say **Leg**; the command is `leg`; `legcli.com` is the domain, not the
+  product name. `leg up` prefixes lines with `[leg]`. Historical changelog
+  entries keep the previous name.
 - **Grok is a supervised and handoff agent.** `leg grok` starts Grok the same
   way `leg claude`, `leg codex` and `leg agy` start those agents: board
   alongside, usage tracking, and a live context handoff bundle. At the limit
@@ -11,6 +129,9 @@
   and agy, `--ask-for-approval never` for Codex, `--always-approve` for Grok).
   Opt out with `--no-auto-approve`, `LEG_AUTO_APPROVE=0` /
   `LEG_NO_AUTO_APPROVE=1`, or `"auto_approve": false` in `preferences.json`.
+- **`leg-agents` is the unscoped alias installer.** It pins the same version of
+  `@ucsandman/legcli` and exposes the same `leg` binary. CI publishes both
+  packages together; `npm test` fails if their versions drift.
 
 ## 0.7.0 (2026-09-15)
 

package/NOTICE

@@ -2,3 +2,11 @@ Portions of this software (src/runner.mjs, src/ledger.mjs, src/git-snapshot.mjs
 and their tests) were ported on 2026-09-10 from a private ucsandman repository
 (team tooling) under the MIT license; that code is included here under the Leg License Agreement (see LICENSE), which its author also holds. Telegram delivery, chat identifiers,
 and machine-specific paths were removed in the port.
+
+The portable-harness engine under src/harness/vendor/agnostic-ai/ is the
+Agnostic AI port engine (https://github.com/ucsandman/Agnostic-AI), copyright
+(c) 2026 Wes Sander, included byte for byte under the MIT License, whose full
+text is in src/harness/vendor/agnostic-ai/LICENSE. That copy is not
+relicensed: it stays MIT, and its upstream commit and per-file hashes are
+recorded in src/harness/vendor/agnostic-ai/UPSTREAM.json. Leg's own
+harness code (src/harness/*.mjs) is under the Leg License Agreement.