Add optional Agent Guild endpoint observation block - #7796
Draft
AgentTanuki wants to merge 1 commit into
Draft
Conversation
|
@AgentTanuki is attempting to deploy a commit to the Sim Team on Vercel. A member of the Team first needs to authorize it. |
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.
Adds an optional Agent Guild block for observing an explicitly supplied public HTTPS agent endpoint. It shares that URL with Guild and returns bounded check statuses, failed checks, unknowns and fixed limitations. It does not authorize delegation, invoke a target task, or turn observations into a safety guarantee.
The operation uses Sim’s native request path, redirects, socket timeout and parent cancellation. It performs no automatic retries, matches the returned target exactly, rejects incompatible responses, and applies a 64 KiB projection limit after the native transport cap. Includes registry entries, catalog templates and opt-in skill suggestions, generated metadata/docs, and the existing neutral search icon.
Validation includes the real Serializer → GenericBlockHandler → executeTool → pinned HTTP transport with only HTTP/DNS responses substituted, plus contribution contract tests, application type checking, generated metadata/docs/catalog checks and boundary audits. The graph baseline refresh records an intentional one-module block addition; exact staging comparison is 0/+1 modules across all 75 guarded entries, with no executable-registry reachability. The full generated refresh also incorporates drift already present at the pinned staging commit.
Validation results: 37/37 native execution cases (independently repeated), 21/21 contribution contract tests, full application type checking, and the required generation/boundary checks passed. Network responses were substituted; live provider availability and authorization involving persisted user/workspace state were not exercised. The native socket timeout is not a total deadline.
The generated documentation is preserved exactly as emitted by the existing generator. Its trailing whitespace produces two cosmetic diff-check findings; generated-doc freshness and original-source whitespace checks pass.