docs(albok-service): all wings migrated to generation collections; 0.1.10 rollback now needs a full reindex
This commit is contained in:
@@ -12,7 +12,7 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
|
||||
between walks; the Nemi timer now fires at :03). infra-ops deployed it at albok-dev's ask (althing 8199), from a clean archive
|
||||
of vh/albok `751a729` (tag albok-service/v0.1.12). It is the heid bug-hunt fold over unit 4.1 (contract rev 1.10). No route,
|
||||
config or schema change. Rollback: `compose.yaml.pre-0.1.12` (0.1.11) stays free even after a reindex, because 0.1.11 and
|
||||
0.1.12 share the generation layout. The 0.1.10 caveat below still applies.
|
||||
0.1.12 share the generation layout. ⚠ **Since 2026-10-06 ~1530, EVERY wing is migrated** (fleet/memory g3, fleet/stash g1, personal/agent-feedback g1, personal/notes g1; the unsuffixed collections are gone), so a rollback to 0.1.10 now needs a reindex of every wing on 0.1.10 first (~23–27 min for fleet/memory). albok-dev's after-measurement under reindex: 0 mismatches in 15,176 samples, p95 1.42× idle. The 200-object-load check came in at 2.01× against a 2× bar; that ruling is Prime's.
|
||||
Prior: 0.1.11 @ `sha256:4b641c3e…` (2026-10-06 0202 – 1254) (healthy 0202:23,
|
||||
~20 s down between walks). Deployed by infra-ops at albok-dev's ask (althing 7991; release operator-ratified per albok-dev),
|
||||
built from a clean archive of vh/albok `ffc6d4e` (tag albok-service/v0.1.11). Unit 4.1 read priority: a reindex builds a
|
||||
|
||||
Reference in New Issue
Block a user