✨ Show dynamic content evidence in context - #334
Open
Robdel12 wants to merge 1 commit into
Open
Conversation
Render the API-owned evaluation in human comparison context so contained and partial changes report the same explained, residual, and policy facts already available to JSON consumers.
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
The comparison context API already returns confirmed policy revisions plus explained and residual Honeydiff evidence, but the human and
--agentoutput still said0 confirmed regionsand omitted that evidence. That made a correctly contained comparison look unresolved from the CLI.Approach
Render the API-owned evaluation directly in comparison context. Contained and partial comparisons now show the persisted status, explained component numerator and denominator, residual count, and number of cited confirmed regions. The CLI does not infer policy state or invent values.
Evidence
A real contained comparison now reports
11/11 components explained · 0 left · 1 confirmed region. A partially explained comparison reports34/37 components explained · 3 left · 2 confirmed regions, matching the JSON response exactly. The complete CLI test suite and lint pass.