slack-term 1.38.0 → 1.39.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -91,7 +91,7 @@ slack search "deploy" --count 50
91
91
  slack send "#general" "Hello team"
92
92
  # Prints who you're acting as (From: @handle (Uxxxx) — Workspace) + a destination
93
93
  # preview + confirm code; rerun with --code=<code> to actually send. Every gated write
94
- # (send/edit/delete/upload/schedule/channel create/drafts) shows that From: line and
94
+ # (send/edit/delete/upload/schedule/channel create/lists/drafts) shows that From: line and
95
95
  # binds it into the code, so a profile switch mid-flow invalidates it instead of acting
96
96
  # as the wrong account.
97
97
  slack send "#general" "Hello team" --code=<code>
package/SKILL.md CHANGED
@@ -120,7 +120,7 @@ plus `[as bot]` under `--as-bot`) and the resolved destination (`→ ... — THR
120
120
  `→ ... — NEW top-level message`); verify both before re-running with `--code`.
121
121
 
122
122
  **Every** gated write opens its preview with that same `From:` line — `send`, `edit`,
123
- `delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `drafts edit`,
123
+ `delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `lists create/add/set/share`, `drafts edit`,
124
124
  `drafts delete` — and the identity is part of the confirm hash: switching
125
125
  profile/token between preview and confirm invalidates the code instead of acting as
126
126
  someone else. It matters most on `schedule send`, where the message goes out later,
@@ -140,6 +140,8 @@ To actually notify someone, write `@handle` (auto-converted to `<@USERID>`; see
140
140
  When the target is a **thread**, the confirm preview shows the thread's recent messages
141
141
  (not the channel's last message) and prints `⚠ possible duplicate: …` if your text is
142
142
  near-identical to an existing reply — so you can avoid re-posting something already said.
143
+ Preview lines mask any 32+ character token-like run (`[A-Za-z0-9_-]`) to its first 4
144
+ characters, so a key someone pasted into the thread or channel is not echoed into your log.
143
145
 
144
146
  `send` also warns (non-blocking) when the destination's most recent message is your own
145
147
  and no one has replied since — `⚠ 相手はまだ返信していません…`, suggesting `slack edit`