Skip to content

docs: refine 0.6 compatibility and checkpoint wording#28

Merged
rlippmann merged 1 commit into
mainfrom
codex/release-readiness
May 13, 2026
Merged

docs: refine 0.6 compatibility and checkpoint wording#28
rlippmann merged 1 commit into
mainfrom
codex/release-readiness

Conversation

@rlippmann
Copy link
Copy Markdown
Owner

Summary

Refines TS 0.6 compatibility wording and release documentation for accuracy against the finalized 0.6 parity surface.

Updates include:

  • explicit reference to the Python 0.6.19 fixture/contracts baseline
  • clarified semantic compatibility wording
  • clarified fixture/contracts validation wording
  • clarified continuation-safe checkpoint persistence wording

Why

TS 0.6 now validates against a substantially larger parity surface than earlier README wording described.

These updates make the documented compatibility scope precise and aligned with the actual validated fixture/contracts baseline.

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

No code changes.
No fixture changes.
No CI changes.

Validation:

  • npm test

@rlippmann rlippmann merged commit 2e18f80 into main May 13, 2026
1 check passed
@rlippmann rlippmann deleted the codex/release-readiness branch May 13, 2026 06:30
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