Improve agent-first onboarding and access handoffs

[davejohnson]

What changed

• Open Companion onboarding automatically on first launch, register repositories before a Hypervibe spec exists, and connect Claude Desktop and/or Codex in the same flow.
• Track project readiness explicitly so spec-less repositories are chat-ready and stale initialized snapshots are cleared honestly.
• Expose sanitized public service metadata from hv_spec_get and use repo-backed spec/bindings for hv_health, allowing public reachability checks without provider credentials.
• Keep public endpoint results separate from credentialed provider drift, and discard health response bodies, headers, cookies, and arbitrary payloads in the Companion.
• Change missing-connection and delegated-secret guidance to be task-driven: connect credentials the user already controls or prepare a value-free owner handoff instead of assuming provider membership.
• Document the no-role-picker, no-new-service collaboration model and the out-of-band/shared-secret-manager key handoff path.

Why

A new user could launch Hypervibe Companion without knowing that the next useful step was to connect a coding agent and continue in chat. The existing guidance also leaned toward giving collaborators provider access even when they only needed to supply an API key or inspect project intent.

This makes chat the entry point that determines the user's actual task, preserves full functionality for solo users, and keeps provider access scoped to operations that genuinely require it.

User and developer impact

• A fresh Companion installation now leads directly from repository selection to Claude/Codex and a starter prompt.
• A collaborator without Railway/GCP/etc. credentials can see committed desired topology and public endpoint reachability, while exact drift, private logs, and mutations remain blocked or unverified.
• No hosted Hypervibe control plane, secret relay, or shared drift service is introduced.
• Existing project registry and snapshot files remain backward-compatible.

Validation

• npm test — 104 test files, 819 tests passed
• swift test --package-path apps/macos — 45 tests passed
• npm run typecheck
• npm run build
• npm run prepublish-check
• git diff --check