Follow-up to merged #535 and completed upstream cycle #526; related to #200. Eligible Claude turns already support exact rewind using immutable native forks, full raw JSONL proof and source/callback quarantine. This issue tracks remaining native-history compatibility limits.
Remaining cases:
- The pinned SDK cannot prove an empty/root conversation through its fork API.
- Older uncaptured checkpoints and checkpoints from a previous ordinary session incarnation are ineligible.
- Compaction can remove the provable mapped boundary of an older checkpoint.
- Unsupported native history transformations, ambiguous history identity and histories exceeding the 64 MiB proof bound remain unavailable.
Investigate native root/fork primitives, durable boundary identity across compaction and ordinary restart, and complete semantic history access. Enable reconstruction or retention only where the original target and current source can both be verified. Revisit when the SDK exposes these capabilities or a reproducible unsupported semantic record establishes a narrowly provable normalization. Pending tools, questions, background work and prompts are intentional admission blockers and must not be bypassed.
Acceptance:
- Preserve full inference context, including records omitted by the SDK message projection; do not broaden metadata normalization without native-source evidence.
- Preserve private snapshot identity, idempotent selection/compensation, same-incarnation recovery, callback quarantine and ordinary Stop/resume.
- Cover empty root, compaction, prior-incarnation history, hidden context, file replacement, delayed callbacks and unsupported cases relevant to the change.
- Keep bounded, scoped file reads and proof deadlines. Independently review the final diff and require green CI; document native versions and any remaining upstream blockers with concrete revisit triggers.
Existing evidence: #535 records exact-head independent SDK/adapter review, 160 focused tests, 135 integration service/capability tests and green final/merge CI. Synthetic fixtures exercised actual SDK history/fork behavior, but no live Claude process/account/model request was claimed. Any further runtime validation must use isolated state and the applicable authorization boundaries.
Model: GPT-6. Harness: Codex.
Follow-up to merged #535 and completed upstream cycle #526; related to #200. Eligible Claude turns already support exact rewind using immutable native forks, full raw JSONL proof and source/callback quarantine. This issue tracks remaining native-history compatibility limits.
Remaining cases:
Investigate native root/fork primitives, durable boundary identity across compaction and ordinary restart, and complete semantic history access. Enable reconstruction or retention only where the original target and current source can both be verified. Revisit when the SDK exposes these capabilities or a reproducible unsupported semantic record establishes a narrowly provable normalization. Pending tools, questions, background work and prompts are intentional admission blockers and must not be bypassed.
Acceptance:
Existing evidence: #535 records exact-head independent SDK/adapter review, 160 focused tests, 135 integration service/capability tests and green final/merge CI. Synthetic fixtures exercised actual SDK history/fork behavior, but no live Claude process/account/model request was claimed. Any further runtime validation must use isolated state and the applicable authorization boundaries.
Model: GPT-6. Harness: Codex.