@simplepush/cli 0.1.1 → 0.2.0

package/README.md

@@ -18,6 +18,7 @@ bunx @simplepush/cli events --since 24h
 ```
 sp task      Send a task, optionally wait for the first completion.
 sp subtask   Append a follow-up to an existing task via its append token.
+sp cancel    Withdraw a pending task, subtask, or task group you sent.
 sp notify    Send a fire-and-forget notification.
 sp collect   Collect replies, inputs, or submissions as bounded NDJSON.
 sp download  Download one file a collect line referenced, by its ids.
@@ -69,6 +70,23 @@ sp notify -t ops --content "Restart the staging cluster?" -c "Approve,Deny" \
   --format json | sp collect
 ```
 
+### Cancel what you no longer need
+
+`sp cancel` withdraws a pending send; the id's prefix picks what: `tsk_` one task, `sub_` one follow-up (the chain stays live), `grptsk_` every still-pending member of a group. Recipients see the card flip to canceled, and a running `sp collect` counts the member as done.
+
+```sh
+sp cancel tsk_0198…
+
+# tear down the rest of a group after the first useful answer
+sp cancel grptsk_0198… --reason answered --note "already handled"
+# → {"type":"canceled","groupId":"grptsk_…","canceled":2,"skipped":1}
+
+# replace a follow-up with a corrected one (same chain only)
+sp cancel sub_0198… --reason superseded --superseded-by sub_0199…
+```
+
+Already-answered members are skipped, never failed; re-canceling is a no-op. With an API token it cancels a personal send, without one it uses the org session. `--note` is sealed under the org master key automatically on org cancels; on personal cancels pass `-p "pw@topic"` (topic send) or a bare `-p "pw"` (send to your own devices) to seal it.
+
 ### Download the files people upload
 
 `--save-files` downloads every collected file (photos, voice recordings, file uploads, reply and submission files) into a directory as it streams in, decrypted and checksum-verified. Each file object on the NDJSON line gains a `path` with the saved location.
@@ -137,6 +155,15 @@ sp subtask --append-token "$TOKEN" \
   -a "accept=Accept:primary,deny=Deny:destructive"
 ```
 
+Collect its answers like any send: pipe the `sent` line, or collect after the fact by pairing the parent task id with the subtask id in `--instance` (a subtask's events arrive on the parent task, so the id needs both halves):
+
+```sh
+sp subtask --append-token "$TOKEN" --format json \
+  --text-input "ETA?" | sp collect --inputs
+
+sp collect --instance tsk_0198…/sub_0198… --since 24h
+```
+
 ### Watch your account live, or replay history
 
 ```sh