feat(albok-service): 1.0.0a1 (version-only rebuild of 0.1.24; v1 alpha cut)

stacks/albok-service/README.md

@@ -8,7 +8,10 @@ The FastAPI process that owns Albok's buildings-and-wings store (`vh/albok`,
   (`servers/nh3-albok/README.md` says why and what must never be added there). Before that: nh3-docker, 2026-10-02 to 2026-10-04.
 - **URL:** `http://albok.nh3.internal:8392` (= `http://10.100.50.44:8392`). Container port 8390.
   Host port **8392** is kept from nh3-docker, where 8390 was the althing post office, so no client changed.
-- **Image (current):** `gitea.phasefinal.com/pfi/albok-service:0.1.24` @ `sha256:75be71c1…` since 2026-10-16 0917
+- **Image (current):** `gitea.phasefinal.com/pfi/albok-service:1.0.0a1` @ `sha256:6067dfbb…` since 2026-10-16 1046
+  (healthy 1046:36, 8 wings ready). Version-only rebuild of 0.1.24 from vh/albok `0f099e4` (Prime cut the v1 alpha;
+  all four albok packages at 1.0.0a1). No config change. **Rollback:** `compose.yaml.pre-1.0.0a1` (0.1.24), free.
+- **Previous image:** `gitea.phasefinal.com/pfi/albok-service:0.1.24` @ `sha256:75be71c1…` 2026-10-16 0917–1046
   (healthy 0918:04, `/health` 8 wings ready). infra-ops deployed it at albok-dev's ask (althing thread `01M52KF3VM9S3K22A7TWV4DC4A`),
   built from a clean archive of vh/albok `67eabb7` (albok-service 0.1.24, albok 0.1.12). This is unit 6: a locked encrypted wing's
   journal entries are deferred rather than driven into the unmounted mountpoint; accept-head replays them. It shipped with the

stacks/albok-service/compose.yaml

@@ -16,7 +16,7 @@
 #   1513 albok-sealed (encrypted wing personal/sealed, unit 6) likewise; its plaintext exists only while unlocked.
 services:
   albok-service:
-    image: gitea.phasefinal.com/pfi/albok-service:0.1.24@sha256:75be71c1b939dbb050495e6f604a10950bc7dbda0811a5a9e8c6aedc40c48efb
+    image: gitea.phasefinal.com/pfi/albok-service:1.0.0a1@sha256:6067dfbb034d5234794e9114da5a90c7905481de809aca100d69018edba26ae7
     container_name: albok-service
     restart: unless-stopped
     ports: