Repository navigation
Consolidate Harness interfaces into one onboarding entry point - #197
Merged
Merged
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.
Harness authors now start at
apps/parsar-daemon/internal/agent/harness.go. It contains the existing Executor/Turn lifecycle, separate optional interfaces, direct-call/preparation contracts and registration methods. Operation result/error types and Registry storage/lookups remain in their focused files.README and the onboarding guide link directly to this entry point. The guide explains registration order and the distinction between Runtime capability declarations and Core qualification. Existing signatures, registration behavior and protocol types are preserved.
Validation: agent, dispatch and CLI tests pass. A declaration-by-declaration token comparison against main confirms all 46 existing package declarations are unchanged apart from comments and file placement. Full
make checkpasses on zju_a100_2, with the unchanged Web gate run on mx (55 browser tests). Independent blind review found no actionable in-scope issues. No native execution behavior is changed.