cc.sh silent when no bearer resolves; shim comment wrongly exempts loopback

cc.sh fails silent when no .llmmsg-env resolves a bearer; the pane misreads 401 as "hub unreachable". Part 1 - cc.sh (~:126-129, sh.git, on PATH). When no .llmmsg-env overlay resolves a bearer, the launcher proceeds with no token. Every hub call then 401s and the session reads it as an unreachable hub or an FQDN problem rather than a missing credential. Cost real time on audit-llmmsgsrv-cc on 2026-09-11. Want: a launch-time warning when no bearer resolves. Note cc.sh is sh.git - PATH-scripts coordination rule applies (DM bin-venus-cc + bin-whey-cc + bin-lezama-cc after modifying), so the fix is proposed to that lane, not applied by me. Part 2, same item, ours - llmmsg-srv-mcp.mjs:50-51. Its comment scopes bearer presentation to "when behind the Caddy edge-bearer gate (venus)", implying loopback is exempt. It is not: the node hub itself 401s on loopback /roster with no bearer. Measured by bin-venus-cc. The comment is wrong and is what makes the cc.sh failure read as an edge/FQDN problem instead of a credential one. The shim is in my domain, so the comment correction is a diff I author and pm-llmmsgsrv-cc applies. Provenance: relayed by pm-llmmsgsrv-cc (tag pm-llmmsgsrv-cc-mtww037sgvdp); Part 1 from audit-llmmsgsrv-cc's incident, Part 2 measured by bin-venus-cc. Both line citations are claims until I read them myself.