docs: operator is built from source now

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GmpYHPSLGmXGZMyLpn2Lbe

TODO.md

@@ -19,11 +19,6 @@ Live state as of 2026-09-10. Everything not listed here is deployed and green.
       scan now reaches mail, but the file pass has not finished a full cycle
       since the Milvus rebuild, so no mail has been indexed yet. Watch for
       `[SCAN-*] Mail messages: N seen, M queued`.
-- [ ] **Rebuild the operator image.** Its baked-in `/opt/storage/check.py` has
-      drifted from the host copy: it lacks the `s3:ListBucket` grant (dropping it
-      broke image generation on 2026-09-09) and still resolves the store as
-      `clinical-milvus`. The compose mounts the host copy over it as a stopgap;
-      rebuilding makes that mount unnecessary.
 - [ ] **Apply the restored clinical vector-store compose.** Written, committed and
       validated at `/home/danvics/docker/nextcloud-mcp-server`, deliberately NOT
       applied — `up -d` recreates the live clinical Milvus. Owner's call when.
@@ -35,6 +30,8 @@ Live state as of 2026-09-10. Everything not listed here is deployed and green.
   and the MinIO/separate-etcd requirements.
 - Both Milvus stores keep objects in MinIO; verified end to end on the basic side
   (16 objects in the bucket, rows queryable, collection Loaded).
+- The operator image is built from source (`Dockerfile.operator`), so the drifted
+  `check.py` that broke image generation can no longer be run by accident.
 
 ## Worth knowing