feat(phase5): wire adaptive sleep analytics + skip gating into run()

[salishforge]

Summary

PR-A (#136) landed the sleep_phase_analytics table plus the
recordPhaseAnalytics / shouldSkipPhase helpers as analytics-only
infrastructure — the helpers were not yet called from
SleepCycleEngine.run(), so the table stayed empty. This PR wires them in.

• Every top-level phase invocation in run() is wrapped with timing +
  recordPhaseAnalytics() — one row per phase per cycle. Phase
  identifiers: weight-adaptation, scoring, triage,
  capacity-eviction, conflict-resolution, revision,
  graph-maintenance, entity-dedup, reflection, cold-purge,
  schema-detection, temporal-validation, procedure-evolution,
  embedding-migration, deprecated-decay, epistemic-promotion,
  drift-snapshot, audit-archive.
• shouldSkipPhase() gating applied only to the cleanup / reflection
  tail — graph-maintenance, entity-dedup, reflection,
  schema-detection, temporal-validation, procedure-evolution,
  embedding-migration, deprecated-decay. When the last three recorded
  runs of that phase had changes_made = 0, the phase short-circuits
  without I/O and without writing a fresh row (a write would re-anchor
  the zero history; the silent skip keeps the heuristic self-stable).
• Core hot-path phases always run — weight adaptation, scoring,
  triage, capacity eviction, conflict resolution, the Phase 3 revision
  loop, and Phase 6 audit archive are never skipped.
• CHANGELOG.md — the "Wiring deferred" note is replaced with a
  description of the wiring and phase-identifier list.

Test plan

• npm run type-check — clean
• npm run build — clean
• npm run lint — clean
• npm run test:adaptive-sleep — 20/20 pass, including two new
  integration tests:
  - records one analytics row per phase that ran in a single cycle
  - skips skippable phases on subsequent cycles when prior runs were idle
• npm audit --omit=dev — 0 vulnerabilities
• CI green