Slack: add some fixes and connect it all up

docs/configuration.md

@@ -327,14 +327,13 @@ Slack runs in Socket Mode and requires both a bot token and app token:
       sessionPrefix: "slack:slash",
       ephemeral: true
     },
-    replyToMode: "off",      // off | first | all
     textChunkLimit: 4000,
     mediaMaxMb: 20
   }
 }
 ```
 
-Clawdis starts Slack only when a `slack` config section exists and both tokens are set (unless `slack.enabled` is `false`). Provide `SLACK_BOT_TOKEN` + `SLACK_APP_TOKEN` env vars if you prefer. Use `user:<id>` (DM) or `channel:<id>` when specifying delivery targets for cron/CLI commands.
+Clawdis starts Slack when the provider is enabled and both tokens are set (via config or `SLACK_BOT_TOKEN` + `SLACK_APP_TOKEN`). Use `user:<id>` (DM) or `channel:<id>` when specifying delivery targets for cron/CLI commands.
 
 Reaction notification modes:
 - `off`: no reaction events.

docs/slack.md

@@ -121,7 +121,6 @@ Slack uses Socket Mode only (no HTTP webhook server). Provide both tokens:
       "sessionPrefix": "slack:slash",
       "ephemeral": true
     },
-    "replyToMode": "off",
     "textChunkLimit": 4000,
     "mediaMaxMb": 20
   }
@@ -137,13 +136,6 @@ Tokens can also be supplied via env vars:
 - Channels map to `slack:channel:<channelId>` sessions.
 - Slash commands use `slack:slash:<userId>` sessions.
 
-## Reply threading
-Slack replies can be threaded when reply tags are present and `slack.replyToMode` is enabled.
-
-```json
-{ "slack": { "replyToMode": "first" } }
-```
-
 ## Delivery targets
 Use these with cron/CLI sends:
 - `user:<id>` for DMs