VCO Release v3.0.2

Highlights

Published the current main line instead of leaving recent work stranded behind the v3.0.1 side-release branch. This cut packages the latest governed repository state at c2f98b5 as the next public release.
Added a more explicit upgrade path for existing installations. The repo now ships the vibe-upgrade skill surface, version reminder plumbing, and fresher upstream metadata checks so users can detect stale installs and refresh them with less guesswork.
Introduced the workspace-shared memory plane and related runtime disclosure controls. The runtime now has explicit memory disclosure, ingest, and workspace memory policy surfaces rather than overloading older memory paths.
Tightened governed artifact review and specialist visibility. Document artifact governance, delivery acceptance review gates, discussion-time specialist consultation, approved-dispatch disclosure, and stage-by-stage specialist lifecycle surfacing are now represented more clearly in both runtime behavior and proof surfaces.
Continued hardening release and install truth around the newer main line. Upgrade metadata reads, duplicate-surface checks, and runtime/config manifest coverage all moved forward with the rest of the repository rather than being frozen at the earlier release side branch.

v3.0.1 was a corrective public release focused on release integrity and nested compatibility fixes from side-release commit d94b772.
v3.0.2 is cut from the later main line at c2f98b5. It is not a descendant of the v3.0.1 release commit, so this note treats v3.0.1 as the previous public release while remaining explicit that the git history is non-linear.
Relative to the work now on main, the most visible additions are:
- upgrade reminder and vibe-upgrade discoverability from PRs #142 and #143
- aggressive specialist routing and later specialist lifecycle disclosure from PRs #144 and #152
- fresher upgrade metadata and release/runtime compatibility fixes from PRs #145 and #146
- the workspace-shared memory plane from PR #148
- document artifact governance and tighter delivery acceptance review from PR #151
The practical result is that users now get the current mainline governance model rather than a release line that stopped before these capabilities merged.

This is a 3.0.x continuation release, not a new major baseline. The v3.0.0 major re-baseline remains the public architecture reset.
This release focuses on moving the public line forward to the latest governed main state and making recent runtime, review, memory, and upgrade work publicly consumable together.
Package pyproject.toml metadata remains on the existing 3.0.0 package line because the repository's current post-v3.0.0 release practice has not been using those package markers as per-patch release counters.

pwsh -NoProfile -ExecutionPolicy Bypass -File ./scripts/governance/release-cut.ps1 -Version 3.0.2 -Updated 2026-04-13 -RunGates -> PASS
python3 -m pytest -q tests/integration/test_release_cut_gate_contract_cutover.py tests/integration/test_dist_manifest_generation.py tests/runtime_neutral/test_release_notes_quality.py tests/runtime_neutral/test_release_cut_operator.py -> 13 passed
pwsh -NoProfile -File scripts/verify/vibe-version-consistency-gate.ps1 -> PASS
pwsh -NoProfile -File scripts/verify/vibe-dist-manifest-gate.ps1 -> PASS
pwsh -NoProfile -File scripts/verify/vibe-version-packaging-gate.ps1 -> PASS
pwsh -NoProfile -File scripts/verify/vibe-release-notes-quality-gate.ps1 -> PASS
pwsh -NoProfile -File ./scripts/verify/vibe-role-pack-governance-gate.ps1 -WriteArtifacts -> PASS
pwsh -NoProfile -File ./scripts/verify/vibe-capability-catalog-gate.ps1 -WriteArtifacts -> PASS
git diff --check -> clean

Operators upgrading from the public v3.0.1 line should treat this release as the first public cut of the newer main branch work rather than as a tiny hotfix delta.
If you rely on installed guidance surfaces, prefer the current vibe-upgrade path and version reminder feedback instead of older manual-only refresh habits.
If you consume runtime review and disclosure behavior, expect stronger surfaced artifact-review expectations, workspace-memory disclosure controls, and more explicit specialist lifecycle reporting.
This note does not claim that v3.0.2 is a direct descendant of v3.0.1; it claims that v3.0.2 is the next public release from the repository's latest maintained main state.