chore: record pre-existing uncommitted repository state

Snapshot of the in-flight state that already existed, identically, in both
this worktree and the main checkout before this session began: the initial
HTTP Client platform implementation (previously untracked), the redis-lab
removal, and the JPA / object-storage / notification integration work.

Kept separate from this session's HTTP Client review response, which lands
in the following commit, so the two bodies of work stay reviewable apart.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docker-compose.yml

@@ -53,6 +53,20 @@ services:
     tmpfs:
       - /tmp:mode=1777,size=128m
       - /var/tmp/heap:mode=1777,size=512m
+    # ---- Fileserver storage volume ------------------------------------------
+    # A named volume, not a tmpfs and not the read-only root. The Fileserver platform's default
+    # storage root is /var/lib/backend/files, and with a read-only root and no mount there was
+    # nowhere on the image it could legally write: enabling the capability failed on its first
+    # upload rather than at startup. The volume is declared unconditionally because a volume
+    # nobody writes to costs nothing, while a missing one costs an outage.
+    #
+    # Ownership: the image runs as uid/gid 1000 (see src/Dockerfile). Docker initialises a fresh
+    # named volume from the image path's ownership, so the directory is created in the image with
+    # that owner; a pre-existing volume or a host bind mount must be chowned to 1000:1000 by the
+    # operator, or every write is refused with a permission error the application reports as
+    # STORAGE_UNAVAILABLE.
+    volumes:
+      - fileserver-data:/var/lib/backend/files
     # ---- Memory limit (D4) --------------------------------------------------
     # Must be set so -XX:MaxRAMPercentage=75 can compute a meaningful heap bound.
     mem_limit: 512m
@@ -78,3 +92,8 @@ services:
       start_period: 60s
       retries: 3
     restart: unless-stopped
+
+volumes:
+  # Survives container replacement, which is the point: published content outlives the process
+  # that wrote it. Back this with real storage in any deployment that keeps files.
+  fileserver-data: