Add the slopbot scaffold and discord.js dependency, unused

docs/slopbot.md

@@ -29,7 +29,7 @@ libraries stands.
    `attachments`, and `embeds` in both gateway events and REST history responses. Unverified apps
    in under 100 servers can enable it in the portal.
 3. Invite the bot with the `bot` and `applications.commands` scopes and the minimum permissions:
-   View Channels, Read Message History, Send Messages (for status replies), Embed Links.
+   View Channels and Read Message History. The bot never sends, so it needs no more.
 4. Store the token in the daemon state file `slopbot.json` (mode 600) or `VESKSLOP_SLOPBOT_TOKEN`.
    Never commit it. The action log redacts token-shaped strings as before.
 
@@ -41,7 +41,8 @@ channels.
 | Setting | Default | Purpose |
 | --- | --- | --- |
 | `VESKSLOP_SLOPBOT_ENABLED` | `0` | Kill switch, off by default |
-| `VESKSLOP_SLOPBOT_TOKEN` / `slopbot.json` | unset | Bot token |
+| `VESKSLOP_SLOPBOT_TOKEN` | unset | Bot token (preferred) |
+| `VESKSLOP_SLOPBOT_STATE` | unset | JSON file with `token` and `clientId` |
 | `VESKSLOP_SLOPBOT_CLIENT_ID` | unset | For the invite URL helper |
 
 ## Code
@@ -68,4 +69,6 @@ Slopbot runs with the faster bot budget; the puppet backend uses the slower user
 
 ## Status
 
-Design approved 2026-09-16. Implementation at checkpoint C4 in [CURRENT.md](../CURRENT.md).
+Design approved 2026-09-16. Scaffold added 2026-09-16: `media-scrape/slopbot/` (config loader and
+invite helper) and the discord.js dependency in `media-scrape/package.json`. Unused until
+checkpoint C4 in [CURRENT.md](../CURRENT.md).