chore(cli): rename package to claudemesh-cli (unscoped) for npm publish

@claudemesh/cli was already taken on npm by an unrelated project
(claudemesh "domain packages", v1.0.7). PM picked option A: publish
unscoped as claudemesh-cli. Binary name stays "claudemesh" — users
type the natural thing on install:

  npm install -g claudemesh-cli
  claudemesh install
  claudemesh join ic://join/...

renamed references everywhere:
- apps/cli/package.json: name
- apps/cli/README.md: title + install command
- apps/cli/src/{index.ts, mcp/server.ts, commands/install.ts} headers
- docs/QUICKSTART.md: install command, version banner, npx hint
- docs/roadmap.md: package name

also (PM journey-friction #5): surface the "restart Claude Code" step
LOUDLY in install output. Added a yellow-bold warning line after the
✓ success lines so new users don't miss the restart step (MCP tools
only load on Claude Code restart).

  ⚠  RESTART CLAUDE CODE for MCP tools to appear.

ANSI colors gated on isTTY + NO_COLOR/TERM=dumb guards.

bundle rebuilt. ready for npm publish pending user's `npm adduser`.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/roadmap.md

@@ -10,7 +10,7 @@ broker, ready for real teams.
 - Signed ed25519 identities + signed invite links (`ic://join/...`)
 - Hello-sig handshake auth against the broker
 - Hosted broker at `wss://ic.claudemesh.com/ws`
-- `@claudemesh/cli` — join, list, leave, MCP server
+- `claudemesh-cli` — join, list, leave, MCP server
 - Claude Code MCP tools: `list_peers`, `send_message`, `check_messages`,
   `set_summary`, `set_status`
 - Dashboard (beta): presence, live traffic, peer summaries