fix: report precision — EVC compile-unit scoping, per-contract change labels - #224
Merged
Conversation
Seranged
approved these changes
Jul 25, 2026
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.
Regenerated verification reports with the report-precision fixes from euler-xyz/euler-verifier#50 (merged to the engine master). No addresses, commit pins, or verification outcomes change —
verify/manifest.jsonandverify/audits.jsonare byte-identical; onlyverify/baselines.jsonand the rendered reports change.What changed
Component diffs scoped to deployed compilation units.
baselines.jsoncomponentPaths now carry:(exclude)pathspecs for source files that are not part of any deployed contract's compilation unit:src/utils/EVCUtil.sol(integrator helper, not compiled into the deployed EVC singleton). The 14-chain pin's delta vs the audited baseline is now +4/−1 (was +58/−11): exactly the isSignerValid signer-exclusion hardening. Pin notes and labels updated accordingly; Polygon reads "set-size 10→100 (audited) + signer hardening" at +15/−12 (was +69/−22).src/Synths/(not among the deployed/verified contracts). The 15-chain pin's delta is now +2/−8 (was +15/−8): the twice-reviewed setLTV change plus the one-line ProtocolConfig parameter default.src/StakingRewardStreams.sol(only TrackingRewardStreams is deployed in scope; no diff impact).Per-contract "What changed" precision. Each table row now reflects only the changed files inside that contract's own compilation unit: rows whose unit contains none of the component's changed files read
≡ baseline (unit), and rows covering a subset show recomputed +/− counts (e.g. the ProtocolConfig parameter change no longer appears on the sequenceRegistry/eVaultFactory rows; EulerSwap per-contract counts are now per compilation unit).Flagged assessment placement. Flagged assessment notes render directly above the product-section table their contract belongs to instead of the top attention block, which now carries only unproven/waived entries.
Every difference vs the previously published reports is one of the changes above (plus the generator reference now reading
master).