feat: OACP v0.5.0

[kiloloop-release]

OACP v0.5.0 — the memory-exit release.

Cross-session memory leaves the kernel and ships separately as agent-memory-cli. OACP keeps the memory layout spec and a conformance fixture that the kernel scaffolders and downstream implementations pin against, plus guards that fail the build if the engine ever creeps back in.

Highlights

Added

• Memory-layout conformance fixture pinning the layout grammar and canonical sync allowlist.
• oacp doctor reports the installed agent-memory version and defers memory-home checks to it.
• Preflight and wheel-content guards fail when a kernel module or the wheel ships the memory engine.

Changed

• The org-memory protocol doc becomes the three-tier memory layout spec the kernel scaffolds against.
• oacp memory and oacp org-memory delegate to the agent-memory CLI until their removal in 0.5.2.
• oacp setup no longer installs memory hooks and retires the ones it generated; agent-memory setup replaces them.
• oacp session-init --pull-memory delegates the pull and reports disabled when agent-memory is absent.

Removed

• The bundled memory engine and the org-memory doctor category, oacp doctor --memory, and docs/protocol/cross_runtime_sync.md.

Fixed

• oacp setup codex regenerates its managed SessionStart hook but never creates one, leaving a deliberately hook-free workspace untouched.

Full detail in CHANGELOG.md.

Contract version

No contract change — spec_version stays 0.4.5. The protocol docs moved substantially by line count, but no required field, schema version or contract constant changed, and the new vocabulary is layout grammar rather than message or audit-record fields. The kernel-to-memory-tool layout agreement is pinned by the vendored conformance fixture and its test, not by the contract stamp.

Verification

• 68 files changed; the promoted tree is byte-identical to the reviewed staging tree (git write-tree = 4a7ed6db3964336c1e4411957c7fef77747e5899 on both).
• preflight --full passes on the source of this promote: conflict markers, makefile parse, packaging boundary (32 scripts match force-include, all 47 sources present), memory boundary (33 kernel modules import no memory engine), YAML validation, ruff, shellcheck, and the test suite.
• The lean-kernel guards were confirmed to fire, not merely pass: planting a memory-engine import into a kernel module makes the boundary check fail and name the file and line, and a planted build proves the wheel-content guard catches a shipped engine package, flat module and template.
• Built artifacts from this tree contain no memory-engine files: oacp_cli-0.5.0-py3-none-any.whl carries 55 entries, 32 bundled scripts and 7 protocol documents, none of them the engine.