Skip to content

v0.5.2 — fixes rc.2 native-checkpoint resume across restarts

Latest
Latest

Choose a tag to compare

View all tags
@shaomingbo shaomingbo released this 30 Sep 23:04
· 0 commits to main since this release
v0.5.2
ac76e59

What changed

  • Fixes the 0.5.1 known issue: continuing a conversation with a committed native checkpoint after a host restart no longer fails with CODEX_RUNTIME_REQUEST_PREPARE on DSH 0.2.0-rc.2.
  • Root cause: the rc.2 host's bundled converter (pi-ai 0.87.1) normalizes the legacy Context.systemPrompt/tools into a leading transcript system message; the owner-bound native runtime keeps its pinned pi-ai 0.84.4 protocol expecting the legacy shape, so the owner request carried empty instructions/tools.
  • The provider adapter restores the canonical initial system message at the owner's streamSimple boundary (src/owner-context.js): instructions, tools, checkpoint and ordering are preserved verbatim; legacy-shaped input passes through unchanged; unsupported rich or mixed transcript shapes fail closed (CODEX_NATIVE_CONTEXT_INCOMPATIBLE).
  • No core patches, no pi-ai version change, no duplicate login; auth/HTTP/codec/catalog ownership stays with the codex-runtime/v1 owner. Version contracts updated together (package 0.5.2, DEFAULT_SOURCE pin, check assertion, README install pins, CHANGELOG).

Verification (tag v0.5.2, commit ac76e59)

  • Full repo check suite: 173 unit + 46 legacy-A + 34 compaction A/B, all passing; npm pack --dry-run --ignore-scripts (35 files) and git diff --check clean.
  • Paired suites against the published owner dsh-token-usage v5.3.1: owner account suite 423 tests / 416 pass / 0 fail / 7 optional skips; cross-plugin integration 51 tests / 50 pass / 0 fail / 1 optional skip; authSdk 0.82.1 / nativeSdk 0.84.4; no real credentials, no live profile.
  • Actual rc.2 Agent harness: create + separate-process resume with a committed native checkpoint — 16 turns, compaction committed, replay passed, 144→154 events, exact DSH system prompt and fixture tool schema preserved in every native request, externalCalls 0.
  • Isolated rc.2 GUI combination acceptance: 7/7 target plugins active, official file/session references and agent/pre-step capture verified; gpt-6.1-sol (owner v5.3.1 verified catalog) serves through the same pinned protocol template with no interaction.
  • Not verified here: real-account wire behavior and production deployment.
Assets 2
Loading