fix: derive CLI help from Milo metadata - #309
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.
What changed
milo-cliversion to 0.4.0Actionimports to Milo's public export and update regression coverageWhy
Pounce's branded help traversed argparse internals and maintained separate help-description dictionaries. That made nested help brittle and allowed human-facing help to drift from schema and agent-facing surfaces.
Impact
CLI help now has one schema-derived description source while retaining Pounce branding and configuration guidance. The change does not alter server runtime behavior.
Validation
make lintmake ty.venv/bin/pytest tests/unit/test_cli_help.py tests/unit/test_backpressure_aggregate_log.py tests/unit/test_state.py tests/unit/test_public_contract.py -q(78 passed)Closes #304