@lmctl-ai/lmctl 0.1.263 → 0.1.264

package/README.md

@@ -46,13 +46,12 @@ 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 mail deliver msg_mbx_123 --json
 lmctl mail sent --limit 100 --cursor "$NEXT_CURSOR" --json
 ```
 
 `lmctl status` is team/SELF-scoped: from a member session it shows your
-identity, team roster busy/idle state, recent activity in both directions, and
-pending mailbox lanes. From a plain operator shell it shows a DB-wide summary.
+identity, team roster busy/idle state, and recent activity in both directions.
+From a plain operator shell it shows a DB-wide summary.
 Use `lmctl status --json` for the full machine-readable view; `--project` and
 `--web` are not status flags.
 
@@ -86,18 +85,13 @@ sqlite3 ~/.lmctl/state.db "INSERT OR REPLACE INTO lmctl_config(key,value,updated
 sqlite3 ~/.lmctl/state.db "INSERT OR REPLACE INTO lmctl_config(key,value,updated_at) VALUES('workspace.provider3','gemini',strftime('%Y-%m-%dT%H:%M:%fZ','now'));"
 ```
 
-`lmctl mail` exposes low-level primitives over the event-log substrate: list
-pending or sent messages, read event history/content, inspect historical
-provider evidence and causal lineage, declare handling/acknowledgement, and
-deliver one specifically addressed queued message. A `mail deliver` call is
-one provider turn for only that message; same-lane messages stay queued for
-separate calls, leaving ordering and retry policy to the external consumer.
-`mail pending` defaults to messages addressed to SELF when run from a member
-session; an explicit `--receiver` overrides that scope. From a plain operator
-shell with no SELF marker, it retains the fleet-wide discovery view.
-Read commands stay event-substrate-only; deliver deliberately follows the
-CREATE event's legacy mailbox-row reference into the existing live delivery
-machinery until that write path is fully cut over.
+`lmctl mail` exposes low-level, read-only/record-only primitives over the
+event-log substrate: list pending or sent messages, read event history/
+content, inspect historical provider evidence and causal lineage, and declare
+handling/acknowledgement. `mail pending` defaults to messages addressed to
+SELF when run from a member session; an explicit `--receiver` overrides that
+scope. From a plain operator shell with no SELF marker, it retains the
+fleet-wide discovery view.
 Missing causal capture is shown as an explicit tree root rather than guessed
 from timestamps.
 For every `mail` subcommand, `--json` is the stable external contract and