@samva/cli 0.14.0 → 0.16.0

package/AGENTS.md

@@ -38,6 +38,11 @@ export that will be delivered, which cannot carry a relative reference.
 machine watch output uses `--jsonl`. `--json` remains one-shot.
 `samva mailboxes events` is a stream: human mode prints one raw record per line, `--jsonl` one result
 envelope per event, `--quiet` nothing, and `--json` is refused (exit 2) with a pointer to `--jsonl`.
+A dropped connection reconnects from the last handled cursor, so an event can repeat but none is
+lost; each reconnect is one stderr line in human mode and one `type: "warning"` envelope
+(`reason: "mailbox_events_reconnecting"`, `details.cursor`, `details.attempt`) in `--jsonl`, never a
+stdout record. `--no-reconnect` ends the command on the first drop, exit `1` with the last cursor.
+A close that retrying cannot fix (`4401`, `4403`, an expired cursor) still ends the command.
 
 The developer loop for a template project is `samva templates dev` (the local visual editor, no
 `vite.config.ts`), `check` (type-check, compile, and render every fixture), `render <template>
@@ -141,6 +146,13 @@ stops sending and receiving, and `resume <id>` resumes without backfilling mail
 paused. These mutations support `--dry-run`. `remove <id>` deletes a mailbox (`--yes` outside a terminal, `--dry-run` to
 preview), `threads` searches, `read` prints a message (human output marks the body as
 untrusted email), and `send` and `reply` take `--idempotency-key` so a retry cannot send twice.
+`create`, `endpoints add`, and `send` take `--channel email|whatsapp|sms` (default `email`); on a
+phone channel the address is a connected number in E.164 form, and `send` takes one `--to` number
+with `--text` or, on WhatsApp, an approved `--template <templateId>` with `--data`. `reply` answers a
+WhatsApp or SMS message on its thread; a bare `--text` reply reads the message first to learn its
+channel. Free-form WhatsApp text outside the customer's 24-hour window fails with
+`WhatsAppServiceWindowClosedError`; send a template. These commands call the API directly because the
+public SDK describes email only.
 Quarantine `list` pages the same way, bounded by `--after` and `--before` on when a message was
 held; `release` and `discard` take the held message's `id` and require a person signed in with
 `samva login`. Discard requires confirmation (`--yes` outside a terminal) and supports `--dry-run`.
@@ -151,9 +163,10 @@ held; `release` and `discard` take the held message's `id` and require a person
 Human mailbox and extension results retain the same facts as JSON: mailbox endpoints (channel, address,
 sender name, default), thread state and activity, message bodies, attachments, authentication and actor,
 receipt waits and skipped recipients, held-mail results, and installation/run details.
-`samva mailboxes events` reads the SDK event stream with reconnects off and prints
-one record per event, `{cursor, id, event}` (`--jsonl` wraps each in a result envelope, `--quiet`
-prints none, `--json` is refused). A drop or refusal ends the command with the server's `_tag` as
+`samva mailboxes events` reads the SDK event stream, which reconnects (`--no-reconnect` turns that
+off), and prints one record per event, `{cursor, id, event}` (`--jsonl` wraps each in a result
+envelope, `--quiet` prints none, `--json` is refused). A refusal, or a drop under
+`--no-reconnect`, ends the command with the server's `_tag` as
 the error `reason`, its `status` and `details`, and a `Try:` line; the last handled cursor, which
 `--cursor` resumes from, goes to stderr in human mode and into `details.lastCursor` otherwise.
 `samva extensions dev` follows the same output modes. 401 and 403 exit 4. An expired