fix: move-codex-session rollback should keep destination history rows it never copied #133
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/move-codex-session-rollback-history"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #132 from its review (finding): when the state copy commits and the history copy then fails, the rollback deleted destination history rows for every moving rollout, including rows a destination writer committed between the two copies. It now deletes history only when the history copy committed. The deletion predates #132.
move-codex-sessionrollback should keep destination history rows it never copiedReview
01M4H763PQSV82W9GT592YVAF8— head7d4d9b4c10808e6a110b48942c23016d564ad088Review — j4k-oss/agent-skills @
b95311f880Scope: diff against base tree
40154724b696Status: dispatched — coverage complete (3/3 slots terminal)
Facts: current review-wide projection
Computed under:
Findings (0)
No findings survived.
Reviewed:
Other claims
Coverage
Coverage pass: 01M4H76H88VKZ50VD2S21FANP1
Accounting: complete
Slot health: healthy
move-codex-sessionshould handle Codex 0.160.1 and large native homes #132The summary's one finding (claim
01M4H3J3X9RYG7TT2S4ZXF5HTH, the precision test's trigger firing for both threads) is valid but sits in a test this PR does not change. It is the same defect #132's review reported in #132 (comment). Tracked in #136.move-codex-sessionhistory rollback test should wait for the script before cleanup7fef9c3b8f7d4d9b4c10move-codex-sessionrollback keeps copied history rows whencopyHistorythrows after its commit #140moveWhileDestinationIsEditedtest helper should wait for the script when its editor fails #141