[mikecerisano]

What this changes

A saved ASC MHL can record a file rename or a directory move using previousPath. BitMatch Check previously ignored that lineage and treated a valid recorded move as unrelated file paths. Check now reports this history as unsupported until it can interpret and verify it, instead of giving a misleading result.

Adds a redistributable, two-generation MD5 fixture generated by the pinned ASC reference CLI: a file rename and a directory move, plus schema, chain, byte-verification, diff and unrecorded-move controls. The corpus and Swift regressions also cover a directory-only lineage marker and a classic MHL record beside valid ASC history. This does not add structural/history verification or change existing manifests.

Local validation

• Pinned reference corpus: 82/82 checks passed.
• Focused Swift evidence tests: 18/18 passed.
• Full engine suite: 129 XCTest cases, 17 intentional hardware skips; 166 Swift Testing cases passed; zero failures.
• iPad generic simulator build: passed.
• Mac app and test host compiled, but the Mac test runner stalled before starting any cases. That run is not counted as a test pass.

GitHub Actions started automatically when this draft was pushed. Observed Mac jobs stop before tests during an Xcode 26.3 compiler IR-generation crash in PreferencesWindow.swift; engine jobs stop before tests on Swift concurrency compile errors in ChecksumTruncationTests.swift and StressTests.swift. The same compile failures appear on the existing #28 CI branch. Evidence-corpus jobs pass. No manual CI rerun was requested; the local results above are the review evidence for this draft. Physical-drive and signed-app checks remain open.