Skip to content

fix: return relocated checkpoint artifact paths on replay - #9219

Open
cocolord wants to merge 1 commit into
mainfrom
codex/checkpoint-relocated-replay-paths-20261122
Open

cocolord wants to merge 1 commit into
mainfrom
codex/checkpoint-relocated-replay-paths-20261122

Conversation

@cocolord

@cocolord cocolord commented Nov 21, 2026 •

Copy link
Copy Markdown
Member

Replaying a committed checkpoint from a copied runtime validated the relocated artifacts but returned paths into the original runtime. Forward the existing TypeScript inspection result to the idempotent refresh-state response so callers receive the JSON and Markdown files in the selected runtime.

Historical Run/index bytes, checkpoint proofs and settlement identity stay intact; replay appends no record and spends no quota. Missing or symlinked artifacts still fail through the same typed owner. This is the bounded V2/V4/R1 recovery checkpoint in the small-kernel RFC; complete composition and original-goal acceptance remain separate.

Validation: fixed-main File baseline reproduced the stale path; 10 real File/SQLite CLI cases passed, covering dry-run/repeated replay and JSON/Markdown missing/symlink refusal. The 14 existing checkpoint recovery cases and Ruff also passed. Independent audits verified 24 cases / 72 phases with unchanged source and no remaining fixture processes. Exact-head standard premerge passed: 6 direct checks, 5 catalog smokes, 8 risk-profile smokes and the public-boundary scan; every selected check executed serially. CI, published exact-head review and merge readiness remain pending. Follows the typed artifact relocation owner in #9163.

This branch has not been deployed

No deployments
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