update-nanoclaw

# Update NanoClaw Update a customized install through an isolated, resumable transaction. The live checkout is not touched until the staged result has passed validation. Use ordinary conversation for decisions and confirmations. Do not depend on Claude Code, Codex, OpenCode, or any provider-specific question/skill tool. ## Safety contract - Require a clean live checkout. - Stage Git integration, dependency installation, installed-skill refresh, and tests in a separate worktree. - Resolve registry branches from the remote that actually carries them. - Stop the detected service and drain this install's active containers before changing source mounted into agent containers. - Snapshot `.env`, `data/`, `groups/`, `store/`, and manual-service state before cutover. Sockets and other ephemeral special files are intentionally omitted. - Gate every breaking migration and external version-pin move. - Stamp the exact Git commit/tree only after all required work succeeds. - Restart through the detected launchd, user-systemd, system-systemd, or nohup mode; require process state, `data/ncl.sock`, and `bin/ncl groups list`. - Refuse cutover while an unmanaged `pnpm dev`/Node host is running. Stop that process explicitly, update offline, then start it again manually. - On build or health failure, restore Git and the mutable-state snapshot, rebuild the previous image, restart the previous service, and health-check it. ## 1. Load the newest controller without changing the live...