add generic agent executor boundary - #14
Draft
pyrex41 wants to merge 4 commits into
Draft
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
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.
Summary
pkg/executor.Runnerboundaryrho.run/v1stdin/JSONL executor with strict stream validationWhy
SCUD should own DAG scheduling and wave execution without owning provider APIs or parsing one harness's private event format. This is the first compatible step toward making Rho a bounded executor while preserving all current callers.
Impact
Existing behavior remains the default. The new protocol adapter validates protocol version, run identity, monotonic sequence numbers, terminal events, and terminal payloads. Configuration and CLI selection are intentionally deferred to a follow-up.
Validation
go test ./...go vet ./...git diff --check