slack-term 1.41.0 → 1.41.2

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.

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
@@ -415,6 +418,7 @@ slack news --limit 1
 - **`conversations.invite` reports success but the member never shows up** — the invited user is likely a single-channel guest (`is_ultra_restricted`); Slack silently no-ops the invite since that account type can only ever belong to the one channel it was created in. `channel create --invite` now warns about this up front.
 - **Send is rejected with "use #channel or @user"** — the CLI enforces human-readable targets. Use `#channel-name` or `@display-name`, not raw IDs.
 - **Confirm code mismatch on any gated write** — the content, target or acting identity changed between preview and confirm (a different profile/`SLACK_TOKEN`, or `--as-bot` added or dropped). Re-run without `--code` for a fresh preview, and re-check the `From:` line and the `→` destination line (THREAD REPLY vs NEW top-level message).
+- **`refusing to act as YOU — SLACK_BOT_TOKEN is exported …`** — you set a bot token in the shell or a project `.env` (not the global `~/.config/slack-cli/.env`) but ran a write without `--as-bot`, which would post as the logged-in person. Add `--as-bot` to post as the app; to post as yourself, set `SLACK_TOKEN` or clear the bot token for that run (`SLACK_BOT_TOKEN= slack …`). Reads are never refused.
 - **Enterprise Grid / admin-locked workspace** — custom app installation may need admin approval or be disabled outright.
 
 ## Safety