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/QUICKSTART.md

@@ -21,14 +21,14 @@ That's it.
 ## Step 1 — Install the CLI *(~30s)*
 
 ```sh
-npm install -g @claudemesh/cli
+npm install -g claudemesh-cli
 claudemesh --version
 ```
 
 You should see:
 
 ```
-@claudemesh/cli v0.1.x
+claudemesh-cli v0.1.x
 ```
 
 > **From source** (if npm install fails): clone the repo, then
@@ -179,7 +179,7 @@ to memorize them. Just describe what you want in plain English.
 **`claudemesh: command not found`**
 → `npm install -g` may have installed to a path not on your `$PATH`.
 Try `npm bin -g` to see the install location, and add it to your shell
-rc. Or use `npx @claudemesh/cli` until you fix the path.
+rc. Or use `npx claudemesh-cli` until you fix the path.
 
 **`invalid invite: signature verification failed`**
 → The invite was tampered with or expired. Ask the mesh owner to