refactor!: rebrand CCAM to AgentHub

Clean break, no compatibility alias. Renames the product name, the CLI
binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` ->
`AGENTHUB_`), the Prometheus metric namespace (`ccam_*` ->
`agenthub_*`), the tmux session prefix (`ccam-lane-<id>` ->
`agenthub-lane-<id>`), the per-repo runtime profile directory
(`.ccam/profile` -> `.agenthub/profile`), the lanes state root
(`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled
plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash
commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` ->
`/agenthub:*`).

Because there is no alias, an existing install has to be updated by
hand: rename its `.ccam/profile` directory and any `CCAM_*` variables,
and reinstall the plugin under its new name.

Two other name families are deliberately left alone here, since they are
not just strings: the `Claude-Code-Monitor` repository/marketplace name,
and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard`
runtime directory, which holds the live database and needs a migration
rather than a rename.

Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across
tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).

server/lib/lane-agents.js

@@ -3,8 +3,8 @@
  * the ship-feature-lane pipeline's agent templates
  * (qc-local, senior-gate-reviewer) into a lane's own .claude/agents/, so a
  * driving session can launch them by the BARE subagent_type name. Source is
- * the repo's own `agents/` — the same files the ccam plugin ships, where
- * they resolve as `ccam:qc-local`; installing them into the lane is what
+ * the repo's own `agents/` — the same files the agenthub plugin ships, where
+ * they resolve as `agenthub:qc-local`; installing them into the lane is what
  * makes the unprefixed name work there too. Plain file I/O except
  * for one git call — resolving where a worktree lane's shared info/exclude
  * actually lives, the same git-dir/git-common-dir distinction E2's
@@ -25,29 +25,29 @@ const EXCLUDE_LINE = ".claude/agents/";
 // loads from the working directory. Marker-delimited so a reinstall replaces
 // exactly this block and never the user's own prose, and appended rather than
 // written over an existing file.
-const STAGE_BLOCK_START = "<!-- ccam:stage:start -->";
-const STAGE_BLOCK_END = "<!-- ccam:stage:end -->";
+const STAGE_BLOCK_START = "<!-- agenthub:stage:start -->";
+const STAGE_BLOCK_END = "<!-- agenthub:stage:end -->";
 const STAGE_BLOCK = `${STAGE_BLOCK_START}
 ## Declare your lane stage as you work
 
-This directory is watched by CCAM. Its pipeline map advances on its own by
+This directory is watched by AgentHub. Its pipeline map advances on its own by
 *inferring* your stage from your tool calls, but an inference carries no
 evidence — the node stays amber, never green. Only your own declaration does:
 
 \`\`\`bash
-ccam stage <stage> --tool codex --evidence "<what is actually done>"
+agenthub stage <stage> --tool codex --evidence "<what is actually done>"
 \`\`\`
 
 - Call it at every real transition — starting to plan, starting to implement,
   running tests, opening the PR — not once at the end.
 - \`--tool codex\` matters: one directory can back both a \`claude\` lane and a
   \`codex\` lane, and without a tool the command fails rather than guess. Inside
-  a pane the dashboard started you need nothing — it carries \`CCAM_LANE_ID\`.
-- \`ccam stage\` warns on stderr and names the valid nodes if a stage matches
+  a pane the dashboard started you need nothing — it carries \`AGENTHUB_LANE_ID\`.
+- \`agenthub stage\` warns on stderr and names the valid nodes if a stage matches
   none of this lane's pipeline template.
 - If it reports that no lane owns this directory, skip the stage calls and
   carry on. Stage reporting is reporting, never control flow.
-- A one-line \`[ccam]\` reminder may be typed straight into this pane asking for
+- A one-line \`[agenthub]\` reminder may be typed straight into this pane asking for
   evidence on the current stage. That is the dashboard, not the user — treat it
   as the same instruction as this section and make the real call.
 ${STAGE_BLOCK_END}`;