feat(replay): add capture plan orchestration - #363
Open
PhilipJohnBasile wants to merge 2 commits into
Open
Conversation
youssofal
force-pushed
the
main
branch
2 times, most recently
from
September 1, 2026 08:07
2382dfd to
8bc4d88
Compare
PhilipJohnBasile
force-pushed
the
feat/replay-orchestrator
branch
from
September 1, 2026 13:02
9d9d3d0 to
ddc1e2f
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.
Split from #336 as one independently reviewable system.
This PR adds engine-neutral replay orchestration only:
The deterministic replay engine remains in #351. Privacy-safe request capture remains in #356. This PR imports neither implementation. A caller hands the orchestrator report and decision mappings after its replay engine finishes.
Measurement on this commit:
Validation:
The existing macOS CI job now includes
tests/test_replay_orchestrator.py.