VCO Release v2.3.51

Highlights

Moved downstream delivery acceptance from an external verification layer into the normal vibe governed runtime main chain. Governed runs now freeze product acceptance criteria, manual spot checks, completion-language policy, and a delivery-truth contract directly in the main requirement surface.
Extended the governed plan and closure path so xl_plan records a delivery-acceptance plan and phase_cleanup emits a per-run delivery-acceptance-report.json. This makes completion-language downgrades part of the real runtime path instead of a post hoc review convention.
Completed the recent specialist-governance sequence on main: stage-bound specialist dispatch, child-lane same-round auto-absorb under root approval, and stronger native-specialist failure proofing. This improves how vibe uses specialist help without surrendering runtime authority.
Fixed the Windows specialist runtime handoff so native specialist execution remains viable on current Windows environments.

v2.3.50 was mainly about install truth, router AI connectivity proofing, and host-adapter/install-surface closure.
v2.3.51 shifts the center of gravity into the governed execution path itself. The main difference is that the repo no longer only says “delivery truth matters”; the normal vibe runtime now writes and carries that truth in its own artifacts.
The older release improved readiness disclosure and verification entrypoints. The new release raises the honesty bar for declaring work complete after a governed run.

Main-chain delivery-acceptance coverage:
- pytest -q tests/runtime_neutral/test_runtime_delivery_acceptance.py tests/runtime_neutral/test_workflow_acceptance_runner.py tests/runtime_neutral/test_release_truth_gate.py
Governed runtime / hierarchy / topology coverage:
- pytest -q tests/runtime_neutral/test_governed_runtime_bridge.py tests/runtime_neutral/test_l_xl_native_execution_topology.py tests/runtime_neutral/test_root_child_hierarchy_bridge.py
Release-surface hygiene:
- git diff --check

Operators should expect stricter completion wording after normal governed runs. A clean runtime/process closure is no longer treated as equivalent to proven downstream project delivery.
Normal vibe session artifacts now include a delivery-acceptance-report.json and companion markdown summary under outputs/runtime/vibe-sessions/<run-id>/.
This release improves truthfulness and closure semantics. It does not claim that every host UI now enforces an absolutely unskippable final text gate; the authoritative change is that the governed runtime itself now records and carries the delivery-truth result.