fix(generate): include runnable parent commands in discovery files#80
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.
Summary
Fix discovery generation so directly invokable parent commands are documented alongside leaf commands.
What Changed
Why
The previous implementation treated only leaf commands with RunE as callable. That caused Phase 4 discovery output to omit valid Cobra commands like full srv, which is directly invokable even though it also has a version subcommand. As a result, generated discovery files could under-report the CLI surface presented to agents.
Impact
Agents consuming generated discovery files now see runnable parent commands, not just leaves. This makes llms.txt and SKILL output better aligned with real Cobra execution semantics and with the actual example CLI behavior.
Validation