slack-term 1.44.0 → 1.46.0

package/README.md

@@ -123,9 +123,10 @@ slack react "<permalink>" eyes --remove   # take a reaction back
 
 # Ask a question with its choices pre-seeded as 1️⃣..🔟 reactions — answering is
 # one tap on an existing pill, no emoji picker. Same two-step confirm gate as send.
-# A ❓ "その他 (other)" pill always follows the choices: pressing it means "none of
-# these" and the answer comes as a reply (exit 5), not as the ❓ itself.
-# --explain (or SLACK_TERM_ASK_EXPLAIN=1) adds an ℹ️ "説明して (explain)" pill after ❓:
+# A ➕ "その他 (other)" pill always follows the choices: pressing it means "none of
+# these" and the answer comes as a reply (exit 5), not as the ➕ itself. (Pills posted
+# before ➕ carry ❓ there; they are still read, collected and voided the same way.)
+# --explain (or SLACK_TERM_ASK_EXPLAIN=1) adds an ℹ️ "説明して (explain)" pill after ➕:
 # pressing it asks YOU to explain in the thread and is never an answer — the question
 # stays open. --wait/--waitFor say so on stderr and may post ONE thread note (once per
 # question) saying an explanation is coming; --explain-exit makes that exit 7.
@@ -151,7 +152,7 @@ slack ask "#eng" "@here 誰か見れる?" "見る" "あとで"            # anyo
 # With no choices the question asks for a free-text reply and the reply is the answer.
 # In a DM a plain reply counts; in a channel only reactions and thread replies do.
 # Once answered, the question is edited to "✅ …回答済み > <answer>" — the body/background
-# and the CHOSEN option line stay; the other options, ❓ line and instructions go. The
+# and the CHOSEN option line stay; the other options, ➕ line and instructions go. The
 # unpressed seeds are removed, leaving the chosen pill visible.
 #
 # Thread notes (audience replies that are not the answer, even after ✅) go to
@@ -362,9 +363,15 @@ into a second board.
 
 ### tail — real-time message stream
 
