Optimize CLI output defaults for agent efficiency (#94)#99
Merged
Conversation
11 tasks
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.
Description
Implements issue #94 end-to-end by centralizing CLI output policy and applying compact/TTY-aware defaults across command surfaces.
Key outcomes:
--prettysupport.--formatdefaults to auto-detect (tablefor TTY,jsonfor non-TTY) while preserving explicit override behavior.status --verbose; default JSONstatusnow returns summary-first payloads.SPECLEFT_COMPACT=1) withnext --limit 1default.features validate,features add,features add-scenario,test skeleton,test stub,init, threshold-basedcoverage).fix_commandfields for applicable failure outputs indoctor,contract test, andenforceJSON payloads.SPECLEFT_COMPACT=1and exit-code-first workflow guidance.Type of Change
Checklist
Testing
Related Issues
Closes #94