Agent host: SilverBullet boots into accounts and the vault, not a bare space

SB_NAME alone put SilverBullet 2.11 in single-space mode: no accounts, no
setup wizard, and its /data folder served instead of the vault. The compose
file sets only PUID and PGID now, a test holds it to that, and the host
check fails on a single-space boot.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

deploy/agent-host/check.sh

@@ -10,6 +10,11 @@ bad() { echo "FAIL: $1"; fail=1; }
 cd "$stack" || { echo "FAIL: no $stack"; exit 1; }
 [ "$(sudo docker compose ps --status running -q | wc -l)" -ge 1 ] \
   && ok "SilverBullet is running" || bad "SilverBullet isn't running"
+if sudo docker compose logs --no-color silverbullet 2>/dev/null | grep -q 'boot mode: single-space'; then
+  bad "it booted a single space with no accounts (an SB_* setting?)"
+else
+  ok "it keeps accounts (no single-space boot)"
+fi
 code=$(curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:3000/)
 case $code in 2??|3??) ok "it answers locally ($code)" ;; *) bad "it answers $code" ;; esac
 probe=.nisse-probe-$$

deploy/agent-host/silverbullet/compose.yaml

@@ -8,9 +8,10 @@ services:
     image: ghcr.io/silverbulletmd/silverbullet:2.11.1-slim
     restart: unless-stopped
     environment:
+      # Only these. Any SB_* setting (even SB_NAME) boots a single space with
+      # no accounts, serving /data instead of the vault.
       PUID: "1000"
       PGID: "1000"
-      SB_NAME: Nisse vault
     ports:
       # IPv4 only; setup.sh's firewall lets only the operator's Caddy in.
       - "0.0.0.0:3000:3000"