Add the slopbot live check and record the invite blocker

docs/slopbot.md

@@ -60,6 +60,18 @@ channels.
 - The Bot tab shows connection state, the guilds slopbot is in, the active scrape, and the queue.
   It also renders the invite URL from the client ID.
 
+## Live check
+
+```sh
+cd poc
+VESKSLOP_SLOPBOT_ENABLED=1 VESKSLOP_SLOPBOT_STATE=/path/to/slopbot.json \
+  pnpm test:slopbot:live <channelId> [guildId]
+```
+
+The check logs in, prints the bot user and guild count, then fetches one history page and maps it.
+The token is read from the state file or the environment and is never printed. The bot must be
+invited to the guild first (View Channels + Read Message History).
+
 ## Rate limits
 
 discord.js handles per-route buckets and retries `429` and `5xx` internally. The scrape engine adds

docs/testing.md

@@ -177,6 +177,17 @@ Notes:
   locally and point `LD_LIBRARY_PATH` at it.
 - The live start was verified on 2026-09-13 through the web UI route.
 
+## Slopbot live check
+
+The bot core needs a real token and an invite to the test guild. The check logs in, lists guilds,
+and fetches one history page without printing the token:
+
+```sh
+cd poc
+VESKSLOP_SLOPBOT_ENABLED=1 VESKSLOP_SLOPBOT_STATE=/path/to/slopbot.json \
+  pnpm test:slopbot:live <channelId> [guildId]
+```
+
 ## Sanctioned live target
 
 The only permitted live-send target is user **zzib** (`177117296140091393`). Send a test message