@lmctl-ai/lmctl 0.1.182 → 0.1.183
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.
- package/README.md +18 -0
- package/dist/cli/index.js +584 -528
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -46,6 +46,7 @@ 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
48
|
lmctl mail sent --json
|
|
49
|
+
lmctl mail sent --limit 100 --cursor "$NEXT_CURSOR" --json
|
|
49
50
|
```
|
|
50
51
|
|
|
51
52
|
`lmctl status` is team/SELF-scoped: from a member session it shows your
|
|
@@ -77,6 +78,23 @@ list messages sent from SELF, read a message's ordered event history, check its
|
|
|
77
78
|
historical provider transcript, and render causal delegation lineage. It does
|
|
78
79
|
not query the retired mailbox/chat/invocation tables. Missing causal capture is
|
|
79
80
|
shown as an explicit tree root rather than guessed from timestamps.
|
|
81
|
+
For every `mail` subcommand, `--json` is the stable external contract and
|
|
82
|
+
includes `schema_version: 1`; default text output is for humans and may change.
|
|
83
|
+
JSON failures use `{status:"error", errorKind, message}`. The unbounded `sent`
|
|
84
|
+
and `tree` scans are cursor-paginated, with 100 results by default and 1,000
|
|
85
|
+
maximum; pass `next_cursor` back through `--cursor` until it is `null`.
|
|
86
|
+
`schema_version` is the authoritative output-contract version; the separate
|
|
87
|
+
`schema: "event-log-v1"` field identifies the backing substrate.
|
|
88
|
+
|
|
89
|
+
Stable top-level success fields are:
|
|
90
|
+
|
|
91
|
+
- `sent`: `schema_version`, `schema`, `identity`, `filters`, `messages`,
|
|
92
|
+
`next_cursor`.
|
|
93
|
+
- `history`: `schema_version`, `schema`, `message_id`, `events`.
|
|
94
|
+
- `seen`: `schema_version`, `schema`, `message_id`, `receiver`, `db`,
|
|
95
|
+
`transcript`, `answered`.
|
|
96
|
+
- `tree`: `schema_version`, `schema`, `root`, `since`, `since_timestamp`,
|
|
97
|
+
`sent`, `next_cursor`, `orphan_policy`, `incomplete_capture_note`.
|
|
80
98
|
|
|
81
99
|
- `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.
|
|
82
100
|
|