Repository navigation
docs(adr): accept ADR-0030 on renderers and the CLI/action boundary - #785
Merged
Merged
Conversation
One result model rendered for terminal, plain and GitHub Actions output, with gating opt-in and CI baselines degrading silently. Amends ADR-0027 decisions 7 and 9.
Teakowa
enabled auto-merge (squash)
October 19, 2026 11:40
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.
Records the decision to render one result model through terminal, plain and GitHub Actions renderers, and fixes the CLI/action boundary.
--fail-on-style gating is an opt-in CLI option, default off; thewrightaction stays thin.Docs only. Numbered 0030 because
mainalready has ADR-0029. Implementation issues follow after merge;docs/cli/presentation.mdanddocs/cli/commands.mdare updated with the implementation.Unverified: the annotation
file=base path when--rootorworking-directoryis not the repo root; this belongs in the implementing issue's acceptance.