feat(svos): v0.0.20 UI 0.0.24 published on nh3-svos (stronger look default, 125 s draft wait); no restart

2026-10-19 00:56:31 -07:00
parent 5be01a8744
commit 87ddd9c5f3
2 changed files with 15 additions and 1 deletions
@@ -23,6 +23,20 @@ configuration, enrollment and acceptance.
 | App-consistent hook | svos-dev's `/etc/qemu/fsfreeze-hook.d/50-svos` stops the SVOS services on freeze and restarts the ones that were running on thaw. ⚠ **Debian's qemu-ga does NOT run fsfreeze hooks unless configured** (no `-F` in the unit, no `qemu-ga.conf` by default). Here `/etc/qemu/qemu-ga.conf` points it at **`/usr/local/sbin/fsfreeze-dispatch`** (`configs/qemu-ga/fsfreeze-dispatch`), which unlike the stock `/etc/qemu/fsfreeze-hook` propagates failure: if a freeze hook fails, it thaws that hook and the completed ones and exits 1, so qemu-ga refuses the freeze. **Live drill 2026-10-05 1952–1953 (services running):** quiesced backup `vm/111/2026-10-06T02:52:11Z` → kernel+interface down ~1–2 s, back by themselves, health ok. Refused freeze (temporary `60-drill-refuse` after 50-svos, since removed) `vm/111/2026-10-06T02:53:03Z` → the dispatcher unwound and restarted the services, and then **⚠ vzdump did NOT abort: it logged `ERROR: unable to freeze guest fs`, backed up UNFROZEN (crash-consistent, app live), and reported `Backup job finished successfully`, rc 0.** Both images mapped from PBS and mounted read-only (`ro,noload`) on nh3-pve-2, never booted: `svos.db` integrity ok (each image still carries its ~0.9 MB WAL: keep `-wal` with the db when restoring), interface `pins.sqlite3` integrity ok, config/key/config-generation hashes equal live, table counts equal live except `events`. **Monitoring:** `scripts/check-backup-freshness.sh` now reads the LOG of every OK vzdump task and reports ERROR lines; a freeze/thaw error is an APPLICATION-CONSISTENCY FAILURE, verdict **DEGRADED, exit 4** (alerted by the daily wrapper to infra-hermes). nh3-pve-2 was not in the check's node lists at all before 2026-10-05; it is now. Drill B is acknowledged by UPID in the script |
 | Monitoring | Beszel native agent 0.18.7 (`playbooks/beszel-native.yaml`, `configs/beszel-agent/hosts/nh3-svos.env`), hub system `t6y646ifa3x7xxv`, alerts CPU>95%/15m, Disk>85%/5m, Memory>90%/10m, offline/2m. Up 2026-10-05 |

+## Release 81cc5a2 / v0.0.20, stronger look by default + the /tasks draft wait — UI-only publish (2026-10-19 0055; Prime's "deploy it" via svos-dev, threads `01M59JF8Z900KCHP5CJ98F90BW` / `01M59JHRV294CVS0BCMHQR96XY`)
+
+- **Push:** Prime pushed main (`12f2eb2`, one docs commit past the release) and the tag `v0.0.20` → `81cc5a21dfab` himself.
+- **Kit:** kernel 0.0.20 wheel (a version bump only) and UI 0.0.24 from a clean archive of the tag; everything else carried from 91e9f2d.
+  Kit sha256 `e81fadd8…`. Playbooks: `nh3-svos-81cc5a2-v0.0.20-stage.yaml`, then `…-v0.0.20.yaml`.
+- **Publish:** `current → 81cc5a2`, then `svos-front-inventory`. UI handle `/assets/index-Cm1ek0Xu.js` + `/assets/index-CNudli_R.css`
+  (the CSS is unchanged); 91e9f2d is the previous handle. Nothing restarted and there was no card. The processes still map 15c2d04 (kernel,
+  knowledge, judge, voice) and 6d4cb1c (interface).
+- **What it fixes:** the /tasks draft. Each of Prime's four propose calls at 0050–0053 came back `ok` in 12–20 s, but the page's shared
+  request helper (`web/src/lib/notification-http.ts`) aborted at 10 s and showed "Outcome not confirmed". 0.0.24 waits 125 s.
+- **Verified from the served bundle:** the build id is `81cc5a2`, and it contains `125e3`. The look comes from `?look=`, else `stronger` (read at source
+  in `Yggdrasil.svelte`). Seeing it render needs a browser.
+- **Rollback:** `current → releases/91e9f2d`, then `svos-front-inventory`.
+
 ## Release 91e9f2d / v0.0.19, U21 working look — UI-only publish (2026-10-19 0037; Prime's "push it now" in-session; svos-dev thread `01M59H5W335E6W5JP67M6Y6SE7`)

 - **Push:** origin `main` already named 91e9f2d by the time of the push; infra-ops pushed the tag `v0.0.19` → `91e9f2d70c5e` at 0037.