@lmctl-ai/lmctl 0.1.178 → 0.1.180

package/README.md

@@ -45,6 +45,7 @@ lmctl plan ./my-project
 lmctl lint ./my-project/my-project.lmctl
 lmctl seed ./my-project/my-project.lmctl
 lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next steps."
+lmctl mailbox sent --json
 ```
 
 `lmctl status` is team/SELF-scoped: from a member session it shows your
@@ -68,9 +69,16 @@ Lintable teamfile templates for research, writing, and review teams ship in the
 `lmctl` top-level subcommands are: `api`, `chat`, `serve`, `device`,
 `team`, `terminal`, `tail`, `health`, `recover`, `ls`, `lint`, `seed`, `hire`,
 `refresh`, `clone`, `plan`, `workspace`, `diagnose`, `diagnose-prompt`,
-`status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
+`mailbox`, `status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
 [documentation](https://lmctl.com/lmctl) to define your first team.
 
+`lmctl mailbox` is a read-only, low-level view of the current legacy message
+tables and historical provider sessions. It can list rows sent from SELF, trace
+exact and best-effort legacy links, check whether a recorded delivery session
+saw a message, and show flat 24-hour delegation activity. The current schema
+does not contain a unified message id or causal parent/child linkage; command
+help and JSON output state those limits explicitly.
+
 - `lmctl chat <teamfile> <alias> "message"` drives or messages a member. If a member-origin target is busy, chat queues the message for that sender->receiver lane; the next chat **from that same sender** to that receiver, when it is free, delivers the queued lane plus the new message. The lane key is `(sender, receiver)`: **a chat to that receiver from anyone else does not flush your queued mail.** If you go idle waiting for the reply you queued, nothing else will unblock it — you are the only party whose next chat flushes that lane.
 
 ## Model selection