Conversation
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.
Summary
memory_consolidationtraffic from the foreground scenarioWhy
Native background requests and retries can arrive at the mock provider while a foreground skill scenario is running. Counting POST requests lets that traffic consume a shell step, causing the fixture to execute an unresolved
<job-id>placeholder and produce misleading failures or hangs.Tests
node --test --test-name-pattern="durable tracked review fixture isolates memory traffic and retries|requires the codex CLI|durable tracked task and result readback" tests/e2e/codex-skills-e2e.test.mjsnpm run lint -- --no-warn-ignored tests/e2e/codex-skills-e2e.test.mjsnpm run typechecknpm run check:version-syncnpm run check:changelogThis is test-only; production routing and memory behavior are unchanged.