What

Add non-blocking pnpm commands for launchd-based desktop startup so automation can restart the local stack without blocking on the Electron process.

Why

pnpm start and pnpm restart intentionally stay attached to the Electron lifecycle, which makes them awkward for agents and other automation that need the command to return immediately.

How

Add a scripts/dev-launchd-bg.sh wrapper that runs the existing launchd start flow inside a dedicated tmux session and exposes matching background-aware start/stop/restart/status/logs commands through root package scripts.

Affected areas

• Desktop app (Electron shell)
• Controller (backend / API)
• Web dashboard (React UI)
• OpenClaw runtime
• Skills
• Shared schemas / packages
• Build / CI / Tooling

Checklist

• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes
• pnpm generate-types run (if API routes/schemas changed)
• No credentials or tokens in code or logs
• No any types introduced (use unknown with narrowing)

Notes for reviewers

This change only adds automation-oriented entrypoints; the existing blocking pnpm start / pnpm restart behavior remains unchanged for manual use.