Repository navigation
Clarify verification status in History and CSV exports - #34
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 could show an older Quick transfer as unverified while its CSV/JSON export still called the same file a “Match.” Exported per-file status now uses the same interpretation as History and keeps the original journal wording in a separate
recorded_status/recordedStatusfield. Saved history is unchanged.The automatic CSV also stops calling a copied-but-unverified row “Verified” solely because it carries a checksum. That label now requires a verified result status and a checksum.
Local validation: full Mac app suite passed (267 XCTest, 12 expected skips; 861 Swift Testing, zero failures). Focused History/report suites passed (7 XCTest and 28 Swift Testing), 18 focused engine evidence tests passed, and the iPhone/iPad simulator build succeeded. A separate full engine run stalled at a permission-test boundary and was stopped; it is not counted as a pass. No physical-drive behavior changed.
Hosted Actions may start automatically on push. Existing Mac and engine jobs on nearby drafts stop during compiler/toolchain errors before tests; local results above are the validation evidence for this draft. No manual CI rerun was requested.