Repository navigation
feat(agentcore): add Turn driver and loop recovery integration - #90
Merged
Fodesu merged 1 commit intoOct 3, 2026
Conversation
Fodesu
force-pushed
the
feat/agent-runtime-core-17-loop-conformance
branch
from
October 3, 2026 14:43
3d56088 to
26e67c3
Compare
Fodesu
marked this pull request as ready for review
October 3, 2026 14:48
Fodesu
force-pushed
the
feat/agent-runtime-core-17-loop-conformance
branch
from
October 3, 2026 17:04
26e67c3 to
38e1dbd
Compare
Fodesu
force-pushed
the
feat/agent-runtime-core-17-loop-conformance
branch
from
October 3, 2026 17:11
38e1dbd to
c60737b
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.
Summary
Adds the driver and conformance layer for the execution Loop. The new driver helpers exercise the Loop through its public
Advance,Deliver, and recovery-facing boundaries rather than reaching into reducer implementation details.Design
The driver separates three responsibilities that are easy to conflate in a Run test: advancing persisted state to a quiescent point, observing dispatched effect keys, and delivering terminal outcomes back through the Loop. Model and tool paths are driven through the same contract, while the driver-specific helpers make the relevant setup and outcome sequencing explicit. Recovery helpers cover Runs that already contain Executing targets and therefore must not silently redispatch or settle them as if the current process owned the original attempt.
The responder abstractions model the Executor boundary used by conformance scenarios. They can validate assignments before a start barrier, accept dispatches by stable key, return outcomes separately, and represent retryable, unknown, or terminal responses. Loop helpers preserve the important invariant that a start fact is committed before an external effect is offered, and that a dispatch whose result is unknown leaves the target Executing for reconciliation.
The driver also makes observation boundaries visible: committed facts are emitted as committed events, while model deltas, reasoning deltas, tool progress, and reset markers remain provisional. This keeps tests focused on the durable protocol rather than on a particular transport or worker implementation.
Testing
The added conformance driver and loop/recovery responder helpers are test infrastructure. They provide reusable scenarios for the later behavior suites without asserting additional production semantics in this branch.