Repository navigation
docs: require Node README capability summaries - #2
Merged
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
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.
Downstream Node repositories need an explicit contract for documenting entrypoints and Tool capabilities. Add the required README fields and template to the contribution guide, link it from the root README, and align the Tool handler description with its Query/Action/Session implementation.
Count production Nodes, Endpoints, operations, HTTP routes and deployment Tool bindings separately. This change only updates documentation.
Maintain independent English
README.mdand Simplified ChineseREADME_zh.md, with reciprocal language links and matching API identifiers, commands and configuration examples. Future interface changes must update both documents.