VCO Release v2.3.52

Highlights

Landed stage-aware memory activation inside the normal six-stage vibe governed runtime. Governed runs now emit memory-activation-report.json and memory-activation-report.md, carry bounded memory-context injection into requirement/plan artifacts, and keep the activation path visible in per-stage receipts.
Added real governed backend adapter calls for Serena, ruflo, and Cognee. When enabled, the runtime now writes request/response artifacts under the session's memory-backend/ directory instead of only recording advisory ownership policy.
Kept the memory contract narrow and explicit instead of widening it into an uncontrolled background memory layer:
- Serena remains for explicit project decisions
- Cognee remains for bounded relation recall / ingest
- ruflo remains XL-scoped for milestone and handoff continuity in plan_execute
- knowledge-steward is still an explicit skill, not automatic runtime capture
- the cleanup fold is a local governed fold artifact, not silent auto-invocation of the deepagent-memory-fold skill

v2.3.51 moved delivery acceptance into the main governed runtime chain and tightened specialist-governance closure.
v2.3.52 moves the memory plane forward from mainly policy / route advice into observable stage-bound runtime behavior with real backend read/write paths and runtime artifacts.
The important difference is not "more memory everywhere". The difference is that governed runs now show where memory was read, where it was written, and where the runtime deliberately refused to widen memory scope.

Memory activation/runtime backend coverage:
- pytest -q tests/runtime_neutral/test_memory_runtime_activation.py
Governed runtime / topology / hierarchy regression 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
- pwsh -NoProfile -File scripts/verify/vibe-version-consistency-gate.ps1
- pwsh -NoProfile -File scripts/verify/vibe-dist-manifest-gate.ps1
- pwsh -NoProfile -File scripts/verify/vibe-nested-bundled-parity-gate.ps1

Operators should expect new runtime artifacts under outputs/runtime/vibe-sessions/<run-id>/, especially the memory activation report family and, when backend lanes are enabled, request/response receipts under memory-backend/.
This release proves governed memory activation and bounded backend integration. It does not claim that every memory-related skill is now silently auto-running in the background.
knowledge-steward still requires explicit user intent, and the runtime cleanup fold should be read as local governed context compaction rather than as a full skill-level memory handoff backend.