Onboard: auto-enable systemd lingering on Linux

docs/gateway.md

@@ -188,6 +188,14 @@ Then enable the service:
 systemctl --user enable --now clawdbot-gateway.service
 ```
 
+**Alternative (system service)** - for always-on or multi-user servers, you can
+install a systemd **system** unit instead of a user unit (no lingering needed).
+Create `/etc/systemd/system/clawdbot-gateway.service`, set `User=` and
+`WorkingDirectory=`, then enable with:
+```
+sudo systemctl enable --now clawdbot-gateway.service
+```
+
 ## Supervision (Windows scheduled task)
 - Onboarding installs a Scheduled Task named `Clawdbot Gateway` (runs on user logon).
 - Requires a logged-in user session; for headless setups use a system service or a task configured to run without a logged-in user (not shipped).

docs/setup.md

@@ -109,6 +109,18 @@ pnpm clawdbot health
 - Keep `~/clawd` and `~/.clawdbot/` as “your stuff”; don’t put personal prompts/config into the `clawdbot` repo.
 - Updating source: `git pull` + `pnpm install` (when lockfile changed) + keep using `pnpm gateway:watch`.
 
+## Linux (systemd user service)
+
+Linux installs use a systemd **user** service. By default, systemd stops user
+services on logout/idle, which kills the Gateway. Enable lingering:
+
+```bash
+sudo loginctl enable-linger $USER
+```
+
+For always-on or multi-user servers, consider a **system** service instead of a
+user service (no lingering needed). See `docs/gateway.md` for the systemd notes.
+
 ## Related docs
 
 - `docs/gateway.md` (Gateway runbook; flags, supervision, ports)