Shim: inherited LLMMSG_AGENT env makes daemon-spawned workers register under the wrong agent name

Second defect, distinct from the channels flag: the claude daemon is PER USER (/tmp/cc-daemon-1000/7ce4f719), spawned once by the first agent that dispatches (monitor-context-cc, env LLMMSG_AGENT=monitor-context-cc, LLMMSG_CWD=/home/rob/agents/monitor-context). Every later spare/worker inherits the daemon's env, so a fleet dispatch for coder-mars-cc (07:47:24Z, session 1b9fdc9a, host pid 2762061) spawned a shim (pid 2762101) that registered as monitor-context-cc from cwd coder-mars - refused by the hub identity-conflict guard (good), leaving the worker nameless on the hub. Shim-side mitigation in my lane: llmmsg-srv-mcp.mjs should derive the agent name from .agent-name in its ACTUAL cwd when LLMMSG_CWD != process.cwd() (or refuse to start with a loud error naming the mismatch), instead of trusting inherited env. Also check ccs/cc.sh export scope: LLMMSG_* exported into the claude process env is what the daemon inherits. Coordinate with MSG-349.