docs(adapters): add external-adapter discovery index + authoring guide#637
Merged
Conversation
Completes the "link to adapters defined elsewhere" path with concrete artifacts. - docs/adapters/registry.md — a discovery-only index of in-tree tool adapters (per capability contract, with shipping adapters + tracked extension points), in-tree organizations, and a table for community/external adapters maintained outside the repo. States the discovery-not-installation rule (PRINCIPLES §13): nothing is auto-fetched; an external link is a pointer to evaluate, and adopters wire an adapter in deliberately. - docs/adapters/authoring.md — the step-by-step how-to for authoring a tool adapter (find the contract → implement → declare capability + prerequisites + optional organization → wire in → add an eval) or an organization, with the contribute-upstream vs keep-external trade-off. Wire-in: vendor-neutrality "Authoring your own adapter" now links both; docs/index.md gains a "Find or author a backend adapter" row; organizations/README points its authoring section at the new guide. Generated-by: Claude Code (Opus 4.8)
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.
What
Completes the "link to adapters defined elsewhere" path (from the
vendor-neutrality work) with concrete artifacts.
docs/adapters/registry.md— a discovery-only index of:in-tree tool adapters per capability contract (shipping adapters +
tracked extension points), in-tree organizations, and a table for
community/external adapters kept in their authors' own repos.
States the discovery-not-installation rule (PRINCIPLES §13) up front:
nothing is auto-fetched; an external link is a pointer to evaluate,
and adopters wire an adapter in deliberately.
docs/adapters/authoring.md— the step-by-step how-to: author atool adapter (find the contract → implement → declare capability +
## Prerequisites+ optional**Organization:**→ wire into config →add an eval) or an organization, with the contribute-upstream vs
keep-external trade-off table.
Wire-in
vendor-neutrality.md"Authoring your own adapter" now links both(the index reference was previously unlinked).
docs/index.mdgains a "Find or author a backend adapter" row.organizations/README.mdpoints its authoring section at the guide.Verification
doctoc, markdownlint, lychee (all relative links + anchors resolve),
placeholder check — green.
🤖 Generated with Claude Code