1.9 KiB
2026-10-09-u13-ingress-approved
[2026-10-09] APPROVED by Prime (10-09), BUILD DEFERRED until after his snapshot/clear: SVOS app-traffic ingress for U13 (apps on nh3-dev reach the nh3-svos kernel). Shape agreed with svos-dev: (1) kernel --app-listen 127.0.0.1:8410, which never trusts loopback (svos-dev builds it in U9a); (2) a Caddy origin svos-kernel.phasefinal.com on 10.100.50.43, no Basic auth, bearer passed, app paths only, allowlisted to nh3-dev; (3) kernel→bridge over plain LAN HTTP; kernel→seat host (terminal) via nh3-dev's wildcard Caddy svos-seathost.nh3.phasefinal.com (TLS, because the leg carries secrets). nh3-dev is NOT on the mesh; the contracts now say "fleet network". --app-listen is ON MAIN (68c9933, 10-09). It ships in kernel 0.0.9 with schema 11 → 12 (migration 0012 rebuilds dispatches + summons, so the 'schema 11' acceptance line changes and a pre-refresh backup is mandatory). At the cutover the bridge gets three owner-approved runtime grants (app-postoffice → app:app-miranda write, app:app-postoffice write, ns:pages write, all autonomous) and installs as svos-postoffice[push] with althing-core from ~/development/althing in apps-env. Release is cut: svoperatingsystem afab123 (tag v0.0.9): kernel 0.0.9, svos-postoffice 0.0.2, svos-terminal 0.0.3, svos-connector 0.0.7, svos-agent 0.0.3, svos-miranda 0.0.2 (U9a + U5b). The SVOS side of the cutover is written up in docs/operations/u13-svos-edit.md (app listener on nh3-svos, terminal app moved to nh3-dev with [seat_host], bridge on nh3-dev with the converse mapping). Gotchas: the terminal app serves WITHOUT its seat host if the socket or launch dir fails (one stderr line); serve refuses --app-listen on the primary port. Build only when the edit is scheduled (highseat-dev owns the schedule) and NOT before the snapshot; the runbook refresh is ours at deploy. Tracking: svos-dev thread 01M4GPXSBKQHCQ30FVPH4R3N7G.