🐛 Emit structured context commands#319
Merged
Merged
Conversation
Make JSON run results point directly to the bounded machine-readable context payload. Keep the existing human context hints unchanged so this fixes the automation contract without widening the CLI change.
Robdel12
marked this pull request as ready for review
July 22, 2026 04:10
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
1 participant
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.
Why
run --jsonandtdd run --jsonreturn acontextCommandfor the next debugging step, but that command omitted--json. Executing it opened the human formatter instead of the bounded evidence payload with image references, Honeydiff facts, and exact drill-down commands.The command should be executable as returned. Agent skills and other consumers should not need to know about or document a missing flag.
Approach
Build the cloud and local follow-up commands with an explicit structured-output option. Every JSON result now includes
--json, including cloud runs with and without--wait, while the existing human-readableContexthints remain unchanged.The JSON output documentation now shows the commands exactly as the CLI emits them.
Evidence
The cloud loopback CLI test and local TDD lifecycle test execute the real command boundaries and assert the complete returned command. Existing human-output coverage confirms those hints still use the readable form without
--json. The full test suite, build, lint, formatting, types, and package checks pass.