feat(portainer): standalone deploy with published 9443 for early ops access

Bring up portainer first as the operator console — before nginx-proxy + TLS
are wired. Self-signed UI on tcp/9443, edge-agent tunnel on tcp/8000.

Once nginx-proxy lands, ports get commented out and access shifts to
https://portainer.wbd-rd.nl/ behind the wildcard cert. The :9443 direct
access remains as commented config for emergency ops if nginx is down.

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

stacks/portainer/compose.yml

@@ -1,15 +1,21 @@
-# portainer — container management UI
+# portainer — container management UI (operator console)
 # Networks: mgmt
+#
+# Standalone deploy publishes 9443 directly so you have a GUI from day 1,
+# before nginx-proxy + TLS are wired up. Once nginx-proxy is up, comment
+# the `ports:` block and access via https://portainer.wbd-rd.nl/.
 
 services:
   portainer:
     image: portainer/portainer-ce:2.21.4
     restart: unless-stopped
     networks: [mgmt]
+    ports:
+      - "9443:9443"          # HTTPS UI, self-signed cert (early-stage direct access)
+      - "8000:8000"          # Edge-agent reverse tunnel (for edge sites)
     volumes:
       - portainer-data:/data
       - /var/run/docker.sock:/var/run/docker.sock:ro
-    # TODO: edge-agent on each site connected back to this central portainer
 
 networks:
   mgmt: