Release CLI 0.13.0-rc.25

[adrianwebb]

Outcome

Publishes the reviewed CLI development-runtime lifecycle changes from staging as 0.13.0-rc.25 without moving npm latest.

Work authority

• Work item / Issue: Make development overlays container-portable and execute cleanup contracts #58 and merged PR Make development runtimes container-portable #59
• Proposal / decision: docs/dev-release.md portable development runtime architecture
• Assignment / checkpoint: Platform session dev-aeef9dc6-5a2
• Actor: codex-root
• Human authority: adrianwebb
• Agent / capacity provider: Codex local development agent
• Exact base ref: staging at de868c3
• Exact head ref: codex/cli-0.13.0-rc.25 at 8df51ed

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Advance only package and lockfile versions after merged implementation verification, pass the protected PR gate, tag the merge commit, publish the immutable prerelease, and read it back before Platform selection.

Changes and commits

• 8df51ed advances the package and lockfile to 0.13.0-rc.25.
• Implementation is already reviewed and merged in de868c3.

Verification

• PR Make development runtimes container-portable #59 passed repository verification.
• Clean dependency hydration and npm run verify:direct passed before the release bump.
• 41 tests and packed-install executable smoke passed.

Risk and rollback

This is an npm prerelease; latest remains unchanged. Rollback is selecting 0.13.0-rc.24 in the Platform development integration lock and regenerating Deployment. No production or stable selection changes.

Completion summary

The reviewed changes are ready for protected prerelease publication. Remaining work is tag publication, npm read-back, Platform exact selection, Deployment repackaging, and the live-session retry.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.