fix(albok-service): 0.1.4 on nh3-docker (version header from metadata)

stacks/albok-service/README.md

@@ -6,12 +6,10 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
 
 - **URL:** `http://albok.nh3.internal:8392` (= `http://10.100.50.40:8392`). Container port 8390.
   ⚠ Host port **8392**, because **8390 on nh3-docker is the althing post office**.
-- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.3` @ `sha256:92bbf31d…` (pinned in
-  `compose.yaml`), built 2026-10-03 1556 from vh/albok `fc4c97a` (tag albok-service/v0.1.3, pushed; albok core 0.1.2).
-  0.1.3 drops the ingester stamp from the sidecar equivalence check, so a Nemi release no longer re-`updated` the whole fleet.
-  ⚠ Its `X-Albok-Service` header still says **0.1.2**: `albok_service/__init__.py` `__version__` was not bumped (the package
-  metadata says 0.1.3). Reported to albok-dev. Check the running version with `docker exec albok-service python -c "import importlib.metadata as m; print(m.version('albok-service'))"`.
-  Prior: 0.1.2 (`544ecfd`, `sha256:6f91a33f…`) 2026-10-03 0251–1558.
+- **Image:** `gitea.phasefinal.com/pfi/albok-service:0.1.4` @ `sha256:c467c92d…` (pinned in `compose.yaml`), built
+  2026-10-03 ~1612 from vh/albok `3d6bdba` (tag albok-service/v0.1.4; pushed by infra-ops on Prime's go). 0.1.4 takes `__version__`
+  from the installed metadata, so `X-Albok-Service` now matches the release (0.1.3 had said 0.1.2).
+  Prior: 0.1.3 (`fc4c97a`, `sha256:92bbf31d…`, ingester stamp out of equivalence) 1558–~1613; 0.1.2 (`544ecfd`) 0251–1558.
   Built from albok-dev's local commit before the operator pushed it. Verified 2026-10-03 1000 with `git ls-remote`:
   origin's `albok-service/v0.1.2` and `v0.1.2` are `544ecfd`, so the image matches the published tag. Image labels
   carry the full SHA.