fix(report): distinguish inventories from restyles - #342
Merged
Conversation
Presentation counts and copy no longer bill one-sided added-node style/state rows as computed-style or state-delta differences. Added elements keep value-only tables labelled head-side inventory (no baseline); raw findings, exit codes, and trust semantics stay backward compatible.
🗺️ StyleProof report📊 View the side-by-side visual report →Coverage, determinism, or report/diff consistency evidence is incomplete — repair the capture or reflow source; visual approval cannot clear this failure. |
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.
Why does this feature exist?
StyleProof currently labels a newly added node's complete computed-style inventory as hundreds of "computed-style differences." During wrapper or path churn, that makes the report look like a large restyle even when most rows are one-sided head context. Reviewers cannot tell structural churn from matched-path style changes.
What changed?
Behavioural Proof (with video and screenshots)
Not applicable: this is Markdown/report semantics rather than an interactive UI surface. Generated demo output was regenerated and checked; behavior tests assert the exact report headlines, tables and JSON count separation.
Verification Summary
.agents/project/DEFINITION_OF_DONE.md.npm run build;npm run typecheck;npm run lint;npm run format:check;npm run privacy:check;npm test;npm run demo:check;git diff --check.Checklist
npm run demo:check; committed demo is currentnpm run build && npm run typecheck && npm run lint && npm run format:checkpassnpm testpasses.agents/project/DEFINITION_OF_DONE.md