test: expand server protocol scenario coverage

docs/operations-runbook.md

@@ -5,10 +5,9 @@ describe a Unix-like client, which is outside v1.
 
 ## Deploy and verify
 
-Use either the checked-in Compose deployment or the systemd unit, never both
-for the same server data directory. Start from the annotated
-[`server.toml`](examples/server.toml) and retain `json_rpc.enabled = false`
-unless performing loopback-only debugging.
+Use the checked-in Compose deployment as the sole Linux-server runtime. Start
+from the annotated [`server.toml`](examples/server.toml) and retain
+`json_rpc.enabled = false` unless performing loopback-only debugging.
 
 For Compose, follow the setup in
 [`deploy/production/README.md`](../deploy/production/README.md), set a pinned
@@ -25,12 +24,6 @@ the process is up; `/readyz` becomes successful only after durable recovery.
 The public endpoint accepts only `wss://HOST/v1/agent`. Do not publish port
 6900 or add a proxy route for JSON-RPC.
 
-For systemd, create the `rvbox` service account, install the binary and
-`deploy/systemd/rvbox-server.service`, place a root:`rvbox` owned `0640`
-`/etc/rvbox/server.toml`, then run `systemctl daemon-reload` and
-`systemctl enable --now rvbox-server`. The unit performs `--check-config`
-before every start.
-
 ## Backup and restore
 
 Stop dispatch before copying data: stop the server gracefully, confirm it is