fix(report): pair path churn for direct deltas - #345
Merged
Conversation
Derive a conservative before→after correspondence among uniquely signed DOM-removed vs DOM-added paths (tag + rect x/y/width + ownTextLength, shared structural prefix) during report prep. Remap matched before paths and re-diff for presentation so wrapper moves collapse and true property deltas pair, while raw findings, counts, exit codes, and approval gates stay path-certified.
🗺️ 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
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 does this feature exist?
Wrapper refactors can hide genuine restyles inside one-sided DOM inventories. Certification should stay conservative, but the report should show direct before/after values when the same element moved to a new path.
What changed?
Behavioural Proof (with video and screenshots)
Not applicable — generated Markdown report behaviour is asserted by end-to-end fixtures and reproduced against the public Fleet PR #1178 map pair.
Fleet reproduction:
4 DOM change(s) · 32 computed-style difference(s)instead of raw path inventory noise2 elements added, 4 elements restyledfont-size 12px → 13.3333px54 DOM / 1326 style / 84 stateVerification Summary
npm test— 652/652 passednpm run demo:check— passedc8a4f225f7afff42f2c7fd0981e6de86302d07e8