[woltspace-asharakeh-contrib]

🦊 Bob the Planner (planner): ## TL;DR

Slack becomes a chat connector, the same kind as Telegram. It's one flat DM that works exactly like Telegram: commands, the dog, voice, images and files, reply routing and the inbox. Target: 0.7. The "hold your first message while you pick a wolt" change is now its own PR, stacked on this one.

For humans

The problem. Slack was the last chat app still wired into the lodge by hand, so it behaved differently from Telegram:

• a picker for every new DM;
• one thread per session;
• no commands, no dog, text only;
• it bypassed the inbox.

Every Slack fix was a second copy of something the shared chat code already did.

What changes.

• Slack is one DM with an active wolt.
  • /wolt and /new switch, at the top of the DM. Slack keeps /apps for itself, so the apps list is /wapps.
  • Inside a thread, Slack doesn't run app slash commands, so typed !wolt, !new and !help work everywhere, and buttons cover the rest.
  • Replying in a thread under a wolt's message routes to that wolt.
  • Voice notes, images and files arrive like on Telegram.
  • Your text arrives as plain text: Slack's link, mention and escape markup is removed.
• With no wolt chosen, Slack behaves like Telegram today: the dog answers, or you pick a wolt and send the message again.
• Setup stays the same. The channels.slack config is unchanged. The Slack app gains the commands and files:read scopes and drops assistant:write, then needs one reinstall.

What goes away. Slack threads per session and Slack's "Agent View" processing status. This changes how an existing Slack setup behaves, so it targets 0.7.

For Woltspace contributors

Problem

container/bot/slack_adapter.py (776 lines) imported lodge code and kept its own routing, its own picker queue and its own outbound path. Slack also had special branches in:

• server/notify.py and server/notification_senders.py;
• container/lib/connector_registry.py;
• src/woltspace/channels.py.

That was the opposite of the connector design (RFC #617: "the lodge decides, connectors translate").

Solution

flowchart TD
  SL[Slack DM] <--> P["container/connectors/slack/<br>connector.json + slack_connector.py<br>(translate only)"]
  P <-->|"socket: event / say / edit / ack / send"| CL["chat_lodge, lodge_messages, lodge_commands<br>(shared with Telegram)"]
  CL --> IN[inbox, sessions, dog]
  X["removed: bot/slack_adapter.py,<br>Slack branches in notify, registry, launcher, app"]

Loading

• Slack folder connector (container/connectors/slack/):
  • Socket Mode in the connector process only, talking to the lodge through connector_client.
  • Owner filter: owner message.im only, failing closed.
  • Route field chat_id = the DM channel, so old Slack session records resolve to the flat DM through the generic codec.
  • Plain text in: the owner's text and captions, and a thread parent's text, are unwrapped from Slack markup (<url|label>, <) before command parsing and routing.
  • Text commands use the ! prefix. Slash names that are Slack built-ins are mapped (/wapps → apps).
  • Thread reply under this bot's own message → reply_to.
  • Bot token on downloads: the token is only ever sent to Slack's own file host (https://files.slack.com).
  • Files out: every file that goes out (a notify --file or a dog image) passes the outbox check, and a dog image keeps its own file name.
  • Startup refusal: a manifest owner_pattern refuses to start without a usable owner id, with the remedy.
  • Wolf pings: a default_route_env keeps SLACK_NOTIFY_CHANNEL working.
• Compatibility:
  • notify --slack C [T] and --to slack:C:T normalize to the flat route;
  • the channels.slack config keys are unchanged.

Where to focus

1. The owner-DM fail-closed filter, and reply routing that trusts only this bot's own parent message.
2. Markup normalization at the connector boundary (text, captions, thread parents).
3. The removals: nothing Slack-specific is left in core.
4. The legacy route normalization for stored Slack routes.

Validation

• Tests: test-first throughout, with an independent reviewer's negative tests (all review findings fixed, including five from a maintainer-side read).
• Full suite: 4,065 run, 0 new failures against the base's known list. No new Ruff/ty diagnostics.
• Real Slack workspace, on a lodge running this work:
  • /wolt and /wapps;
  • !wolt in a thread;
  • a voice note;
  • a PDF;
  • a thread reply reaching the right wolt;
  • a link and a mention arriving as plain text;
  • a captioned image;
  • DMs in and out.
• Size against main: production +535/−1,222, tests +585/−1,575, docs, skills and the setup manifest +155/−212, CI +5/−1.

Limits

• Mentions: a mention arrives as the raw user id (@U…), not the display name. That's a possible follow-up.
• Ingress: a connector-to-lodge crash before the inbox stores a message can still lose it, as before.
• Telegram button data: the 64-byte limit fits wolt names up to 50 characters.
• Behaviour changes: Slack voice notes are now opus files; wolf pings to Slack need the connector running; /sessions/new/slack is removed.
• Follow-up PR: the held first message, for every connector, is stacked on this one.