A user unit's default PATH lacks ~/.cargo/bin, so every zellij call from
app-terminal failed to launch (rc 127 under the unit's environment), and the app
reported degraded from the U13 cutover on. With PATH set, the kernel logged
app-terminal up at 15:56:40Z; the pinned manifest is unchanged and no card was
raised.
- configs/svos-apps/nh3-dev/: user units for svos-terminal (running),
svos-postoffice, svos-miranda, svos-agent (installed, not yet started).
- configs/svos-front/Caddyfile: svos-terminal.phasefinal.com upstreams to
https://svos-seathost.nh3.phasefinal.com now that app-terminal runs on nh3-dev.
- configs/fv-ml1-sol/: an nh3-dev user unit holding fv-ml1's BMC SOL session
into the journal; fv-ml1's kernel console goes to ttyS1 (the SOL port,
marker-tested) from its next boot (ZFSBootMenu commandline on zroot/ROOT).
Prime approved svos-dev's U13 pre-edit ask (2026-10-10 1639).
- B1: release afab123 on nh3-svos (kernel 0.0.9, migration 11->12) after a
vzdump and an offline svos.db copy; app-terminal and app-postoffice held on
b588510 by drop-ins until the edit.
- B2: --app-listen 127.0.0.1:8410 (drop-in) fronted by Caddy as
svos-kernel.phasefinal.com on the LAN, allowlisted to nh3-dev; the path list
adds /auth/kernel-key, which every connector client needs. DNS rewrite on
the three internal AdGuards.
- B3/B4: svos-seathost (-> :8404) and svos-highseat (-> :8773) on nh3-dev's
fleet Caddy, allowlisted to nh3-svos; /opt/svos apps env on nh3-dev with
svos-postoffice[push] (althing-core 3.7.0 from althing 7a2a1c1) and
svos-terminal. The fleet Caddyfile is now tracked in configs/.
vh