Optimization of worker workspace size and enablement of headless IPC for ClawTeam

**Implementation PR**: Review guide and verification steps available in PR comments.

Status update from current main: The workspace optimization parts described here are largely present now. clawteam/workspace/manager.py already does the OpenClaw-specific slimming pass and reuses node_modules, .venv, and venv via symlinks instead of copying full dependency trees. Recent docker/nanobot runtime work also improved environment propagation and container-side clawteam bootstrap. What is still missing relative to this issue is the explicit headless worker wrapper / IPC piece (the old scripts/openclaw_worker.sh idea). Leaving this open makes sense, but the issue should be understood as 'headless wrapper / IPC remaining' rather than 'workspace slimming still absent'.

Status update after e2e51ad. This issue is now further along than just workspace slimming. Runtime injection is no longer hard-coded to tmux: - `runtime inject` now resolves the agent's registered backend from the spawn registry - `RuntimeRouter` now dispatches through the registered interactive backend instead of assuming tmux - `WshBackend` now supports live runtime injection via its RPC channel - shared notification rendering moved into a backend-agnostic helper Validation on 2026-04-15: - `ruff check clawteam tests` - `pytest -q` -> `570 passed` What still remains open relative to the original request: - `subprocess` is still a true headless/non-interactive backend and does not support live terminal injection - there is still no separate explicit worker wrapper script in the old `openclaw_worker.sh` sense So I would treat this issue as "interactive-backend IPC now covered; subprocess/headless wrapper still open" rather than a pure workspace-size request.

Follow-up after a3b124c. The remaining subprocess/headless gap is now narrower: - `SubprocessBackend` now implements runtime delivery for headless workers by queueing the rendered runtime notification into the agent inbox - `runtime inject` therefore works for registered subprocess agents instead of failing with "backend does not support runtime injection" - `runtime watch` now explicitly rejects subprocess agents so we do not create an inbox self-routing loop Validation on 2026-04-15: - `ruff check clawteam tests` - `pytest -q` -> `573 passed` What is still not true: - subprocess does not support live terminal keystroke injection, because there is no interactive TUI to target - delivery is mailbox-based headless IPC, not pane/block injection like tmux/wsh At this point I would describe as: workspace slimming complete, interactive IPC covered for tmux/wsh, and headless subprocess delivery available via inbox-backed runtime queuing. The only remaining part would be a separate ex...

Closing this as completed on current `main`. What is now in place: - workspace slimming in `clawteam/workspace/manager.py` - shared dependency reuse via `node_modules` / `.venv` / `venv` symlinks - runtime injection across interactive backends (`tmux` and `wsh`) - headless runtime delivery for `subprocess` agents via inbox-backed queuing - recent container/runtime propagation work for docker-wrapped agents Validation on 2026-04-15: - `ruff check clawteam tests` - `pytest -q` -> `573 passed` The only thing not implemented exactly as originally phrased is a separate legacy-style wrapper script, but the underlying functionality requested by this issue is now present in the main runtime paths. Any future work here should be tracked as a new focused enhancement, not as the original workspace/headless IPC gap.