restartlisted

# clawback restart Run `.skills/restart/scripts/restart.sh` from the project root. It is exactly `run_monitor.sh --stop` followed by `run_monitor.sh --detach`: it stops the currently detached proxy (graceful SIGTERM, then SIGKILL after ~5s) and starts a fresh one in the background, printing the new PID and log path. ```bash .skills/restart/scripts/restart.sh # restart with current config .skills/restart/scripts/restart.sh -- --port 8090 --log-level debug .skills/restart/scripts/restart.sh --log-file data/other.log # target a non-default log/pidfile ``` ## Watch mode (`--watch`) `.skills/restart/scripts/restart.sh --watch` restarts once now, then keeps restarting automatically whenever a source file under `src/` or `bin/` changes — handy when another `clawback claude` session is editing the code and you want the proxy to pick it up hands-free. ```bash .skills/restart/scripts/restart.sh --watch # auto-restart on src/ + bin/ edits .skills/restart/scripts/restart.sh --watch -- --port 8090 # passthrough is forwarded to every restart ``` It runs in the foreground and prints each restart as it happens. **Ctrl-C stops watching but leaves the proxy running** (restarts are spawned in their own session, so the signal can't reach them) — same survivability as a plain `--detach`. Mechanics, in case you need to reason about it: - Only `src/` and `bin/` are watched, recursively. The proxy's own writes live under `data/`, w