feat(plugin): ship the repo's skills as ccam plugin skills

The repo root already IS the `ccam` plugin root (`"source": "./"`), so the
conventional `skills/` dir at the root is the plugin's skills dir — while
`.claude/skills/` only loaded for a session whose cwd was inside this
checkout. That is useless for a lane working in another repo, which is why
`ccam skills install` existed at all.

Move all seven skills to `skills/`: they now reach every plugin user as
`/ccam:<name>` (bare `/<name>` as an alias). `ccam skills install` stays as
the fallback for a plain checkout without the plugin, sourcing from the new
path.

Agents deliberately do NOT move. A plugin agent is addressed as
`ccam:qc-local`, which would break the `subagent_type: qc-local` references
in ship-feature-lane; `ccam lanes agents install` keeps writing them into the
lane's own `.claude/agents/`, the highest-priority agent source. MCP was
already plugin-shipped via `plugins/ccam/.mcp.json`.

Mechanical fallout: ~115 source files carry a doc-comment pointer to
`.claude/skills/file-headers/`, repointed to `skills/file-headers/`. The
generic Claude Code config-surface examples in openapi/cc-config (`.claude/
skills/code-reviewer`) describe any user's layout and are left alone.

Also fixes the two file-headers scripts, whose `ROOT=` climbed four levels
from `.claude/skills/file-headers/scripts/` and would have escaped the repo
from the new depth — it scanned sibling projects until corrected to three.

npm run test:server (1160 pass), test:client (422 pass), mcp:typecheck,
mcp:build + mcp:check-build all green.

skills/debug-live-issue/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: debug-live-issue
+description: Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
+---
+
+# Debug Live Issue
+
+Use this workflow for incident-style debugging.
+
+## Steps
+- Capture symptom, expected behavior, and reproducible path.
+- Isolate subsystem first: hook ingestion, API route, DB state, websocket, or UI rendering.
+- Reproduce with minimal surface area.
+- Prove root cause before changing code.
+- Apply minimal fix and re-verify.
+
+## Evidence standards
+- Prefer direct logs, API responses, DB state checks, and deterministic repro steps.
+- Avoid speculative fixes without root-cause evidence.
+- If not fully reproducible, state uncertainty and strongest hypothesis.
+
+## References
+- Investigation template: `references/investigation-template.md`

skills/debug-live-issue/references/investigation-template.md

@@ -0,0 +1,32 @@
+# Investigation Template
+
+## Problem statement
+- Symptom:
+- Expected behavior:
+- First observed:
+- Scope:
+
+## Reproduction
+- Preconditions:
+- Exact steps:
+- Actual result:
+
+## Evidence
+- Logs:
+- API responses:
+- Database observations:
+- Websocket behavior:
+- UI behavior:
+
+## Root cause
+- Confirmed cause:
+- Why it happens:
+
+## Fix
+- Change summary:
+- Why this fix is minimal and safe:
+
+## Verification
+- Commands/tests run:
+- Manual verification:
+- Residual risk: