VCO Release v3.0.0

Highlights

Promoted the unpublished v2.3.56 architecture-closure baseline into the official major-release line instead of leaving that closure work stranded as a local-only release note. The repository now advances from the last public v2.3.55 tag to a new v3.0.0 baseline in one truthful step.
Hardened install and uninstall behavior around host safety, ownership boundaries, and sidecar-first activation. Supported hosts keep Vibe on a skill-first path, uninstall stays owned-only, and legacy ledger compatibility remains bounded instead of letting cleanup sprawl into unrelated host state.
Added stronger governed execution integrity. Child-lane lineage validation, delegated execution receipts, surfaced-skill promotion into governed execution, and stricter runtime/MCP truth reporting reduce the gap between what the runtime says happened and what the repository can actually prove.
Introduced native MCP-first install guidance and implementation support. The install surface now prefers native MCP setup where appropriate, can auto-provision MCP in a warning-only / strict-offline-safe mode, and reports readiness truth more honestly across shell, PowerShell, and CLI paths.
Tightened the release and packaging baseline that ships with the repo. Runtime-facing release surfaces, dist manifests, release metadata, package versions, and release notes now move together under a single v3.0.0 cut instead of splitting repo release truth from package metadata.

v2.3.55 focused on uninstall hardening, skill-only host alignment, OpenCode startup recovery, AI config-key separation, and macOS bootstrap compatibility.
v3.0.0 absorbs that next unpublished architecture baseline and every merged change through origin/main at 9bea31e, including:
- the v2.3.56 architecture-closure and owner-consumer proof baseline
- host install/uninstall safety fixes from PRs #123, #124, and #130
- governed specialist-promotion and delegated-lineage tightening from PRs #127 and #129
- proof refresh and runtime/MCP truth alignment from PR #128 and PR #132
- MCP auto-provision plumbing, docs, and warning-only offline-safe behavior from PR #131
- native MCP-first install contract tightening from PR #133
The practical result is a larger release boundary than a normal patch cut: users move to a repo state where architecture closure, host safety, governed execution proof, and MCP-first installation are aligned at the same time.

This cut is not just a small batch of fixes on top of v2.3.55. It re-baselines the public line to include an architecture-closure milestone that previously existed only as a local release note.
Install, uninstall, runtime, and MCP setup expectations are now framed around a more opinionated contract: native MCP-first when supported, warning-only fallback behavior when strict offline constraints apply, and more explicit host-ownership boundaries.
The repository's own package version markers now align with the governed release version at 3.0.0, which is a stronger public packaging statement than the prior placeholder 0.1.0 values.

Targeted release tests and gates for this cut are expected to cover release-cut behavior, dist manifest generation, version-governance runtime roles, release-note quality, and packaging/version consistency.
Exact commands and fresh outcomes must be updated after the operator apply and verification pass complete.

Treat v3.0.0 as the first public line that officially includes the v2.3.56 architecture-closure baseline. If you reviewed that note locally before, this release is the public promotion of that state plus the later merged install/runtime/MCP work.
Host operators should prefer the current native MCP-first install guidance rather than older prompt flows that assumed MCP setup would always be manual or always be silently auto-managed.
MCP auto-provision is intentionally not a hidden success path. In strict-offline or degraded environments, the release keeps warning-only honesty instead of pretending MCP became ready when it did not.
If you consume the Python package surfaces directly, re-pin to 3.0.0; the package metadata now matches the governed release line instead of staying on the placeholder 0.1.0 scaffold version.
Existing bounded compatibility surfaces remain deliberate. This release does not claim that every fallback, shim, or historical platform edge has been removed; it claims they are more explicitly governed and better reflected in install/runtime truth.