Validate packet capture outcomes and narrow cleanup inventory

docs/STATUS.md

@@ -1,6 +1,6 @@
 # Delivery status — 2026-09-26
 
-Unreleased changes after v0.0.5: cleanup previews now return before report creation or clipboard clearing; cleanup preserves files whose recorded size or modification time changed after planning; operation dependencies use the same case-insensitive matching during validation and execution. Seven disposable-file/clipboard-mock regressions and one dependency regression were added. Windows PowerShell 5.1 passed all component suites (128 checks). PowerShell 7 blocked the new cleanup test's replacement catalog with an antivirus response; no matching recent Defender detection was available. This compatibility failure remains open and no replacement executable is published for these changes.
+Unreleased changes after v0.0.5: cleanup previews now return before report creation or clipboard clearing; cleanup preserves files whose recorded size or modification time changed after planning; operation dependencies use the same case-insensitive matching during validation and execution. Packet capture now checks native exit codes, honors previews, validates local paths consistently, refuses existing capture outputs and verifies conversion output. Windows PowerShell 5.1 passed all component suites (142 checks). Fourteen capture checks and 48 feature checks pass in PowerShell 7. Cleanup testing in PowerShell 7 is still blocked by an antivirus response in production cleanup catalog and target validation, even after removing the test's private-function replacement. Defender and Bitdefender are both registered on this host; the responsible product is not established. No replacement executable is published while this compatibility failure remains open.
 
 The update architecture and implementation pass was completed on 2026-09-20. The product is named ms-private. Local OS inventory, offline bundle verification, the graphical and terminal wizards, app/debloat flows, Microsoft app-account purge, network enforcement and capture, reversible privacy-service shutdown, Recall, exact sensors, privacy-artifact cleanup, lock handling, security status and AME packaging are implemented or prepared as described below. No real package download, app removal, account purge, policy write, service mutation, firewall change, device disable, cleanup or Recall deletion was performed.