[rappdw]

Publish the October 30 release with explicit retained-history unified Codex adoption and working native Codex panes in Claude-served mixed-agent sandboxes. The installer selects the new release, supports confirmed adoptions, and continues holding unconfirmed retained state for an explicit operator transition.

The deployment pin is the merged release-line backport in proofpoint/amap-deploy-sandy#115. It includes shared native adoption proof for startup and host verify, explicit legacy-record revalidation, stable system-interpreter startup, installed-build selection, and bounded single inventory reads. The Codex connector pin adds redundant reasoning-effort compatibility. Claude and router commits stay unchanged. Older release records and published tags stay unchanged.

Validation:

• Deployment Python 3.9/3.13 suites and sibling-canary CI passed. The pinned squash-merge tree matches the tested PR head.
• Fresh exact-component checkouts passed the release contract: sibling pins, 26 launcher cases, isolated host imports, and pinned transition/adoption/revalidation/inventory suites.
• All four offline Git bundles were restored and checked for matching commit, annotated tag object, and Git object integrity. The archive checksum is tracked beside the manifest.
• New release CI runs the contract on Python 3.9 and 3.13. Published annotated tags must be verified before promotion.

Installation does not automatically adopt, erase, recreate, or transfer ownership of existing state. The runbook documents explicit adoption and revalidation. These source-level checks do not establish target-host readiness.