memory: snapshot — 2026-10-06 fv-ml1 rebalance, backup checker, Scriberr diarization, albok 0.1.12, gateway retention; in-flight compacted; 17 entries archived

2026-10-06 21:45:09 -07:00
parent 0f6c7a0912
commit 3a9eca354a
25 changed files with 936 additions and 912 deletions
@@ -0,0 +1,12 @@
+# `[2026-09-27]` Worldtree reward path: code + config live (Prime)
+
+(Moved out of the in-flight section at the 2026-10-06 snapshot.)
+
+- `d8726a13` (Domari's Skywork/Selene fix) was ALREADY on origin/main when Prime said to push it: it
+  was pushed as part of `79cce92f` at 1221. Demo runs image `79cce92f`. **Personal still runs
+  `51168a2e`**, which is older and lacks the fix; its image follows worldtree CI, never a manual up.
+- `deploy-wt-config` deployed demo and personal (1437): `providers.yaml` `reward_models.scalar-judge`
+  (6d4ac44), plus a77639d's corrected selene description, which had never reached the hosts. Both
+  are healthy, with 0 drift. It is inert on personal until that image picks up d8726a13.
+- worldtree-instance-configs: its 6 long-unpushed commits (53349f8…6d4ac44, Aug 2 to Sep 27) were
+  **pushed on Prime's go-ahead** (a9d091e..6d4ac44). Origin, the repo and both hosts now agree.