vhaudiquet
99ecceacb5
The claw's side of §10: one bridge per process, established at first agent build and never re-read — the claw is single-instance and its servers are stateful across calls, so a mid-process rewire would orphan running sessions' socket paths. The global `mcp.yaml` is the claw's config scope (no profiles here); the off switch is `disabled_mcp_servers` beside the rest of claw.yaml, and both agent construction sites — chat turns and `coding_agent` jobs — layer the wiring on: the init file and socket and token into `shell_env`, the post-filter lines into the prompt's `mcp` section, the persisted set into the config. A frontend without wiring changes nothing, so the daemon without `mcp.yaml` behaves exactly as before. The test configs gain the new field; the fd-limit discoveries from the workspace run are already handled by the harness runs above.