@lmctl-ai/lmctl 0.1.98 → 0.1.99

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/CHANGELOG.md +16 -0
  2. package/dist/cli/index.js +572 -494
  3. package/dist/cli/schema.sql +10 -1
  4. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -2,6 +2,22 @@
2
2
 
3
3
  All notable public-preview changes for `@lmctl-ai/lmctl` are recorded here.
4
4
 
5
+ ## 0.1.99 — 2026-07-10
6
+
7
+ - **`lmctl wait` now reports your delivered messages, not just background jobs.** In self-centered
8
+ push mode you `chat` (queue), `push` (deliver), then `wait` to collect. `wait` reports the
9
+ responses of messages *you* sent that have been delivered since your last wait, sender-wide across
10
+ all targets, each reported exactly once (a per-message `waited` claim). If nothing is newly
11
+ delivered but something is still queued or in-flight, it blocks until a delivery lands; if nothing
12
+ is pending at all, it returns idle. `lmctl exec`'s existing tracked-job wake is unchanged — one
13
+ `wait` now surfaces both sources.
14
+ - **Messages have a three-state lifecycle:** `queued` → `in-flight` → `delivered` (with the response
15
+ as the receipt). in-flight is a real persisted state so a separate `wait`/`check` can see a delivery
16
+ in progress; a delivery that dies mid-turn is reclaimed back to `queued` (at-least-once), and `wait`
17
+ runs that reclaim so it never blocks forever on a dead delivery.
18
+ - Migration v48 adds the in-flight (`delivering_at` + holder) and `waited` markers to `agent_mailbox`,
19
+ guarded so fresh and migrated databases match.
20
+
5
21
  ## 0.1.98 — 2026-07-10
6
22
 
7
23
  - **`lmctl push` — flush your outbound queue.** In daemon-less push mode the sender drives delivery: