test(execution): cover orchestrator kernel boundary - #246
Draft
JoTalbot wants to merge 5 commits into
Draft
Conversation
|
The safe adapter boundary from this draft is consolidated into PR #248. Protected legacy orchestrator remains intentionally unmodified; please do not merge this stacked draft independently. |
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
Scope
This PR intentionally does not modify the legacy
orchestrator.py. It creates a safe integration checkpoint before wiring the main Orchestrator through the kernel.Next step
Wire
Orchestrator._execute_step()fortoolsteps toexecute_orchestrator_tool_step()after CI validates this boundary.