Repository navigation
Clarify verification scope in history and reports - #27
Merged
Merged
Conversation
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.
History and regenerated reports could describe a selected verification mode as though every check finished, or show older Quick rows as verified. They now separate the selected check plan from saved results. Quick remains a size-only check on screen and in PDFs; the original saved row text stays intact in raw CSV/JSON evidence.
History and exported reports disclose recorded selected results and AppleDouble exclusions. A completed record with only part of its saved selected-file plan can no longer get a green History/PDF verdict or a prior-backup hint. Regenerated PDFs lead with the derived safety verdict and omit an older positive attempt summary when the saved evidence does not support it. Older records without a saved plan explicitly say that their coverage cannot be reconstructed. The report summary stays compact and distinguishes failed-only records from empty transfers.
Local validation on the final patch: full engine suite passed (129 XCTest cases, 17 opt-in skips; 163 Swift Testing cases); full Mac app suite passed with parallel testing disabled (266 XCTest cases, 12 skips; 855 Swift Testing cases); iPad build and full iPad/iPhone simulator suites passed;
git diff --checkpassed. A parallel Mac run had one existing thumbnail workflow test end inCancellationErrorunder suite load; its isolated 16-test rerun and the full serial suite passed. A generated one-page History PDF was rendered and visually checked.After PR #26 merged, I updated this branch from main and reran the full engine, Mac, iPad, and iPhone suites on both changes together. GitHub's Mac and engine jobs remain red with the same Xcode 26.3 / Swift 6.2.4 compiler failures already present on main; no new failure appears in this diff. The GitHub iPad build and evidence jobs pass.