docs(albok-service): fleet/memory reindex stood down pending 0.1.8

This commit is contained in:
vh
2026-10-04 08:18:42 -07:00
parent ebe0165acf
commit e8faa74512
+3 -1
View File
@@ -8,7 +8,9 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
⚠ Host port **8392**, because **8390 on nh3-docker is the althing post office**.
- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.7` @ `sha256:0dbb8cc7…` (pinned in `compose.yaml`), built
2026-10-04 ~0755 from vh/albok `64f75dc` (tag albok-service/v0.1.7; pushed by infra-hermes on albok-dev's hand-down via infra-ops).
Deployed between Nemi walks; three wing reindexes followed (fleet/stash, personal/agent-feedback, fleet/memory).
Deployed between Nemi walks; fleet/stash + personal/agent-feedback reindexed on it. fleet/memory reindex was
stood down (HOLD, msg 01M43QWC7HBTYSH8G1NSTJA4F7): the heid re-pass found real drift in 0.1.7 and 0.1.8 follows —
on the new tag, all three reindexes run in the original order.
Prior: 0.1.6 `sha256:2b44c9d4…`, built
2026-10-04 ~0544 from vh/albok `6c1adcd` (tags albok-service/v0.1.6 + core v0.1.4; pushed by infra-ops on Prime's go). 0.1.6 is
the review fold on 0.1.5's search fix: the keyword-index build now takes a lock (two concurrent first queries could cross