docs(albok-service): fleet/memory reindex result on 0.1.8; reindex path shape note
This commit is contained in:
@@ -9,8 +9,9 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
|
||||
- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.8` @ `sha256:239f900e…` (pinned in `compose.yaml`), built
|
||||
2026-10-04 ~1115 from vh/albok `e653c29` (tag albok-service/v0.1.8; heid re-pass fixes over 0.1.7: keyword-index
|
||||
lock mismatch, journal-stranding replay path, bypassable 400, link-kind handling in the collapse). fleet/memory
|
||||
reindexed on it per albok-dev (their 0.1.7 stash + agent-feedback reindexes stand — 0.1.8 does not change what a
|
||||
reindex writes).
|
||||
reindexed on it per albok-dev (10,849 obj / 15,418 chunks, 1613.6 s, clean, commit 563dcae; their 0.1.7
|
||||
stash + agent-feedback reindexes stand — 0.1.8 does not change what a reindex writes).
|
||||
⚠ reindex path shape: POST /buildings/<building>/wings/<wing>/reindex (the wing segment is required).
|
||||
Prior: 0.1.7 `sha256:0dbb8cc7…` (64f75dc), fleet/stash + personal/agent-feedback reindexed on it.
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user