Document and test governed-runner tool facade#49
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.
Summary
Documents and tests the product-facing governed-runner tool adapter path now exposed by AgentPlane through
sp-run tool ....These remain pure facade delegations:
prophet governed-runner tool list-tools prophet governed-runner tool call governed_runner.doctor --args-json '{}'Delegates to:
sp-run tool list-tools sp-run tool call governed_runner.doctor --args-json '{}'Adds
prophet governed-runner tool ...tests/test_governed_runner_tool_facade.pyBoundary
No governed-runner implementation moves into
prophet-cli. This only documents and tests the facade path after AgentPlane added the actualsp-run tool ...delegate path.Validation