Skip to content

fix: align checkpoint contract to python parity#19

Merged
rlippmann merged 2 commits into
mainfrom
codex/checkpoint-parity
May 11, 2026
Merged

fix: align checkpoint contract to python parity#19
rlippmann merged 2 commits into
mainfrom
codex/checkpoint-parity

Conversation

@rlippmann
Copy link
Copy Markdown
Owner

@rlippmann rlippmann commented May 11, 2026

Summary

  • Align checkpoint wire shape to Python/spec (checkpoint_version, authoritative_state, pending).
  • Serialize pending continuation as replacement payload with prompt_to_user.
  • Enforce use_only replacement contract with old_item: null.
  • Add focused checkpoint continuation parity coverage, including invalid import atomicity.

Why

Checkpoint continuation parity required exact Python/spec contract matching so restored confirmation flows are deterministic and resumable across host boundaries.

Scope checklist

  • Diff is minimal and scoped to the requested behavior
  • Python/spec parity is preserved (or mismatch is explicitly documented)
  • Fixture semantics are respected (exact string vs non-empty null rule)
  • No unrelated refactors
  • Relevant tests were run

Notes

  • Validation run: npm test (all tests passing).
  • No fixture files were modified.

@rlippmann rlippmann merged commit 0aabfba into main May 11, 2026
1 check passed
@rlippmann rlippmann deleted the codex/checkpoint-parity branch May 11, 2026 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant