feat: propagate harness capability rosters - #87
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
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.
Why
Loopy protocol v3 gives each coordinator a caller-frozen roster of the enabled harness families and four strength tiers. Team Harness previously had no typed way to carry that context through its root coordinator, nested harness coordinators, and direct spawned-agent audit records. As a result, downstream agents could lose the actual model choices that the outer loop had selected.
This PR adds transport only. Team Harness does not open, interpret, schedule from, or enforce the caller-owned roster. The coordinator still decides whether and how to delegate.
What changes
capability_roster_context_v1named capability.CallerContextwith an optional absolute roster path, digest, and compact JSON summary. The three fields are validated as one bundle.type=harnessdelegation.agent_assignment.jsonfor auditability.Deliberate boundaries
Validation
pytest -q src/tests/test_caller_contract.py— 19 passedsrc/tests/test_console.py, unrelated to this diffExternal review
Claude Code and Antigravity reviewed this transport together with the consuming Loopy protocol-v3 implementation. No material Team Harness architecture issue remained after review.