feat(svos): v0.0.18 live on nh3-svos — interface 0.0.7 (U20 settings) + UI 0.0.22; card approved 2352:16; kernel process left on identical 0.0.17 code

This commit is contained in:
vh
2026-10-18 23:52:56 -07:00
parent 16603fe70b
commit f281bfb830
2 changed files with 23 additions and 2 deletions
+2 -2
View File
@@ -1,6 +1,6 @@
# Persistent memory — eshpfi-management
_Last updated: 2026-10-18 ~2300 (SVOS v0.0.17 deployed and verified by events). Previously 2026-10-18 ~2125 (snapshot for clear: SVOS v0.0.16 + judge live, v0.0.17 pushed not deployed; albok u6 done; Worldtree b195; asset-engine retired). Previously: 2026-10-14 (snapshot for clear, elway note updated: SVOS v0.0.11 live, pewpewstudio deployed, albok inbox live, decision seat on h2o; earlier: the h2o swap saga, U13.)_
_Last updated: 2026-10-18 ~2355 (SVOS v0.0.18 live; v0.0.17 deployed ~2255). Previously 2026-10-18 ~2125 (snapshot for clear: SVOS v0.0.16 + judge live, v0.0.17 pushed not deployed; albok u6 done; Worldtree b195; asset-engine retired). Previously: 2026-10-14 (snapshot for clear, elway note updated: SVOS v0.0.11 live, pewpewstudio deployed, albok inbox live, decision seat on h2o; earlier: the h2o swap saga, U13.)_
> **Always check for `/tmp/infra-ops-handoff.md`** — if it exists and its
> `Written:` stamp is under **8 hours** old, read it (it carries the in-flight
@@ -122,7 +122,7 @@ _As of 2026-10-18 ~2125 PT. The newest subsection is first; older subsections ca
- **Nothing is mid-action.** No ops-log claims held, no background watchers. eshpfi `main` is pushed (standing push since 2026-10-13); vh/worldtree-instance-configs `main` also has STANDING push since 2026-10-16 (Prime; auto-memory `feedback_git_autonomous`). On Prime's word ~2120 10-18: svoperatingsystem `main` + tag `v0.0.17` (15c2d04) and dotfiles `f909dcf` pushed. ⚠ The working tree and index are shared with infra-hermes, albok-dev and subagents: commit with `git commit -- <paths>` and read `git log origin/main..main` before pushing. `graphify-out/GRAPH_REPORT.md` stays modified on purpose.
- **SVOS v0.0.17 (15c2d04) LIVE since 10-18 2255** (Prime's "deploy now" 2235 via svos-dev, thread `01M595YP8R62Y665C38MHPH6YX`): kernel 0.0.17 + UI 0.0.21 on nh3-svos, config gen `29bc36bf074b8245` (the six runtimes' prompt/working/window), voice `utterance_seconds = 60`; nh3-dev `current → 15c2d04`, only svos-terminal 0.0.6 restarted. No card: terminal revision 6 changes only `version`, so it pinned silently. Verified: 13 `seat/activity_changed` events at 2255:13 (ops-infra working = the positive control, 12 waiting; dev-ldp stays unknown, its 14-day-old claude matches neither mark). Not verified by infra-ops: GET /seats (needs a principal) and the hero "Fleet · working · N" (Prime's eyes). Rollback: servers/nh3-svos/README.md § Release 15c2d04.
- **SVOS v0.0.18 (6d4cb1c, U20 settings) STAGED on nh3-svos 10-18 2324, NOT cut over** (svos-dev thread `01M59D7NTZNN75SRP0M4ZQF91A`): kit built from the LOCAL tag (origin had only 15c2d04 at 2323); `/opt/svos/releases/6d4cb1c` installed, check-config ok, current still 15c2d04. Cutover = `playbooks/svos-releases/nh3-svos-6d4cb1c-v0.0.18.yaml` (current + front door, then ONLY svos-interface restarts). Two gates: origin's v0.0.18 must name 6d4cb1c64de0 (`git ls-remote`), and Prime must be AT THE BOARD — app-interface 0.0.7 adds verbs, so its card holds the whole interface (wrong-revision) until approved; 15-min expiry. After it: Prime's two grants on ns:interface-settings (read; write autonomous). Go = Prime's word, on svos-dev's thread or in this session (either counts). At cutover, the README release section MUST say the kernel process stays on 15c2d04's code and reports 0.0.17 until its next restart (identical code; svos-dev asked).
- **SVOS v0.0.18 (6d4cb1c, U20 settings) LIVE since 10-18 2352** (thread `01M59D7NTZNN75SRP0M4ZQF91A`): infra-ops pushed svoperatingsystem main + tag on Prime's in-session "push it" (his own push never landed). Interface 0.0.7 + UI 0.0.22; only svos-interface restarted; card approved by Prime 2352:16 (via Matrix), interface down 30 s. ⚠ The kernel process still runs 15c2d04's code and reports 0.0.17 until its next restart (identical code). **Open, Prime's:** the two `ns:interface-settings` grants (read; write autonomous), then the /settings and panel checks plus his listening test. Details + rollback: servers/nh3-svos/README.md § Release 6d4cb1c.
- **SVOS (before v0.0.17): v0.0.16 `b51aa5e` on nh3-svos (10-18 1634–2254)** with app-judge (drafting gen-large; six local task models; `[tasks].judge` on, gen `13241a40`); nh3-dev on `3726d73`. Card audio VERIFIED 10-18 (3/3, 4.5–5.5 s). voice.toml `utterance_seconds` was 30 until v0.0.17 (the old web client refused >30); 60 since. **Open:** one drafted scratch task from /tasks (Draft → launch → approve; expect routing, admitted, routed, launching, started) — verifies v0.0.14's gate, the hermes query-file route and U19; Prime must launch it (every spawn is an owner card). Details + rollback material: servers/nh3-svos/README.md.
- **Worldtree:** all three on v1.0.0b195 `a416ac01c5a2` since 1112 10-16; Matrix bridge profile-gated (`COMPOSE_PROFILES=matrix` on demo + personal box .env; pinned none, renders api only). Retired-config strips DONE (demo `2240110`, personal `4d1aae2`). ⚠ Pinned's seeded host config dir `/opt/worldtree-pinned/config` is NOT tracked in vh/worldtree-instance-configs and `deploy-wt-config` refuses pinned: capture it. The daily memory gate keeps its harness scratch since 10-18 (`--keep-data`, `~/.local/state/wt-memory-gate-batch/scratch/<batch>/`, 14-day user tmpfiles); 10-18 PASS. Keep defaults `library:` (thread `01M4WA58P2M001K1420NN72WFM`).
- **Decision seat = h2o-lightning-4b (production, Prime 1805 10-13: fix forward, no INC fallback).** The one open margin is the judge's personal-question reading (h2o 18 vs INC 6 on fleet/memory); albok-dev re-fits it forward in small batches on the live seat.