VCO Release v3.0.1

• Date: 2026-04-09
• Commit(base): a5befb8
• Previous remote release: v3.0.0

Highlights

• Restored install-time generated nested compatibility for managed installs. The installer now materializes the nested bundled/skills/vibe compatibility surface again, and the materializer no longer deletes the source tree when the source root already points at that nested skills directory.
• Hardened the governed release operator instead of relying on a fragile happy path. release-cut.ps1 now runs the bundled-sync operator in preview/apply mode, appends JSONL ledger entries safely even when the existing ledger lacks a trailing newline, and inspects gate signatures before adding -WriteArtifacts.
• Reopened the full extended release train by restoring the governance assets those gates expect. Historical Wave40-63, Wave64-82, Wave83-100, and Wave121-140 boards, manifests, and governance docs are back in place so a fresh release can pass against the current repository state instead of depending on missing historical context.
• Tightened gate compatibility around canonical skills. The capability-catalog and role-pack governance gates now union config/skills-lock.json entries with canonical core/skills/*/skill.json identifiers, preventing false failures for canonical skills such as vibe.

What Changed Since v3.0.0

• v3.0.0 established the new public baseline around architecture closure, host-safe install/uninstall, governed execution proof, and MCP-first readiness.
• v3.0.1 is the first corrective release on top of that baseline. It is focused on release integrity rather than new product scope:
  • fix the nested generated-compatibility install regression
  • restore bundled-sync preview/apply behavior inside the release operator
  • repair release-ledger append behavior for newline-less JSONL files
  • restore historical governance assets required by the extended release gates
  • align release gates with canonical skill identifiers so the current repository can verify cleanly
• The practical result is that the repo can now cut and verify a governed release from current main without hand-patching missing history or accepting broken nested install behavior.

Validation Notes

• pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/governance/release-cut.ps1 -Version 3.0.1 -Updated 2026-04-09 -RunGates
• pytest -q tests/runtime_neutral/test_release_cut_operator.py
• Targeted gate reruns while fixing the release train:
  • pwsh scripts/verify/vibe-wave40-63-board-gate.ps1
  • pwsh scripts/verify/vibe-wave125-gate-family-convergence-gate.ps1
  • pwsh scripts/verify/vibe-role-pack-governance-gate.ps1 -WriteArtifacts
  • pwsh scripts/verify/vibe-capability-catalog-gate.ps1 -WriteArtifacts
  • pwsh scripts/verify/vibe-wave64-82-closure-gate.ps1 -WriteArtifacts

Migration Notes

• If you consume install-time generated nested compatibility paths, re-cut or reinstall from v3.0.1; this patch restores the nested compatibility surface that regressed after v3.0.0.
• If you run release operations through scripts/governance/release-cut.ps1, this release is the first cut that restores bundled-sync preview/apply linkage and gate invocation compatibility across mixed gate signatures.
• This release intentionally restores historical governance assets that current release gates still treat as required proof. Operators who trimmed those files locally should keep them; the current release train depends on them.