Update root monitoring thread after launch-ready validation

OPEN_THREADS.md

@@ -6,6 +6,7 @@ Repo-specific work belongs in:
 - `Codex/API/OPEN_ITEMS.md`
 - `Codex/Portal/OPEN_ITEMS.md`
 - `Codex/Agent/OPEN_ITEMS.md`
+- `Codex/Monitoring/OPEN_ITEMS.md`
 
 Keep this file short.
 
@@ -48,10 +49,13 @@ Keep this file short.
   - API/control plane/internal bridge/agent/admin services private
 
 ### Monitoring / observability
-- normalize game/dev Alloy monitoring contract across API discovery, agent-written Alloy labels, Prometheus targets, and Grafana dashboards
-- keep dynamic game/dev discovery on API -> sync script -> file_sd and verify automatic add/remove behavior for new containers
-- finish game/dev template cleanup so Alloy is standard and `node-exporter` is removed from those templates
-- keep OPNsense plugin and PBS monitoring as explicit platform exceptions while Linux-managed targets converge on Alloy
+- core lifecycle monitoring is launch-ready
+- `/etc/zlh-monitor` is now the operational monitoring source of truth
+- game/dev monitoring uses API discovery -> monitor sync -> file_sd for lifecycle inventory and add/remove validation
+- container Alloy remote-write to Prometheus `10.60.0.25:9090` is the canonical game/dev metrics path
+- `game-dev-alloy` scrape health also works because container Alloy now listens on `0.0.0.0:12345`
+- remaining future work lives in `Codex/Monitoring/OPEN_ITEMS.md`: centralized logs/Loki and optional OPNsense router-only monitoring
+- keep OPNsense plugin/PBS monitoring as explicit platform exceptions while Linux-managed game/dev targets converge on Alloy
 
 ### Notifications / launch polish
 - email notifications across backend contract + Portal UX