refactor(honcho): probe /openapi.json instead of /health, add warm-fuzzy summary

Real-world Honcho deployments (3.0.5, observed in production) don't
expose a /health endpoint on the API server binary -- the OpenAPI spec
shows no health/liveness route besides authenticated queue status. The
upstream self-hosting docs reference /health, but it's not in the shipped
server. Switch the liveness probe to /openapi.json instead:

- Always present (FastAPI default), unauthenticated, cheap
- Returns deterministic JSON we can validate (openapi: "3.x")
- Bonus: parses info.version so we can show "Honcho 3.0.5" inline

Renames in src/health.ts:
- checkHonchoHealth -> checkHonchoServer
- getHealthUrl       -> getServerProbeUrl
- HealthCheckResult  -> ServerCheckResult (with serverVersion field)

Adds gatherSummary(config) -- one shared function that calls queueStatus
and peer.conclusions.list in parallel post-auth, returning queue/memory
state. setup-runner, status-runner, and health-runner all use it now,
eliminating duplicate logic across the three runners.

setup-runner now ends with a warm-fuzzies panel: server version + latency,
auth latency, workspace, peers, memory state ("empty -- will build as
you chat" or "N conclusions stored"), and deriver progress. Gives users
concrete proof the full memory pipeline is wired up before they start
their next session.

Author: offendingcommit