docs(readme): add the community-adapters row to the roadmap - #211
Merged
Conversation
Merged
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
Ten
adapter wantedissues (#201-#210) now exist, one per harness, each carrying the research a contributor needs (where it writes, format with writer links, lineage, generations, capture recipe, gotchas) plus the playbook, the reference PR, and the evidence-section pointer. This adds the row that makes them visible from the roadmap, linking theadapterlabel query, and the issues are on the project board. Aider (lossy source) and Amp (no local writes since 2026-03; export-backed only) were researched and left out on purpose.Release note