Prepare for a live account: separate the indexes, and probe new routes live

With .env pointing at the real account, testing against the local instance
became dangerous: process env beats --env-file, so a local smoke run would
crawl fixtures straight into the live index, where a per-course refresh
carries them forward indefinitely. mcp-env.sh now pins its own database
(schulcloud_local) and mirror as well as the instance.

The override publishes the server on MCP_HOST_PORT and takes
CRAWL_INTERVAL_MS from .env, since what_changed can only report what
happened between crawls. The build context leaves out tmp/, which holds a
mirror of the account's files, and local-instance/.

probe checks live what the gap fixes established locally: the /api/v1 course
and user routes, classes, room allowedOperations as an object, and the
preview enums on a real file. A failure there means a feature degrades
rather than breaks.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/LOCAL.md

@@ -14,7 +14,17 @@ curl -s http://127.0.0.1:8080/healthz     # {"status":"ok","sessions":0,"index":
 
 `docker-compose.override.yml` is merged automatically and is **local-only**: it
 publishes the server on `127.0.0.1:8080` and Postgres on `127.0.0.1:55432`, and
-switches crawling to on-demand. On the Pi neither port is published — Caddy
+switches crawling to on-demand. Two `.env` settings adjust it: `MCP_HOST_PORT`
+moves the published port when 8080 is taken, and `CRAWL_INTERVAL_MS` restores a
+crawl timer — worth doing against a real account, because `what_changed` can
+only report what happened between crawls.
+
+After pasting a new `TSC_JWT_COOKIE` into `.env`, **recreate** the container —
+`env_file` is read when the container is created, not on restart:
+
+```bash
+docker compose up -d --force-recreate schulcloud-mcp
+``` On the Pi neither port is published — Caddy
 reaches the container over the Docker network.
 
 Loopback binding is deliberate. The bearer token is the only thing in front of