Add shared command core and CLI

[davejohnson]

Summary

• extract a transport-neutral command registry, context, result envelope, provider bootstrap, and plan/apply orchestration layer
• rebuild MCP as a thin adapter while preserving all 42 canonical hv_* commands and no-argument startup compatibility
• add a friendly CLI with schema-driven flags, file/stdin input, human and JSON output, explicit MCP entrypoints, and TTY-only confirmations
• generate MCP/CLI documentation from the shared registry and add architecture/agent guardrails that enforce the interface boundary

Why

Hypervibe orchestration was coupled to MCP registration and response types, which made a CLI or future interface duplicate behavior or bypass state. Both interfaces now execute the same validated, redacted command definitions and use the same desired-state lifecycle, provider adapters, connections, receipts, and audit history.

Validation

• 108 Vitest files, 881 tests passed
• TypeScript typecheck passed
• production build passed
• registry-generated catalog reports 42 commands
• package prepublish secret/safety check passed
• CLI, legacy no-argument MCP, and hypervibe-mcp entrypoint smoke tests passed