Deploy ML Intern Slack worker (6)

docs/source/ml-intern/slack-bot.md

@@ -4,7 +4,7 @@ The optional Slack bot runs inside the Chat UI server. Mention **@ML Intern** in
 
 > @ML Intern take the model I linked above and create a Gradio Space for it.
 
-The bot reads that thread (in personal-account sessions, only the owner's messages), then runs the same ML Intern harness used by HuggingChat. It immediately reacts to accepted requests with 👀 before inference. In new threads, its first reply is a persistent **Session status** card showing ⏳ _working..._ while a run is active, or its waiting/finished/stopped state, elapsed time in roughly 10-second increments, and Jobs spending, reservations, and budget. The Stop control lives on that card. Each new invocation gets its own status card below the invoking message; earlier cards retain their final state. Answering questions or resuming the same turn updates that turn’s card. Public updates, questions, and final results appear below it. Existing threads receive the card at the bottom because Slack cannot insert a new reply above older messages. Successful Space creation exposes a separate link labeled as still in setup. Progress updates show no private model reasoning or raw tool arguments. It shows numbered questions (1, 2, 3) and lettered options (A, B, C) in separate sections without repeating the question below the choices. A single-choice question with up to five options has inline buttons with an explicit confirmation, including the exact amount for budget grants. Forms with two to five single-choice questions and up to five options each also show inline choices. Selections refresh directly after each click and are saved as drafts; **Submit answers** appears after every question has a selection and confirms them together, including any budget amount. Changing a selection invalidates an older submit button. Longer or multi-select forms use the **Answer questions** modal. A divider follows the questions and controls; compute totals live in Session status. Inline choices omit that redundant button; an **Other answer** button remains when custom answers are allowed. After submission, the original question card marks confirmed choices with ✅ and removes its controls. Custom answers appear underneath their question. A divider follows the last answer, and the assistant continues below the card without posting a duplicate answer summary. Previously answered private forms are not retroactively published. Results also appear in the thread. Workspace members can mention the bot in an existing channel thread to participate in the same conversation. The original task owner remains the only person who can approve budgets, submit question forms, or stop or resume the task. In shared-token mode, workspace members can use **Download trace** in a channel thread; personal-account traces are owner-only and delivered by DM. DM traces remain private to the DM owner. Participants share that thread's existing approved budget; other threads and DMs remain separate sessions. In channels, the owner's thread replies need no mention; other participants still mention the bot. In DMs, no mention is needed.
+The bot reads that thread (in personal-account sessions, only the owner's messages), then runs the same ML Intern harness used by HuggingChat. It immediately reacts to accepted requests with 👀 before inference and swaps it for ✅ once the run finishes. Replies can tag people who asked the bot something in the thread; other mentions stay plain text. In new threads, its first reply is a persistent status card showing ⏳ _working..._ while a run is active, or its waiting/finished/stopped state, elapsed time in roughly 10-second increments, and Jobs spending, reservations, and budget. The Stop control lives on that card. Each new invocation gets its own status card below the invoking message; earlier cards retain their final state. Answering questions or resuming the same turn updates that turn’s card. Public updates, questions, and final results appear below it. Existing threads receive the card at the bottom because Slack cannot insert a new reply above older messages. Successful Space creation exposes a separate link labeled as still in setup. Progress updates show no private model reasoning or raw tool arguments. It shows numbered questions (1, 2, 3) and lettered options (A, B, C) in separate sections without repeating the question below the choices. A single-choice question with up to five options has inline buttons with an explicit confirmation, including the exact amount for budget grants. Forms with two to five single-choice questions and up to five options each also show inline choices. Selections refresh directly after each click and are saved as drafts; **Submit answers** appears after every question has a selection and confirms them together, including any budget amount. Changing a selection invalidates an older submit button. Longer or multi-select forms use the **Answer questions** modal. A divider follows the questions and controls; compute totals live in the status card. Inline choices omit that redundant button; an **Other answer** button remains when custom answers are allowed. After submission, the original question card marks confirmed choices with ✅ and removes its controls. Custom answers appear underneath their question. A divider follows the last answer, and the assistant continues below the card without posting a duplicate answer summary. Previously answered private forms are not retroactively published. Results also appear in the thread. Workspace members can mention the bot in an existing channel thread to participate in the same conversation. The original task owner remains the only person who can approve budgets, submit question forms, or stop or resume the task. In shared-token mode, workspace members can use **Download trace** in a channel thread; personal-account traces are owner-only and delivered by DM. DM traces remain private to the DM owner. Participants share that thread's existing approved budget; other threads and DMs remain separate sessions. In channels, the owner's thread replies need no mention; other participants still mention the bot. In DMs, no mention is needed.
 
 Public run updates are retained in a separate, cumulative message in the Slack thread. Earlier results, links, and instructions remain readable as the compact status card changes or becomes a question or final response. Only public assistant text is shown, never private reasoning. Long updates continue in additional messages. Public commentary is published before the question it leads to. After an answer, only new commentary appears below it; earlier text is not replayed. Final results are posted as a new message after progress updates.