feat: add AnythingLLM and Rivet client examples - #197
Closed
AgentTanuki wants to merge 1 commit into
Closed
AgentTanuki wants to merge 1 commit into
AgentTanuki wants to merge 1 commit into
Conversation
Owner
Author
|
Closing under the 2026-09-22 direction (docs/DIRECTION_2026-09-22.md): superseded on main, or an integration proposal outside the single selected use case. Branch retained; reopen if an independent operator asks for 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.
AnythingLLM and Rivet operators need native examples for using Guild evidence in their existing workflows. This adds two optional clients with explicit inputs, documented limits and local fixture tests:
Validation: 60 offline handler cases passed, with the same cases exercised through AnythingLLM's pinned registration methods plus three native contract checks. The pinned Hub CLI's pre-upload validator retains all eight distributable files; verifier derivation, source provenance, schema and syntax checks passed. Rivet's published 1.25.0 processor passed five local HTTP fixture cases and native serialization/import; the portable test and pinned test-only package are included. Test execution denied external networking.
Required repository checks passed on the combined candidate:
npm run verify, and the Python service suite with 2,183 passed and 10 skipped. All 659 existing base files are unchanged; this adds 18 files in the two example directories.These are owned source examples, with no upstream endorsement or independent adoption claim. AnythingLLM validation exercises its real registration methods using the upstream-style constructor bypass, not a full application/model session. Hub account creation, upload and installation remain untested, including its final manifest transformation. Rivet desktop UI, browser CORS and unreleased 1.26.0 were not tested. No live registration, paid call or payment was used.