@lmctl-ai/lmctl 0.1.180 → 0.1.182

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 (3) hide show
  1. package/README.md +7 -8
  2. package/dist/cli/index.js +941 -928
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -45,7 +45,7 @@ lmctl plan ./my-project
45
45
  lmctl lint ./my-project/my-project.lmctl
46
46
  lmctl seed ./my-project/my-project.lmctl
47
47
  lmctl chat ./my-project/my-project.lmctl Lead "Inspect the repo and propose next steps."
48
- lmctl mailbox sent --json
48
+ lmctl mail sent --json
49
49
  ```
50
50
 
51
51
  `lmctl status` is team/SELF-scoped: from a member session it shows your
@@ -69,15 +69,14 @@ Lintable teamfile templates for research, writing, and review teams ship in the
69
69
  `lmctl` top-level subcommands are: `api`, `chat`, `serve`, `device`,
70
70
  `team`, `terminal`, `tail`, `health`, `recover`, `ls`, `lint`, `seed`, `hire`,
71
71
  `refresh`, `clone`, `plan`, `workspace`, `diagnose`, `diagnose-prompt`,
72
- `mailbox`, `status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
72
+ `mail`, `status`, and `db`. Run `lmctl <command> --help` for details on each, and see the
73
73
  [documentation](https://lmctl.com/lmctl) to define your first team.
74
74
 
75
- `lmctl mailbox` is a read-only, low-level view of the current legacy message
76
- tables and historical provider sessions. It can list rows sent from SELF, trace
77
- exact and best-effort legacy links, check whether a recorded delivery session
78
- saw a message, and show flat 24-hour delegation activity. The current schema
79
- does not contain a unified message id or causal parent/child linkage; command
80
- help and JSON output state those limits explicitly.
75
+ `lmctl mail` exposes read-only primitives over the event-log substrate only:
76
+ list messages sent from SELF, read a message's ordered event history, check its
77
+ historical provider transcript, and render causal delegation lineage. It does
78
+ not query the retired mailbox/chat/invocation tables. Missing causal capture is
79
+ shown as an explicit tree root rather than guessed from timestamps.
81
80
 
82
81
  - `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.
83
82