@lmctl-ai/lmctl 0.1.94 → 0.1.96

package/CHANGELOG.md

@@ -2,6 +2,38 @@
 
 All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
 
+## 0.1.96 — 2026-07-10
+
+- **Fixed: 0.1.95 silently stopped recording `team_chat_log`.** The chat-log INSERT omitted the
+  `origin` column, so on any existing database (where `origin` is `NOT NULL`) every insert failed
+  with `NOT NULL constraint failed: team_chat_log.origin` and the row was dropped — chats still
+  worked, but the audit trail stopped. Found by dogfooding the published artifact.
+- **Fixed: fresh 0.1.95 databases got a `team_chat_log` without an `origin` column at all.** The v46
+  migration hand-duplicated the table shape and drifted from `schema.sql`, so new installs never
+  recorded operator-vs-agent origin. Fresh and migrated databases now produce an identical table, and
+  a pre-46 database gains `origin` (existing rows backfilled to `unknown`) with its rows preserved.
+- Regression tests now assert that a fresh database's `team_chat_log` column set matches `schema.sql`
+  exactly, and that a migrated database also has `origin`.
+
+## 0.1.95 — 2026-07-10
+
+- **Removed `I_am=` (and `--from`) entirely.** A member's identity now resolves **only** from
+  `LMCTL_SELF_SESSIONID`, which lmctl sets automatically on every member it spawns. Nothing a user
+  can type asserts an identity.
+- **The identity marker is required exactly when lmctl must persist a sender** — i.e. when enqueueing
+  a mailbox message. Direct blocking calls need no identity, so **`lmctl chat`, `lmctl loop` and
+  `lmctl recover` now work from a plain operator shell with no flag**. Previously `--from`/`I_am=`
+  was mandatory for any operator-run chat, so this is strictly more usable than before.
+- **`lmctl send` to a busy target without a marker now returns `busy`** (try later) instead of an
+  error, and enqueues nothing. An operator cannot queue: it has no `lmctl wait` to be woken.
+- **Fixed `lmctl recover`.** It drives only idle members and no longer demands a caller identity.
+- **MCP stale-bridge cleanup is shape-gated.** A stale `lmctl`/`lmctl0` bridge is removed only when
+  **both** the server name and the command shape (`lmctl mcp`) match, so an unrelated MCP server you
+  configured yourself is never deleted. Cleanup now also runs on `seed`. The `from` parameter was
+  removed from the `lmctl_chat` MCP tool schema.
+- **Migration v46:** `team_chat_log` sender columns are nullable (operator-origin turns record no
+  sender). The migration is guarded — it rebuilds only when the table exists and never throws.
+
 ## 0.1.94 — 2026-07-08
 
 - **Debug diagnostics now write only to the debug log file.** YOLO spawn

package/README.md

@@ -65,7 +65,7 @@ Lintable teamfile templates for research, writing, and review teams ship in the
 [documentation](https://lmctl.com/lmctl) to define your first team.
 
 - `lmctl send <teamfile> <alias> "message"` messages a Lead; enqueues if it is up, falls back to chat if down.
-- `lmctl recv [I_am=<teamfile:alias>]` drains the calling Lead's mailbox consume-on-read.
+- `lmctl recv` drains the calling Lead's mailbox consume-on-read, inferred from `LMCTL_SELF_SESSIONID`.
 
 ## Model selection