Skip to content

Preserve recorded verification scope in reports - #55

Merged
mikecerisano merged 2 commits into
mainfrom
work/oct19-reliability-20261019
Oct 19, 2026
Merged

mikecerisano merged 2 commits into
mainfrom
work/oct19-reliability-20261019

Conversation

@mikecerisano

Copy link
Copy Markdown
Collaborator

Generic checksum reports could be labelled Thorough just because MD5 was present, even though that did not establish a separate source reread. Master Report now preserves an explicitly recorded mode and scope, leaves older modes unknown, and refuses contradictory scope/count claims. Finished transfers have a small Verification details disclosure.

The full Mac gate exposed a test fixture that ignored its source-analysis timeout. The fixture now requires analysis to settle before setup assertions; production readiness guards are unchanged. The two focused baseline suites passed five repetitions, so that run did not reproduce the full-suite timing failure.

Validation: the decoder regression fails on unchanged main and passes here; the full engine suites, full Mac app suite, and universal iPhone/iPad build pass. Independent review found no remaining blocker. Physical-device and signed-app walkthroughs remain separate release checks.

@mikecerisano
mikecerisano merged commit 04ca316 into main Oct 19, 2026
4 of 8 checks passed
@mikecerisano
mikecerisano deleted the work/oct19-reliability-20261019 branch October 19, 2026 23:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant