@lmctl-ai/lmctl 0.1.97 → 0.1.99

package/CHANGELOG.md

@@ -2,6 +2,38 @@
 
 All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
 
+## 0.1.99 — 2026-07-10
+
+- **`lmctl wait` now reports your delivered messages, not just background jobs.** In self-centered
+  push mode you `chat` (queue), `push` (deliver), then `wait` to collect. `wait` reports the
+  responses of messages *you* sent that have been delivered since your last wait, sender-wide across
+  all targets, each reported exactly once (a per-message `waited` claim). If nothing is newly
+  delivered but something is still queued or in-flight, it blocks until a delivery lands; if nothing
+  is pending at all, it returns idle. `lmctl exec`'s existing tracked-job wake is unchanged — one
+  `wait` now surfaces both sources.
+- **Messages have a three-state lifecycle:** `queued` → `in-flight` → `delivered` (with the response
+  as the receipt). in-flight is a real persisted state so a separate `wait`/`check` can see a delivery
+  in progress; a delivery that dies mid-turn is reclaimed back to `queued` (at-least-once), and `wait`
+  runs that reclaim so it never blocks forever on a dead delivery.
+- Migration v48 adds the in-flight (`delivering_at` + holder) and `waited` markers to `agent_mailbox`,
+  guarded so fresh and migrated databases match.
+
+## 0.1.98 — 2026-07-10
+
+- **`lmctl push` — flush your outbound queue.** In daemon-less push mode the sender drives delivery:
+  `lmctl push` sequentially delivers all of this node's queued mail to receivers that are currently
+  idle (one lane per turn, reusing the same delivery path as `chat`), and skips busy receivers so
+  their mail stays queued. It is single-instance per node — a second concurrent `push` is rejected
+  as a conflict and delivers nothing.
+- **`lmctl check` — read-only status.** Reports this node's background jobs and its outbound queued
+  mail, grouped by `(sender, receiver)` lane with pending counts and each receiver's busy/idle. It
+  never delivers, marks, or mutates anything (including creating no tracked invocation).
+- **Removed `lmctl recv` and `lmctl loop`.** In push mode the receiver never pulls (delivery is
+  pushed), and `loop` is replaced by launching `lmctl chat`/`lmctl push` in the background and
+  waking on `lmctl wait`. Both now error as unknown commands. `wait` is unchanged.
+- The idle-target delivery used by `chat` is now a shared `deliverLane` helper that `push` reuses,
+  so the two can't drift.
+
 ## 0.1.97 — 2026-07-10
 
 - **`lmctl chat` now carries the mailbox queue; `lmctl send` is removed.** One verb. Chatting a

package/README.md

@@ -57,7 +57,7 @@ onboarding.
 Lintable teamfile templates for research, writing, and review teams ship in the
 [examples gallery](https://lmctl.com/examples/).
 
-`lmctl` top-level subcommands are: `api`, `chat`, `recv`, `loop`, `code`, `serve`, `intake`,
+`lmctl` top-level subcommands are: `api`, `chat`, `check`, `push`, `code`, `serve`, `intake`,
 `mcp`, `monitor`, `device`, `team`, `terminal`, `tail`, `health`, `wait`,
 `exec`, `recover`, `ls`, `lint`, `seed`, `hire`, `refresh`, `clone`, `plan`, `workflow`,
 `run`, `project`, `workspace`, `diagnose`, `diagnose-prompt`, `status`, and
@@ -65,7 +65,8 @@ Lintable teamfile templates for research, writing, and review teams ship in the
 [documentation](https://lmctl.com/lmctl) to define your first team.
 
 - `lmctl chat <teamfile> <alias> "message"` drives or messages a member; if a member-origin target is busy, chat queues the message for that lane.
-- `lmctl recv` drains the calling Lead's mailbox consume-on-read, inferred from `LMCTL_SELF_SESSIONID`.
+- `lmctl check` shows the calling member's background jobs and outbound queued lanes without mutating anything.
+- `lmctl push` flushes the calling member's outbound queued lanes to idle receivers; busy receivers stay queued.
 
 ## Model selection