-`slack tail` polls a channel every 3 seconds (configurable via `--interval`) and
-prints new messages as they arrive, in the same `[ts]  @handle:  text` format as
-the `read` command.
+`slack tail` prints new messages in a channel as they arrive, in the same
+`[ts]  @handle:  text` format as the `read` command.
+
+- **Transport: RTM WebSocket** (default) when the token is a desktop session
+  (`xoxc-` + cookie) and none of `--since`, `--timeout`, `--exit-on-message` is
+  given. If RTM can't connect it says `RTM unavailable — switching to polling.`
+- **Fallback: polling** every `--interval` ms (default `60000` = 60 s; e.g.
+  `--interval=3000` for near-real-time at the cost of more API calls). Used for
+  other tokens, with any of the three flags above, or with `--no-rtm`.
 
 ```sh
 slack tail "#general"               # follow new messages from now

package/SKILL.md

@@ -174,13 +174,16 @@ without losing clicks. A reaction is durable state anyone can read back later.
   destination resolve with the bot token (so the bot needs `users:read`).
 - **Answer paths**: a pill, or free text. In a DM a plain reply counts; in a channel only
   reactions and thread replies do (a channel carries unrelated traffic).
-- **❓ is the standing "other" choice.** Every question with choices lists it last
-  (`1️⃣ … 2️⃣ … 3️⃣ … ❓ その他 — スレッドで返信`) and seeds it after the keycaps. Pressing it
+- **➕ is the standing "other" choice.** Every question with choices lists it last
+  (`1️⃣ … 2️⃣ … 3️⃣ … ➕ その他 — スレッドで返信`) and seeds it after the keycaps. Pressing it
   is not an answer — `--wait` notes it on stderr and keeps waiting for the reply, which
-  arrives as free text (exit `5`).
+  arrives as free text (exit `5`). Questions posted before 2026-10-14 carry ❓ as this
+  pill (line and seed); they keep working, and a ❓ press counts as "other" on either kind.
+  The head marker stays `:question:` — only the pill moved. A free-text question has no
+  other choice and still seeds ❓.
 - **ℹ️ is the "explain first" pill** — offered with `--explain` (or
-  `SLACK_TERM_ASK_EXPLAIN=1`; `--no-explain` overrides), listed under ❓ and seeded after
-  it. ❓ means "none fit, my answer follows"; ℹ️ means "I can't answer yet — explain".
+  `SLACK_TERM_ASK_EXPLAIN=1`; `--no-explain` overrides), listed under ➕ and seeded after
+  it. ➕ means "none fit, my answer follows"; ℹ️ means "I can't answer yet — explain".
   It **never answers or closes** the question: no ✅, the pills stay. `--wait`/`--waitFor`
   print who pressed it on stderr (`--json`: `explain: [user ids]`) and may post ONE thread
   note per question saying an explanation is coming (the thread is the record — re-presses
@@ -218,7 +221,7 @@ never get the same note twice. Only the question's audience counts; the asker, b
 bystanders are never notes.
 
 **Answering keeps the context.** The ✅ rewrite keeps the question's body (its background)
-and the chosen option; only the options not chosen, the ❓ line and the instructions go.
+and the chosen option; only the options not chosen, the ➕ (or ❓) line and the instructions go.
 The head is unchanged (`:white_check_mark:` prefix, question, stamp, quoted answer), so
 anything that keys on the prefix or re-reads the answer works on old and new ✅ bodies alike.
 
@@ -228,7 +231,11 @@ anything that keys on the prefix or re-reads the answer works on old and new ✅
 (repeatable `--void=`; alias `slack ask void <link…>`; same `--code` gate; own questions
 only, `--as-bot` for the bot's). The text becomes `:no_entry_sign:` + reason with the body
 kept, our pills come off, and a 🚫 reaction is added. Three states, three prefixes:
-`:question:` open, `:white_check_mark:` answered, `:no_entry_sign:` void. `--wait` /
+`:question:` open, `:white_check_mark:` answered, `:no_entry_sign:` void (the text prefix;
+the open question's marker REACTION is ➕ on a question with choices, ❓ on free text and
+on questions posted before ➕ — search `has::question: OR has::heavy_plus_sign:`; ➕ is a common
+emoji, so that can match unrelated messages — `slack ask --ls` reads the local sent-log
+and is unaffected). `--wait` /
 `--waitFor` on a void question **exit 6** (`--json` → `status: "void"`): stop waiting.
 Answered questions cannot be voided.
 
@@ -355,7 +362,7 @@ Reason flags stack independently of progress and of each other: ❗ `exclamation
 `slack thread`/`slack read` before replying to avoid duplicates; consolidate multiple
 points into one message.
 
-### todos — Slack's To-dos tab (read-only)
+### todos — Slack's To-dos tab
 
 Not `slack todo`: that tracks tasks as reactions. `slack todos` reads Slack's own
 **personal** To-dos tab (the successor of "Later"), the list in the sidebar.
@@ -364,12 +371,23 @@ Not `slack todo`: that tracks tasks as reactions. `slack todos` reads Slack's ow
 slack todos                       # open to-dos, soonest due first (OVERDUE marked)
 slack todos --filter completed    # also: saved (everything saved), archived
 slack todos --json -n 20          # one object per item: due, done, permalink, text
+
+# Writes — gated like send: the first run previews and prints a code, rerun with --code=<code>
+slack todos add  "<permalink>" --due 2026-11-01T18:00   # --saved: no checkbox
+slack todos done "<permalink>"                          # --undo reopens it
+slack todos edit "<permalink>" --due none               # or --due <time>, --todo / --saved
+slack todos rm   "<permalink>"                          # removes the to-do; the message stays
 ```
 
+A To-do always points at a message, so the target is a message permalink or
+`#chan:<ts>`. `add` refuses a message that is already saved; `done`/`edit`/`rm`
+refuse one that isn't (Slack's delete answers ok even when there is nothing to
+delete, so the CLI checks first).
+
 There is no public API: it uses the desktop client's internal `saved.list`, so
 it needs the **xoxc session** (`slack auth login`) and shows only your own
-to-dos. Bots can't see them. Slack can change this endpoint without notice.
-Adding and completing to-dos is not supported yet.
+to-dos. Bots can't see them. Writes use the internal `saved.add` /
+`saved.update` / `saved.delete`. Slack can change these endpoints without notice.
 
 ## Output formatting