Recovery 3001 0.4.0 Beta 1 Dev 9
Verified at: 2026-07-29 Asia/Seoul
Source commit: 974a3068517a7752b04b5d744d2a2ad9cbad3aa2

Rust workspace tests: PASS, 70 passed, 0 failed
Clippy: PASS, all targets and all features, warnings denied, 0 warnings
Windows release GUI build: PASS
Windows release CLI build: PASS

Image checkpoint audit: PASS
  focused tests: 9/9
  cumulative pre-cancel read-error map: preserved after resume
  missing checkpoint: fail-closed
  source identity and length mismatch: fail-closed
  checkpoint payload tampering: rejected
  partial-image prefix tampering: rejected
  GUI and CLI integration: passed
  source-device write commands: 0
  audit JSON SHA-256: 7fabf758d03df4db9ba392c428d1b649c803dfeb7d7aa7519122ddbddcc1510a

Image fault audit inherited from Dev 8: PASS
  focused tests: 4/4
  failed large read: logical-sector localization
  adjacent failed sectors: exact range coalescing
  disconnect: fail-closed, no later zero-fill
  device identity change: fail-closed, no later zero-fill
  source-device write commands: 0
  audit JSON SHA-256: 182b3c32d7b7f78688eed0e7bce3adc3ffd5f244aa9647e5aba1f9886d2f1f10

FAT32 long-name and preserved-chain audit inherited from Dev 7: PASS
  focused tests: 4/4
  Korean long filename: structurally validated and restored
  preserved fragmented chain: exact 600-byte recovery
  conflicting LFN checksum: deleted 8.3 fallback
  incomplete/out-of-range chain: not trusted
  source-device write commands: 0
  audit JSON SHA-256: 660debf34cf85c7e7a41cee4b41eb9aa502034f6e72cda945d39908b0b456194

Session and candidate preview audit inherited from Dev 6: PASS
  focused tests: 9/9
  source-device write commands: 0
  existing session overwrite: blocked
  session reopen: fresh image rescan required
  audit JSON SHA-256: 4986d6c1248e5d780ee7ad7afb25f65b774ce37630b56bdfed3c6a9505718de0

Windows UI audit: PASS
  automated logical-layout profiles: 3/3
  critical workflow actions per profile: 10
  native Windows screenshots: 5/5
  host: Windows 11 Pro 10.0.26200 build 26200 x64
  display/work area: 1024x768 / 1024x720
  applied DPI: 144 (150%)
  audit JSON SHA-256: 65e7477e167ee437142d8170b0abff6d7b3b62511915f05453db96ae20a4b13c

Multi-environment matrix: PASS, expected behavior 9/9
  full recovery environments: 6
  known limitations correctly exposed: 2
  safe rejection environments: 1
  report SHA-256: bb0eed0397b4f341b85cd68a34d528865aa9c3e52a9c41db0e764d68f891cadc

Real-data exFAT regression: PASS
  filesystem generator: exfatprogs 1.3.0
  image bytes: 15,032,385,536
  image SHA-256: b049eb0ef3c58795b6f947babd0bdaf983310bb2ab283a9c7a737df074a4cafd
  manifest files: 1,000
  manifest bytes: 10,427,498,573
  exact size and SHA-256: 1,000/1,000
  report SHA-256: 7dae50aa05ef57e4f6d2e9affa7afd49fc09802a73f3b7e6c25d93a6cebd0397
  source image unchanged after scan and recovery

Windows executables:
  usb3001-recovery.exe
    bytes: 9,403,392
    SHA-256: 8db285d56666f16c999dab9261f741cc9a378eb945f6f834a45ab126854a3631
    Authenticode: NOT SIGNED
  usb3001-recovery-cli.exe
    bytes: 542,720
    SHA-256: b7e32118b85e80d23e2cfc653da1bc369fa7b39e5bd1898a87f6f3a230ea9969
    Authenticode: NOT SIGNED

The new checkpoint evidence uses deterministic injected cancellation and
tampering. It proves cumulative error-map continuity and fail-closed resume
validation but does not replace long physical read-error/disconnect endurance.
Physical FAT32/exFAT devices, additional vendors and capacities, Windows 10,
unsupervised users, endurance testing, and code signing remain gates.

Android remains deferred and is not included.