# Recovery 3001 0.4.0 Beta 1 Dev 10 R12

Dev 10 R12 finds deleted files below a folder that was itself deleted, while
keeping corrupt stale folder metadata from stopping other valid results.

## What changed

- Deleted FAT32 directory entries are followed within the existing bounded
  traversal.
- Deleted exFAT directory entry sets are followed for contiguous `NoFatChain`
  storage and preserved FAT chains.
- The recoverable deleted-folder path remains visible in the result name.
- Candidate evidence states when a deleted parent folder was used and warns
  that overwritten folder metadata can make the location or name inaccurate.
- Corrupt deleted exFAT directories are skipped without hiding valid
  root-level or sibling results.
- Active directories are traversed before queued deleted directories, so stale
  deleted aliases cannot hide a live directory that reuses the same cluster.
- Actual source read failures still stop the scan instead of being mistaken
  for harmless stale metadata.
- The total number of visited directories is capped in addition to the
  existing depth and per-directory cluster limits.

## Verification scope

- Full Rust workspace: 114 tests expected, 0 failed.
- Clippy: 0 warnings with warnings denied.
- Deleted-folder focused cases: FAT32 recovery, exFAT recovery, and corrupt
  deleted exFAT directory fail-soft behavior.
- Session, preview, and directory focused audit: 25 tests expected.
- Native Windows 11 UI: 1024x720 working area at 150% plus logical layouts.
- Installer: one EXE, Start menu and desktop shortcuts, payload hash, silent
  install and complete uninstall.
- Source safety policy: write-capable source-device API count remains 0.

## Evidence boundary

- R4 FAT32 1,000/1,000 and exFAT 1,000/1,000 exact size/SHA-256 results remain
  retained core evidence; they are not R12 reruns.
- Existing saved searches for an image with newly discoverable deleted-folder
  files can require a fresh scan because R12 intentionally returns more
  candidates.
- A physical R12 copy-delete-folder-recover run has not been performed.
- Windows 10 execution, unassisted nonexpert 4-of-5 completion, long physical
  disconnect/read-fault endurance, additional USB hardware, code signing, and
  SmartScreen reputation remain open commercial gates.