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).

AGENTS.md

@@ -13,27 +13,27 @@
 
 ## Declare your lane stage as you work
 
-This repository is watched by CCAM, its own dashboard. A **lane** is keyed by
+This repository is watched by AgentHub, its own dashboard. A **lane** is keyed by
 working directory, and the pipeline map only moves forward when the agent doing
 the work declares its stage:
 
 ```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.
 - Stage names, `default` template: `intake → plan → implement → tests → review
   → gate → ship → done` (the 16-node `ship-feature` template accepts these as
-  aliases too; `ccam stage` warns on stderr and names the valid nodes if a stage
+  aliases too; `agenthub stage` warns on stderr and names the valid nodes if a stage
   matches none).
 - **`--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 (it names
   both candidates). Inside a pane the dashboard started you need nothing — that
-  pane carries `CCAM_LANE_ID`, which outranks everything but `--lane`.
-- If `ccam stage` reports that no lane owns the directory, this checkout was
+  pane carries `AGENTHUB_LANE_ID`, which outranks everything but `--lane`.
+- If `agenthub stage` reports that no lane owns the directory, this checkout was
   never adopted: skip the stage calls and carry on. Stage reporting is
-  reporting, never control flow — a failed `ccam stage` never justifies skipping
+  reporting, never control flow — a failed `agenthub stage` never justifies skipping
   a step of the actual work.
 
 The dashboard also *infers* your stage from your tool calls (it reads Codex's
@@ -44,8 +44,8 @@ green. Only your own declaration does that — which is why the call above is
 worth making even when the map already looks right.
 
 If you hold a stage for a while with no evidence recorded, the dashboard may
-type a one-line `[ccam]` reminder straight into this pane asking you to run
-`ccam stage ... --evidence "..."`. That is the dashboard, not the user — treat
+type a one-line `[agenthub]` reminder straight into this pane asking you to run
+`agenthub stage ... --evidence "..."`. That is the dashboard, not the user — treat
 it as the same instruction as this section and just make the real call.
 
 ## Where to work