slack-term 1.41.1 → 1.42.0

package/README.md

@@ -139,6 +139,9 @@ ANS=$(slack ask "@bob" "本番に出してよい?" "出してよい" "待って"
 slack ask "#eng" "@alice この PR 出してよい?" "出す" "待つ"     # only alice's answer counts
 slack ask "#eng" "@here 誰か見れる?" "見る" "あとで"            # anyone in #eng; real broadcast
 # (In a 1:1 DM the other party counts automatically — no tag needed.)
+# A tag that resolves to no one (no match, ambiguous, or the user list could not be read)
+# refuses the ask rather than dropping that answerer. With --as-bot, @tags and an
+# @user destination resolve with the bot token (it needs users:read).
 #
 # 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.
@@ -170,6 +173,12 @@ eval "$RESUME --timeout 0" && echo answered
 # A pressed pill is invisible to `slack tail` (it only sees `type: "message"`
 # events and drops `message_changed`), so this is the only way to hear about an
 # answer to a question you did not block on.
+#
+# Answered but never collected? Asks from THIS machine (local sent-log) whose pill was
+# pressed, or that got a reply, while nobody was waiting — grouped by the asking
+# session, with whether that agent is still alive and the --waitFor line that
+# collects each. Read-only: collecting (that line) is what takes it off the list.
+slack ask --pending                    # last 7 days; --since 2h, --channel, --json
 
 # Who sent what: every send/ask/poll/edit is logged locally with its sender —
 # pid, cwd, git branch, agent CLI and session id — and the same attribution rides

package/SKILL.md

@@ -160,6 +160,9 @@ without losing clicks. A reaction is durable state anyone can read back later.
   whole channel). Only their reaction/reply is taken as the answer; an unaddressed
   question is refused (exit 3) rather than let the first bystander decide it. In a 1:1 DM
   the other party counts automatically.
+  A tag that resolves to no one (no match / ambiguous / user list unreadable) refuses the
+  ask (exit 3) — use `<@USERID>` to be explicit. With `--as-bot`, tags and an `@user`
+  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
@@ -237,6 +240,15 @@ This path is not optional convenience — **a pressed pill is invisible to `slac
 which only sees `type: "message"` events and drops `message_changed`. Without `--waitFor`
 an answer can be pressed and nobody ever hears about it.
 
+**Answered, never collected.** `slack ask --pending` (`--since 7d` default, `--channel`,
+`--json`) checks every ask in this machine's sent-log that no `--wait`/`--waitFor` has
+collected, and lists the ones somebody answered — grouped by the asking session, with
+the agent pid and whether it is still alive (pid running, started before the ask, same
+CLI), and per item the exact `collect:` line to run (cursor included). It is read-only —
+nothing is posted, edited, stamped or relayed. Collecting is that `slack ask --waitFor=…`
+line: an answer it hands over (exit 0) takes the ask off the list; a free-text reply it
+hands over (exit 5) is not reported again, but a pill pressed after it is.
+
 ### sent — what did I post, and which session posted it
 
 Every `send`/`ask`/`poll`/`edit` is logged locally (`~/.config/slack-cli/sent.sqlite`)