release: prepare session-peer 0.5.2 #170

Scope

Prepare session-peer@0.5.2 from main after merged #169 and #160.

• Update package/lock/banner and the registered four-language current-version spans with the scoped updater; preserve dated history and independent pins.
• Add only the finite 0.5.2 runtime row carrying the same four exact skill profiles as 0.5.1, with default/undefined/outer-inspection and future/malformed rejection checks.
• Pin public 0.5.1 as the release baseline; preserve preview 0.1.0-preview.1 and stage-only protected publication controls.
• Record storage refusal/availability changes, current comparison and version maintenance, and the repository-only reporter's exclusion from npm. Do not revive test(ssh): add operator-invoked deployment receipt and recovery harness #155 or research feat(codex): prototype native Side Session input in an isolated experiment #82/feat(experiment): add isolated Codex turn steering prototype #142.
• Validate current-main/PR CI, full tests, reproducible exact-source packing, isolated package lifecycle and every packaged Markdown file before a separate merged-source publication approval.

Baseline and gates

Main 1b9e762c154e1050b04f98d5c36cee0d332cf484; registry latest 0.5.1, preview 0.1.0-preview.1, target 0.5.2 absent. Public 0.5.1 SHA-256 09ad128c3ced31fa263008abd8683f6b60d7593183b36b72b334c1463192221c and registry SHA-512 integrity match the published release record.

This issue authorizes preparation and review. Merge, exact-source staging approval, protected npm environment approval, final npm stage 2FA, tag/release publication and fleet installation remain separate gates. Historical settings-read exceptions do not carry forward.