Repository navigation
feat(codex): ingest compressed and shared-history rollouts - #54
Merged
Merged
Conversation
jamesyong-42
force-pushed
the
feat/codex-rollout-storage
branch
from
November 13, 2026 00:33
530ac19 to
0b65666
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Older Codex sessions could appear as empty metadata because Rosetta did not discover
.jsonl.zstrollouts or archived transcripts. Resuming a session in Codex restored its plain file and made the history appear again. Import both representations directly, following the writer protocol pinned to Codex 0.167.2.Validation includes 25 focused storage regressions, cross-adapter replay/live/snapshot tests, 165 pipeline unit tests, 253 daemon tests, 68 ground-truth tooling tests, full-workspace strict Clippy, and checks of all five shared-history range references found in the local census. An isolated import of two copied native sessions produced 92 and 199 canonical messages, respectively, with zero hard errors and a clean SQLite integrity check. No private transcripts or fixtures are committed.
A release-mode paired synthetic run produced identical 8,000-message projections: 485.63 ms for plain input and 493.43 ms for zstd. Twenty quiet polls started zero capture passes in either representation. This is a small warm-filesystem measurement, not a full-archive performance estimate. The reproducible benchmark and storage contract are recorded in
docs/ARCHITECTURE.md.