Document the slopbot token in the daemon .env

CURRENT.md

@@ -306,9 +306,9 @@ mobile draft at 390px.
 
 ## Blocked / needs input
 
-- Slopbot live test needs the bot invited to the test guild with View Channels + Read Message
-  History: <https://discord.com/oauth2/authorize?client_id=793887776151306300&scope=bot%20applications.commands&permissions=66560>.
-  The token lives at `/tmp/opencode/slopbot.json` (mode 600, outside the repo) for this session.
+- Slopbot: the bot is invited to the test guild and the intent is enabled. The token lives in
+  `poc/.env` (gitignored, mode 600) and will be replaced when the project goes to prod. The daemon
+  must be restarted to pick it up.
 - The original repo `zib/Veskslop` has a broken server-side git setup. Fetches and clones fail with
   `bad pack header` because a script (`/home/git/.sys_health_s3`) runs on the Veskslop read path.
   The admin must fix it. Use `zib/Veskslop-t` (remote `veskslop-t`) until then. That remote has no

docs/slopbot.md

@@ -45,6 +45,9 @@ channels.
 | `VESKSLOP_SLOPBOT_STATE` | unset | JSON file with `token` and `clientId` |
 | `VESKSLOP_SLOPBOT_CLIENT_ID` | unset | For the invite URL helper |
 
+The daemon loads `poc/.env` at startup (dotenv, overriding shell exports), so the token normally
+lives there. The file is gitignored; keep mode 600 and replace the token for production.
+
 ## Code
 
 | File | Role |

poc/.env.example

@@ -3,3 +3,8 @@ VESKSLOP_TTS_NAME=MicroslopSam
 VESKSLOP_TTS_CMD="/path/to/microslopsam/setup/veskslop-tts.sh {out} {text_file}"
 # Generate with: /path/to/microslopsam/setup/veskslop-tts.sh --voices
 VESKSLOP_TTS_VOICES=""
+
+# Slopbot (media scraping bot). Create the app, enable the Message Content intent,
+# and invite it with View Channels + Read Message History. See docs/slopbot.md.
+VESKSLOP_SLOPBOT_ENABLED=1
+VESKSLOP_SLOPBOT_TOKEN=