Skip to content

Default CLI operations to JSON and streamline agent guidance - #11

Merged
nxtman123 merged 1 commit into
mainfrom
feat/json-default-output
Sep 10, 2026
Merged

nxtman123 merged 1 commit into
mainfrom
feat/json-default-output

Conversation

@nxtman123

Copy link
Copy Markdown
Collaborator

Operational CLI commands currently require agents to add --json to get structured results. Default success and error output to JSON, retain --json compatibility, and add explicit --human output. Help stays readable by default with structured discovery available through --json --help; event streams use NDJSON and progress stays on stderr.

Separate help/stream output handling from human text so empty event lists return a JSON envelope without a prose sentinel and streams do not produce duplicate final results. Remove redundant flags from agent-facing recovery commands, catalogs, and examples.

Validation: public/vendor checks, typecheck, lint, mock smoke, package dry-run/release checks, and clean npm installation passed during implementation. Full local suite: 577 passed, five unchanged compose tests failed because Liberation fonts are unavailable, one extractor integration test skipped. After updating guidance strings, 217 focused tests passed. Added six tests covering default output, help, errors, conflicting flags, terminal independence, and streams.

No API or vendor contract changes. This changes default output for callers that previously expected prose; those callers should use --human. Existing explicit --json callers remain compatible. Live-server and player checks were not run.

@nxtman123
nxtman123 merged commit e3bc04c into main Sep 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant