scaffold: hub-and-spoke layout, 4-network topology, 13 stack stubs

Initial structure for R&D infrastructure:

- stacks/ — 13 reusable, runnable stack stubs (kebab-case)
  cloud-and-edge: node-red, influxdb, grafana, keycloak, portainer,
                  nginx-proxy, mqtt, postfix
  cloud-only:     wireguard-server, gitea, jenkins, sql (postgres stub)
  edge-only:      wireguard-client

- cloud/ — single central hub composition with 4 networks
           (edge, app, data internal, mgmt) and include: stubs
- sites/ — per-plant edge folders (template README only for now)
- docs/architecture.md — hub-and-spoke + ingress + segmentation rationale

Network model: only nginx-proxy (80/443/8883) and wireguard-server
(51820/udp) publish ports on the cloud host. Edge nginx publishes
80/443 on plant-LAN interface only. MQTT cloud-side via nginx stream
proxy; MQTT edge-side internal-only; Postfix outbound-only.

OT layer (OPCUA, PLCs) is out of scope for this repo.

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

stacks/node-red/compose.yml

@@ -0,0 +1,20 @@
+# node-red — flow-based automation runtime + editor
+# Networks: app
+# UI: internal port 1880 → reverse-proxied through nginx-proxy
+
+services:
+  node-red:
+    image: nodered/node-red:4
+    restart: unless-stopped
+    networks: [app]
+    volumes:
+      - node-red-data:/data
+    environment:
+      TZ: ${TZ:-Europe/Amsterdam}
+    # TODO: Keycloak OIDC adapter; preinstalled modules; CONTRIB allow-list
+
+networks:
+  app:
+
+volumes:
+  node-red-data: