feat(execution): introduce execution kernel boundary - #245
Draft
JoTalbot wants to merge 13 commits into
Draft
Conversation
Owner
Author
|
Execution-kernel v1 is now pushed and covered by unit/adapter/integration-boundary tests. Remaining production step: patch the legacy |
JoTalbot
force-pushed
the
feat/execution-kernel-v1
branch
from
August 25, 2026 14:34
234d347 to
0d4ffdd
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
1 participant
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.
Introduces the v1 execution boundary and tests. The branch is intentionally kept as a draft until the legacy Orchestrator._execute_step() is changed to call the adapter directly; the current branch adds an explicit integration helper without replacing orchestrator.py wholesale.