Split client tooling out of /opt so hub.mjs stops landing on client hosts

Elazar option-b (root-cause fix), 2026-07-11; HELD as not-urgent 2026-07-12. /opt/llmmsg-srv on whey+lezama is a checkout of the hub REPO kept for client-side files every agent spawn needs: connector llmmsg-srv-mcp.mjs (node_modules/@modelcontextprotocol dep), llmmsg-bootstrap-session.sh (sourced every spawn via ccs.sh/ca.sh), agents registry, bridge, chat-duo. Repo bundles server+client, so client hosts drag hub.mjs they never run. Task = split client tooling into its own package so the server half stops shipping to client hosts. Highest blast radius on the fleet (touches the launcher every spawn uses). Deliverable owed to Elazar FIRST: a written, audit-reviewed migration plan BEFORE any host is touched. Design-first; a go != blind execution. Reference audits gathered: whey 14 scripts+4 systemd units+5 MCP configs; lezama ~12 scripts. See memory hub-noise-reduction-initiative.md open-thread 2.