slack-term 1.43.0 → 1.45.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "slack-term",
-  "version": "1.43.0",
+  "version": "1.45.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/snomiao/slack-term.git"

package/ts/ask.ts

@@ -34,13 +34,45 @@ export type AskFound = { answer: string; how: string; who?: string; ts?: string;
  *  in-flight question unparseable. The marker carries identity now, and the
  *  instruction is free to be translated.
  *
- *  It is also seeded as a REACTION, which is what makes `has:question` list
- *  every question the way `has:pushpin` lists every todo. `todo` gave this
- *  emoji up (its needs-discussion flag moved to :thinking_face:) precisely so
- *  the two would not collide in search. */
+ *  It is also seeded as a REACTION on free-text questions and on pills posted
+ *  before ➕; a question with choices now seeds ➕ (`ASK_OTHER_MARKER`) in its
+ *  place. So `has::question: OR has::heavy_plus_sign:`-style search lists the
+ *  open questions the way `has::pushpin:` lists every todo — with the trade-off
+ *  that ➕ is a common emoji, so that search can also match unrelated messages
+ *  (`slack ask --ls` reads the local sent-log and is unaffected). `todo` gave
+ *  ❓ up (its needs-discussion flag moved to :thinking_face:) precisely so the
+ *  two would not collide in search. */
 export const ASK_MARKER = "question";
 export const ASK_MARKER_PREFIX = `:${ASK_MARKER}: `;
 
+/** The "other" pill — "none of these fit, my answer follows as a reply" —
+ *  seeded after the numbered pills and listed under them in the body. ➕, not
+ *  ❓ (taku 2026-10-14): ❓ read as "I have a question", not "add my own answer".
+ *
+ *  ❓ stays the HEAD marker (`ASK_MARKER_PREFIX` on the first line): that is the
+ *  wire format that identifies an ask, and every reader keys on it. Only the
+ *  pill moved. A free-text question has no other line and still seeds ❓.
+ *
+ *  Pills posted before this carry ❓ as the other pill, both as the seed and
+ *  as the body line. They stay fully working: the parser accepts either line
+ *  (`askSeedMarker(text)` says which one a question was seeded with), a press
+ *  on either counts as "other", and void / edit / resolve take off exactly the
+ *  seed that is there. */
+export const ASK_OTHER_MARKER = "heavy_plus_sign";
+export const ASK_OTHER_PREFIX = `:${ASK_OTHER_MARKER}: `;
+/** Every reaction that means "other" on some open pill: ➕ now, ❓ on the
+ *  pills posted before ➕. */
+export const ASK_OTHER_MARKERS: readonly string[] = [ASK_OTHER_MARKER, ASK_MARKER];
+
+/** The "explain" pill (`--explain`): pressing it asks the asker to explain the
+ *  question, and is NEVER an answer. Reported 2026-10-14: an "explain" offered
+ *  as a numbered choice was collected as the decision and closed the question.
+ *  Not ➕: ➕ means "none of these fit — my answer follows as a reply", and that
+ *  reply resolves the question; ℹ️ means "I cannot answer yet", and the question
+ *  stays open for a real answer after the explanation. */
+export const ASK_EXPLAIN_MARKER = "information_source";
+export const ASK_EXPLAIN_PREFIX = `:${ASK_EXPLAIN_MARKER}: `;
+
 // The copy a reader sees, per language. Japanese is the default and its
 // strings are a WIRE FORMAT: questions already in flight were posted with them
 // and are recognised by them, so they must never be reworded. Adding a language
@@ -118,6 +150,14 @@ interface AskCopy {
   overflowNote: string;
   otherThread: string;
   otherHere: string;
+  /** The free-text parser matches this exactly (`askIsExplainCopy`), so it is
+   *  a wire format too: questions in flight carry it. */
+  explainLine: string;
+  /** WIRE FORMAT — never reword. `--wait`/`--waitFor` find a question's
+   *  thread note by this exact copy (`askIsExplainNote`), so a reworded note
+   *  is not found by later runs, which would post a second one, and the old
+   *  note would stop being excluded from answers and notes. */
+  explainNote: string;
   invalidPrefix: string;
   answeredVia: (how: string, who: string) => string;
   howReaction: (glyph: string) => string;
@@ -128,10 +168,10 @@ interface AskCopy {
 }
 
 /** The standing "none of these" choice (`otherThread` / `otherHere`), listed
- *  after the numbered ones. It is the ❓ marker pill, which is seeded LAST so
- *  the reaction row reads the same as the body: 1️⃣ 2️⃣ 3️⃣ ❓. People already
- *  pressed ❓ to mean "none of these fit" — the line makes that an explicit
- *  choice, and says where the actual answer has to go: ❓ itself carries no
+ *  after the numbered ones. It is the ➕ pill (`ASK_OTHER_MARKER`; ❓ on pills
+ *  posted before 2026-10-14), seeded LAST so the reaction row reads the same as
+ *  the body: 1️⃣ 2️⃣ 3️⃣ ➕. The line makes "none of these fit" an explicit
+ *  choice, and says where the actual answer has to go: ➕ itself carries no
  *  answer text, so it never resolves the question; the reply that follows it
  *  does (exit 5, delivered as free text). Optional on the way in: questions
  *  posted before it existed have no such line and must stay collectable.
@@ -147,8 +187,10 @@ export const ASK_COPY: Record<AskLang, AskCopy> = {
       "_このメッセージの *スレッド* で返信してください。本文がそのまま回答になります (チャンネルへの通常投稿は回答として拾いません)。_",
     instructionTextHere: "_このメッセージに返信してください。本文がそのまま回答になります。_",
     overflowNote: "_11 番目以降はリアクションがないので、返信で答えてください。_",
-    otherThread: `${ASK_MARKER_PREFIX}その他 — スレッドで返信してください`,
-    otherHere: `${ASK_MARKER_PREFIX}その他 — このメッセージに返信してください`,
+    otherThread: `${ASK_OTHER_PREFIX}その他 — スレッドで返信してください`,
+    otherHere: `${ASK_OTHER_PREFIX}その他 — このメッセージに返信してください`,
+    explainLine: `${ASK_EXPLAIN_PREFIX}説明して — 押すと質問者に説明を頼みます (回答にはなりません)`,
+    explainNote: `${ASK_EXPLAIN_PREFIX}説明のリクエストを受け付けました — このスレッドで説明します。質問はまだ開いているので、回答はそのあとで大丈夫です。`,
     invalidPrefix: "_:warning: 同時に複数選ばれているため回答として数えていません — どれか 1 つだけ残してください: ",
     answeredVia: (how, who) => `_${how}で回答済み${who ? ` (${who})` : ""}_`,
     howReaction: (glyph) => `リアクション ${glyph}`,
@@ -166,8 +208,10 @@ export const ASK_COPY: Record<AskLang, AskCopy> = {
       "_Reply in this message's *thread* — your reply is the answer (ordinary channel posts are not picked up as answers)._",
     instructionTextHere: "_Reply to this message — your reply is the answer._",
     overflowNote: "_Choices 11 and up have no reaction — answer them with a reply._",
-    otherThread: `${ASK_MARKER_PREFIX}Other — reply in the thread`,
-    otherHere: `${ASK_MARKER_PREFIX}Other — reply to this message`,
+    otherThread: `${ASK_OTHER_PREFIX}Other — reply in the thread`,
+    otherHere: `${ASK_OTHER_PREFIX}Other — reply to this message`,
+    explainLine: `${ASK_EXPLAIN_PREFIX}Explain — press to ask the asker for more detail (not an answer)`,
+    explainNote: `${ASK_EXPLAIN_PREFIX}Explanation requested — it will follow in this thread. The question stays open; answer it after that.`,
     invalidPrefix: "_:warning: Several choices are selected, so this is not counted as an answer — keep only one: ",
     answeredVia: (how, who) => `_Answered by ${how}${who ? ` (${who})` : ""}_`,
     howReaction: (glyph) => `reaction ${glyph}`,
@@ -178,11 +222,36 @@ export const ASK_COPY: Record<AskLang, AskCopy> = {
   },
 };
 
-/** True for the "other" line in either spelling — the shortcode we write, or the
- *  glyph a body hand-edited in the Slack UI can carry. Matched by prefix, not
- *  verbatim, so the copy stays free to change. */
-function askIsOtherLine(line: string | undefined): boolean {
-  return line !== undefined && (line.startsWith(ASK_MARKER_PREFIX) || line.startsWith("❓ "));
+/** The "other" copy pills posted before ➕ carried — the same words under ❓.
+ *  Kept so `askSalvageUnreadable` can still strip it from an old flattened body. */
+const ASK_LEGACY_OTHER_LINES: string[] = ASK_LANGS.flatMap((l) =>
+  [ASK_COPY[l].otherThread, ASK_COPY[l].otherHere].map((s) => ASK_MARKER_PREFIX + s.slice(ASK_OTHER_PREFIX.length)));
+
+/** Which reaction the "other" line names, or null if the line is not one: ➕ or
+ *  ❓ (pills posted before ➕), each as the shortcode we write or the glyph a
+ *  body hand-edited in the Slack UI can carry. Matched by prefix, not verbatim,
+ *  so the copy stays free to change. */
+function askOtherLineMarker(line: string | undefined): string | null {
+  if (line === undefined) return null;
+  if (line.startsWith(ASK_OTHER_PREFIX) || line.startsWith("➕ ")) return ASK_OTHER_MARKER;
+  if (line.startsWith(ASK_MARKER_PREFIX) || line.startsWith("❓ ")) return ASK_MARKER;
+  return null;
+}
+
+/** True for the explain line, in either spelling. Matched by prefix, like the
+ *  other line — used where position alone identifies it (under ❓). */
+function askIsExplainLine(line: string | undefined): boolean {
+  return line !== undefined && (line.startsWith(ASK_EXPLAIN_PREFIX) || line.startsWith("ℹ️ "));
+}
+
+/** True only for this language's explain line AS WRITTEN (either spelling of
+ *  the marker). For a free-text question, where nothing but position separates
+ *  the explain line from the body above it: a body whose own last line starts
+ *  with ℹ️ must not be read as the pill, so the copy has to match exactly. */
+function askIsExplainCopy(line: string | undefined, c: AskCopy): boolean {
+  if (line === undefined) return false;
+  const norm = line.startsWith("ℹ️ ") ? ASK_EXPLAIN_PREFIX + line.slice("ℹ️ ".length) : line;
+  return norm === c.explainLine;
 }
 
 // The invalid-ballot notice, shared by `ask` and `poll` and written INTO the
@@ -228,6 +297,14 @@ export function applyInvalidNotice(text: string, invalid: string[], lang: AskLan
   return out === text ? text : out;
 }
 
+/** True for the thread note `--wait`/`--waitFor` posts when ℹ️ is pressed, in
+ *  either language. Our own bookkeeping: never an answer, never a note — even
+ *  when the identity that posted it is in the audience (an @here question
+ *  collected with another token). */
+export function askIsExplainNote(text: unknown): boolean {
+  return typeof text === "string" && ASK_LANGS.some((l) => ASK_COPY[l].explainNote === text.trim());
+}
+
 /** True if this line is the notice — parsers skip it when walking up. */
 export function isInvalidNotice(line: string | undefined): boolean {
   return invalidLang(line) !== null;
@@ -242,7 +319,7 @@ export const ASK_RESOLVED_PREFIX = `:${ASK_RESOLVED_MARKER}: `;
 /** Prefix `--void` stamps on a question that should no longer be answered —
  *  expired, superseded, or overtaken by events (無効化). A THIRD state beside open
  *  (`:question:`) and answered (`:white_check_mark:`), on purpose: anything that
- *  keys on "starts with :question:" (the stale-pill reminder, `has::question:`)
+ *  keys on "starts with :question:" (the stale-pill reminder, `has::question: OR has::heavy_plus_sign:`)
  *  stops counting it the moment it is voided, and nothing reads it as answered.
  *  Also seeded as a reaction, so `has::no_entry_sign:` lists every void. */
 export const ASK_VOID_MARKER = "no_entry_sign";
@@ -293,7 +370,7 @@ export function askFlatten(s: string): string {
 /** Question body: the prompt, the numbered choices matching the seeded pills,
  *  and an instruction naming the answer paths this command actually reads.
  *  `askParseMessage` is its inverse — keep the two in step. */
-export function askBuildText(question: string, body: string, reactable: string[], overflow: string[], threadOnly: boolean, lang: AskLang = "ja"): string {
+export function askBuildText(question: string, body: string, reactable: string[], overflow: string[], threadOnly: boolean, lang: AskLang = "ja", explain = false): string {
   const c = ASK_COPY[lang];
   const lines: string[] = [`${ASK_MARKER_PREFIX}*${question}*`];
   if (body) lines.push("", body);
@@ -307,8 +384,10 @@ export function askBuildText(question: string, body: string, reactable: string[]
     // form keeps posted and read-back bytes identical, which is what the
     // round-trip test can actually check. (`poll` already did this.)
     lines.push(...reactable.map((s, i) => `${askPill(i)} ${askFlatten(s)}`));
-    // Directly under the pills, matching the ❓ seeded right after them.
+    // Directly under the pills, matching the ➕ seeded right after them.
     lines.push(threadOnly ? c.otherThread : c.otherHere);
+    // Under ➕, matching the ℹ️ seeded right after it.
+    if (explain) lines.push(c.explainLine);
     if (overflow.length) {
       lines.push("");
       lines.push(...overflow.map((s, i) => `(${i + 11}) ${askFlatten(s)}`));
@@ -321,6 +400,7 @@ export function askBuildText(question: string, body: string, reactable: string[]
     lines.push(threadOnly ? c.instructionReactionThread : c.instructionReactionHere);
   } else {
     lines.push("");
+    if (explain) lines.push(c.explainLine, "");
     lines.push(threadOnly ? c.instructionTextThread : c.instructionTextHere);
   }
   return lines.join("\n");
@@ -334,7 +414,7 @@ export function askBuildText(question: string, body: string, reactable: string[]
  *  decision was made against) and the option line that was chosen. Reported
  *  from real use 2026-10-05: collecting an answer replaced the whole message
  *  with question + answer, and the context of the decision was gone. Only what
- *  no longer applies goes — the options NOT chosen, the ❓ line, the answering
+ *  no longer applies goes — the options NOT chosen, the ➕ (or ❓) line, the answering
  *  instructions.
  *
  *  The head is unchanged on purpose: ✅ prefix, question, stamp, blank, quoted
@@ -405,7 +485,7 @@ export function askSalvageUnreadable(text: string): { question: string; body: st
     for (const instr of [c.instructionReactionThread, c.instructionReactionHere, c.instructionTextThread, c.instructionTextHere]) {
       if (body.includes(instr)) wasAsk = true;
     }
-    for (const fixed of [c.instructionReactionThread, c.instructionReactionHere, c.instructionTextThread, c.instructionTextHere, c.overflowNote, c.otherThread, c.otherHere]) {
+    for (const fixed of [c.instructionReactionThread, c.instructionReactionHere, c.instructionTextThread, c.instructionTextHere, c.overflowNote, c.otherThread, c.otherHere, ...ASK_LEGACY_OTHER_LINES, c.explainLine]) {
       body = body.split(fixed).join(" ");
     }
     const at = body.indexOf(c.invalidPrefix);
@@ -454,7 +534,8 @@ function askDecodeEntities(s: string): string {
 }
 
 export type AskParsed =
-  | { kind: "open"; question: string; body: string; reactable: string[]; overflow: string[]; threadOnly: boolean; lang: AskLang }
+  /** `explain`: the body offers the ℹ️ explain pill (`--explain`). */
+  | { kind: "open"; question: string; body: string; reactable: string[]; overflow: string[]; threadOnly: boolean; lang: AskLang; explain: boolean }
   | { kind: "resolved"; question: string; answer: string }
   /** Voided (無効化). `reason` is the stamp line as written; `supersededBy` the
    *  replacement's link when one was given. */
@@ -594,6 +675,7 @@ export function askParseMessage(text: string): AskParsed {
   // there is the body — kept by the ✅ rewrite.
   let bodyEnd = lines.length - 1;
   if (isInvalidNotice(lines[bodyEnd - 1])) bodyEnd--;
+  let explain = false;
   if (hasChoices) {
     // Walk UP from the instruction line rather than down from the question. The
     // choice block is anchored to the bottom of the body, and scanning downward
@@ -609,7 +691,8 @@ export function askParseMessage(text: string): AskParsed {
       if (lines[i] !== "") return { kind: "other" };
       i--;
     }
-    if (askIsOtherLine(lines[i])) i--;
+    if (askIsExplainLine(lines[i])) { explain = true; i--; }
+    if (askOtherLineMarker(lines[i])) i--;
     const raw: string[] = [];
     while (i >= 0) {
       const line = lines[i]!;
@@ -634,10 +717,39 @@ export function askParseMessage(text: string): AskParsed {
     for (let n = 0; n < overflow.length; n++) {
       if (!lines.includes(`(${n + 11}) ${overflow[n]}`)) return { kind: "other" };
     }
+  } else if (lines[bodyEnd - 1] === "" && askIsExplainCopy(lines[bodyEnd - 2], c) && lines[bodyEnd - 3] === "" && bodyEnd - 3 >= end) {
+    // A free-text question's explain line: blank, the line, blank, instruction
+    // — and the line is our copy verbatim. A body that merely ENDS on a line
+    // starting with ℹ️ (a question built without --explain) stays body.
+    explain = true;
+    bodyEnd -= 2;
   }
 
   const body = lines.slice(end + 1, bodyEnd).join("\n").replace(/^\n+|\n+$/g, "");
-  return { kind: "open", question, body, reactable, overflow, threadOnly, lang };
+  return { kind: "open", question, body, reactable, overflow, threadOnly, lang, explain };
+}
+
+/** The marker reaction `ask` seeded on an open question: ➕ when its other line
+ *  says ➕, else ❓ (a free-text question, or a pill posted before ➕ — with a ❓
+ *  other line or none at all). What void / edit / the ✅ swap take off. Read
+ *  from the line directly under the last numbered pill, the one place the
+ *  other line can be; null when the text is not an open ask.
+ *
+ *  Separate from `askParseMessage` so the parse result keeps its shape. */
+export function askSeedMarker(text: string): string | null {
+  const p = askParseMessage(text);
+  if (p.kind !== "open") return null;
+  if (!p.reactable.length) return ASK_MARKER;
+  const lines = text.split("\n");
+  const last = askPill(p.reactable.length - 1);
+  const k = ASK_KEYCAPS[p.reactable.length - 1]!.glyph;
+  // The last pill line is the LAST line opening with that keycap: the block is
+  // anchored to the bottom, and a body line can start with the same keycap.
+  let at = -1;
+  for (let i = lines.length - 1; i >= 0; i--) {
+    if (lines[i]!.startsWith(`${last} `) || lines[i] === last || lines[i]!.startsWith(`${k} `) || lines[i] === k) { at = i; break; }
+  }
+  return (at >= 0 ? askOtherLineMarker(lines[at + 1]) : null) ?? ASK_MARKER;
 }
 
 /** Did a free-text reply actually PICK one of the offered choices?