Validate memory consolidation artifacts before succeeding - #32193
Merged
copyberry[bot] merged 1 commit intoJul 10, 2026
Conversation
## Why A completed Phase 2 agent run does not guarantee that its required outputs were created correctly. Treating a clean workspace as success can also preserve a state where those outputs are missing. ## What changed - Require `MEMORY.md` to be a file and `memory_summary.md` to start with `v1` before marking consolidation successful. - Fail completed runs with invalid artifacts without resetting the workspace baseline, allowing the job to be retried. - Run consolidation for a clean workspace when its required artifacts are invalid instead of taking the no-change success path. ## Testing Added coverage for rejecting an invalid summary and retrying a clean workspace whose consolidation artifacts are missing. GitOrigin-RevId: ac57b2ba9d062c5203ca51afd716795a91814bb3
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/ac57b2ba9d062c5203ca51afd716795a91814bb3
branch
from
July 10, 2026 15:41
6e02931 to
52c9605
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/ac57b2ba9d062c5203ca51afd716795a91814bb3
branch
July 10, 2026 15:42
clusteruni-debug
temporarily deployed
to
issue-triage
July 10, 2026 15:42 — with 
GitHub Actions
Inactive
clusteruni-debug
temporarily deployed
to
issue-triage
July 10, 2026 15:42 — with
GitHub Actions
Inactive
clusteruni-debug
temporarily deployed
to
issue-triage
July 10, 2026 15:42 — with
GitHub Actions
Inactive
clusteruni-debug
temporarily deployed
to
issue-triage
July 10, 2026 15:43 — with
GitHub Actions
Inactive
DoctorGester
temporarily deployed
to
issue-triage
July 10, 2026 15:45 — with
GitHub Actions
Inactive
DoctorGester
temporarily deployed
to
issue-triage
July 10, 2026 15:45 — with
GitHub Actions
Inactive
DoctorGester
temporarily deployed
to
issue-triage
July 10, 2026 15:45 — with
GitHub Actions
Inactive
DoctorGester
temporarily deployed
to
issue-triage
July 10, 2026 15:46 — with
GitHub Actions
Inactive
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.
Validate memory consolidation artifacts before succeeding
Why
A completed Phase 2 agent run does not guarantee that its required outputs were
created correctly. Treating a clean workspace as success can also preserve a
state where those outputs are missing.
What changed
MEMORY.mdto be a file andmemory_summary.mdto start withv1before marking consolidation successful.
baseline, allowing the job to be retried.
invalid instead of taking the no-change success path.
Testing
Added coverage for rejecting an invalid summary and retrying a clean workspace
whose consolidation artifacts are missing.