@settlemint/dalp-cli 3.1.18-main.34042135992 → 3.1.18-main.34051758545

package/README.md

@@ -41,7 +41,8 @@ dalp get tokens --help
 dalp get tokens index --sort name --limit 25
 dalp get tokens documents index 0x…
 dalp create tokens mints 0x… --body '{"recipients":[…],"amounts":[…]}'
-# Mutations wait for settlement by default (TTY spinner + status). Agents get streamed status events.
+# Mutations ask the platform to hold the response until settlement (TTY spinner + status).
+# Agents get streamed status events either way.
 dalp create tokens mints 0x… --body '…' --no-wait
 ```
 
@@ -51,7 +52,7 @@ Long-running work uses `async *run` generators ([Incur Streaming](https://github
 
 - **Humans (TTY):** braille spinner on stderr with clear phase messages (`Preparing…`, `Submitting METHOD /url…`, `Waiting for settlement…`).
 - **Agents (`c.agent`):** structured yields `{ phase, message, status? }` with no spinner noise on stdout.
-- **Blockchain mutations:** when the API returns a `transactionId`, the CLI polls `@settlemint/dalp-sdk/wait-for-transaction` until terminal (override with `--no-wait`).
+- **Blockchain mutations:** the wait belongs to the platform, not the CLI. The default asks it to hold the response until the write settles; `--no-wait` asks it to answer immediately. Either way the command reports what came back, and a write that outlives the wait prints `Request accepted; the transaction is still settling` with the handle. Follow that handle with `dalp get transaction-requests stream <transactionId>`; the CLI does not poll it for you.
 - **SSE endpoints** (`…/stream`): each Server-Sent Event is yielded as a chunk. Use `--format jsonl` for NDJSON (`{"type":"chunk","data":…}`).
 - **Errors:** public `message` stays the headline; `why` / `fix` and mapped resource `links` become an Incur CTA (`meta.cta`) so agents get next commands without scraping free text.
 - **Success links:** JSON:API `links` (`next` / `prev` / related) map to suggested CLI commands when present.