@lmctl-ai/lmctl 0.1.179 → 0.1.181

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 mail sent --json
 ```
 
 `lmctl status` is team/SELF-scoped: from a member session it shows your
@@ -68,9 +69,15 @@ 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
+`mail`, `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 mail` exposes read-only primitives over the event-log substrate only:
+list messages sent from SELF, read a message's ordered event history, check its
+historical provider transcript, and render causal delegation lineage. It does
+not query the retired mailbox/chat/invocation tables. Missing causal capture is
+shown as an explicit tree root rather than guessed from timestamps.
+
 - `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