test: expand server protocol scenario coverage

deploy/production/README.md

@@ -4,12 +4,10 @@ This directory is intentionally separate from the development/toolchain Compose
 files. It starts only the Linux server and nginx TLS terminator; Windows clients
 connect through nginx at `/v1/agent`.
 
-Before the first start, create `server.toml` from the authoritative example and
-prepare writable state directories for the runtime image UID/GID `65532`:
+Before the first start, create `server.toml` from the authoritative example:
 
 ```sh
 cp ../../docs/examples/server.toml server.toml
-install -d -m 0700 -o 65532 -g 65532 state run
 chmod 0640 server.toml
 ```
 
@@ -22,7 +20,8 @@ docker compose -f compose.yaml config
 docker compose -f compose.yaml up -d
 ```
 
-Only `state/` and `run/` are persistent/owned deployment data. Back up the
-whole `state/` directory while the server is stopped; `run/` contains only the
-ephemeral local control socket. Do not publish, proxy, or enable JSON-RPC except
-for intentional loopback debugging.
+The stack's `init` container creates the two named volumes with the runtime
+ownership required by the non-root server. `server-data` is the sole persistent
+data volume and must be backed up as a whole while the server is stopped;
+`server-run` contains only the ephemeral local control socket. Do not publish,
+proxy, or enable JSON-RPC except for intentional loopback debugging.