# Recovery 3001 0.4.0 Beta 1 Dev 10 R19

R19 makes installation, update, and removal fail closed while Recovery 3001
is running. It fixes the R18 lifecycle defect where Windows could remove
registry entries and shortcuts while leaving a locked elevated executable.

## User-visible behavior

- Starting install or removal while Recovery 3001 is open now shows a clear
  instruction to finish the recovery task, close the application, and retry.
- No installed file, registry entry, or shortcut is changed before that check
  passes.
- Silent install and quiet uninstall return exit code `32` when blocked by a
  running Recovery 3001 process.
- Retrying after the application closes completes removal without an install
  directory, uninstall registration, shortcut, AppCompat value, or temporary
  worker left behind.

## Implementation

- The Windows application owns
  `Local\Recovery3001.ApplicationRunning` for its full process lifetime.
- NSIS checks the named mutex before install and uninstall mutation.
- The exact `Recovery 3001` window-title check keeps upgrades from R18 and
  earlier builds safe.
- The registered quiet-uninstall command runs a temporary worker outside the
  install directory so it can return the real blocked or completed status
  while the normal NSIS uninstaller removes itself.
- `tools/Recovery3001-InstallerLifecycle-Audit.ps1` exercises the blocked and
  successful paths with the actual application and installer.

## Retained R18 recovery behavior

- FAT32 and exFAT deleted, hidden, system, hidden-system, and deleted-parent
  candidates remain supported.
- Ordinary active visible files remain excluded from recovery candidates.
- The R18 focused hidden/invisible fixture result remains 5/5 exact.
- The independent R16 FAT32 and exFAT deletion corpus remains 2,000/2,000
  exact size and SHA-256 with zero recovery errors.
- The source-device write-command count remains zero.

## Remaining commercial gates

R19 remains an unsigned development beta. It does not replace the required
disposable physical-USB deletion test, Windows 10 execution, observed
five-person usability study, read-error endurance, or trusted code-signing
certificate evidence.