CMUX runbooks: launch workers lean + socket needs no setup

[casey-capshaw-rbrk]

Follow-up to #3 (merged). Two field-tested refinements to the CMUX runbooks, based on main.

What this adds

1. Launch pane workers lean. claude --model <id> --strict-mcp-config --mcp-config '{"mcpServers":{}}' (if your agent CLI supports it) gives a worker few/no MCP servers. A large MCP fleet injects enough tool schema to crowd out a worker's context after a handful of file reads — the same bloat that can make an in-process subagent/Task tool unusable, which is why explicit pane workers are the reliable path. In both runbooks' launch steps + the meta/AGENTS.md § Optional extensions model note.
2. Socket wording = routine, no setup. Reframed the cmux identify / socketControlMode lines so they read as a sanity-check, not a config step: the in-pane control socket works out of the box under the default cmuxOnly; config only matters to drive CMUX from outside a pane.

Scope

• 3 files, +30/-10. No new files.
• Fully generic / templated (owner: {{NAME}}, no instance-specific model names or paths). Grep gate clean; kit lint green.

🤖 Generated with Claude Code

[claude]

Typo: "the leg truly needs" — should be "the task truly needs" (matches the parallel wording in Jobs/Delegate an initiative to a CMUX workspace.md: "Add back only a server the task truly needs.").

[claude]

VERDICT: ISSUES

Reviewed the diff (Jobs/Delegate an initiative to a CMUX workspace.md, Jobs/Spawn subagent panes in a CMUX workspace.md, meta/AGENTS.md).

Privacy: clean. No real names, hosts, credentials, or instance-specific content — pure framework guidance (lean-launch MCP config advice, socket-setup clarification). owner: {{NAME}} placeholders remain untouched in both Jobs files.

Schema consistency: clean. No new Jobs added (so no re-indexing needed), no new wikilink targets, frontmatter untouched, index.md/root unaffected.

Doc coherence: one nit — left an inline comment. Jobs/Spawn subagent panes in a CMUX workspace.md line 62 says "Add back only a server the leg truly needs" where the parallel sentence in the Delegate job (and the rest of this doc's terminology) uses "task"/"leg" inconsistently; likely a copy-paste typo for "task."

Everything else — the "launch lean" MCP guidance and the socket-setup clarifications — reads consistently across both Jobs files and the meta/AGENTS.md summary.