phase: 28_gateway_agent_proxy

**Phase 28 final pass — complete, 100 % green.** All five tasks were already `complete/`; this pass verified the criteria, re-ran the live half, and did the docs pass.

- Gate `bash .agents/validate.sh` **rc=0**: `1650 passed, 15 skipped`, coverage **98.97 %** (floor 94), `ruff` clean, `pyright` **0 errors**, `node --check` clean, hygiene clean (`/tmp/validate-done.log`).
- Live: `pytest -m live --live` **11 passed**; `./scripts/dev-server.sh status` nine sources `ok`; mTLS re-read of `gateway` → agent **1.2.0**, all three sections `available: true`, 6/6 frontends routed, 11 nginx servers + `$targetBackend`, **19** listeners, no core errors (`data/logs/28-finalpass-live.out`); installed agent file byte-identical to this tree (`b0e9ebf1b718…`).
- Criteria: 1 ✅ pytest/coverage · 2 ✅ three sections over a captured tree, `false`/`null` + one `errors` line each elsewhere with `cpu`/`mem`/`disk_io`/`system` intact · 3 ✅ `AGENT_VERSION` 1.2.0 + SCHEMA names all three · 4 ✅ six fixtures verbatim, capture refuses a bad read, 116 socket address columns hold no globally routable endpoint · 5 ✅ gateway runs 1.2.0 and answers over mTLS (transcript `data/logs/28-task05-rollout.md`, `28-finalpass-live.out`) · 6 ✅ validate · 7 ✅ additive: HEAD's 1.1.0 and this 1.2.0 `collect()`ed over one `--root` are key-for-key equal plus the three new sections, `--no-proxy` equal exactly (`data/logs/verify-28-final.py` → 41 PASS, `28-final-verify.out`).
- Docs fixed (README/AGENTS/Containerfile, all re-green): README's opening said "Four dashboards" above a five-row table and said the new sections are "stored in the snapshot" (they are in the **agent's** document — no `/api` payload, no `sample` row, nothing charts them until phase 29); `Containerfile`'s header still said "three dashboards"; AGENTS's coverage figure (98.94 → **98.97 %**), invariant 6 gained the captured-socket-table identifier rule, the agent bullet gained "phase 28 stops at the wire", and the fleet record names the stash-and-compare control plus the volatile listener count. Full record: `data/logs/NOTES-28-final.md`.
- Deviations: none functional; no git index/history touched, phase files untouched (`PLAN.md` and `complete/` unchanged). `uv pip list --outdated` still lists 4 packages (fastapi 0.153→0.161 etc.) — advisory only, dependencies untouched by this phase, left for a deliberate pass.
- Next pending phase: `.agents/phases/todo/29_gateway_dashboard_page/` (the page that consumes these three sections).

tests/fixtures/gateway_haproxy.cfg

@@ -0,0 +1,57 @@
+# Verbatim /etc/haproxy/haproxy.cfg from gateway-ops, read read-only over the ssh key by
+# ./scripts/capture-gateway-config.sh (AGENTS.md invariant 7: verify against the
+# deployed upstream, never guess its shape).
+# Nothing here is rewritten: it is this fleet's ingress map, and the domains in it are
+# the data — an inbound name and the target it routes to are what these config sections
+# exist to report. Key material appears only as the file paths the proxy reads.
+defaults
+    log     stdout local0 info
+    mode    tcp
+    option  tcplog
+    timeout connect 10s
+    timeout client  30s
+    timeout server  30s
+    timeout tunnel  3600s
+    default-server init-addr last,libc,none
+
+frontend haproxy-22
+    bind :::22 v4v6
+    default_backend gitea-2222
+
+frontend haproxy-2000
+    bind :::2000 v4v6
+    default_backend sec-gitea-2000
+
+frontend haproxy-5201
+    bind :::5201 v4v6
+    default_backend iperf3-5201
+
+frontend haproxy-8080
+    bind :::8080 v4v6
+    default_backend unifi-external-8080
+
+frontend haproxy-25565
+    bind :::25565 v4v6
+    default_backend testcraft-25565
+
+frontend haproxy-25566
+    bind :::25566 v4v6
+    default_backend nimcraft-25566
+
+backend gitea-2222
+    server gitea reeseapps-gitea.reeselink.com:2222 check inter 5s
+
+backend sec-gitea-2000
+    server sec-gitea stackexpected-gitea.reeselink.com:2222 check inter 5s
+
+backend iperf3-5201
+    server iperf3 web.reeselink.com:5201 check inter 5s
+
+backend unifi-external-8080
+    server unifi unifi-external.reeselink.com:8080 check inter 5s
+
+backend testcraft-25565
+    server mc1 minecraft.reeselink.com:25565 check inter 5s
+
+backend nimcraft-25566
+    server mc2 minecraft.reeselink.com:25566 check inter 5s