audit-path-sanitize

Auditing path sanitization involves checking character replacement rules and sanitization behavior to ensure Windows-safe folder naming. This validates that sanitization routines correctly replace invalid characters and prevent unsafe folder repairs before executing filesystem operations.

SQLite-stored classification route desynchronization occurs when filesystem paths and client folder naming become inconsistent during repairs. It is detected by verifying destination-existence checks, where broken routes are identified only when the destination folder no longer exists in the filesystem.

Validating empty-folder cleanup guards requires confirming structural-folder protections and empty-folder checks are present before destructive rmdir or rmtree removal. The audit reads the current code to verify these safeguards exist and strictly reports findings based on the existing validation logic.

The path repair audit works with Windows paths and SQLite classification routes by checking character replacement rules and verifying destination-existence checks. It specifically validates sanitize rules, empty-folder cleanup guards, and orphan detection across the filesystem and classification storage.

A limitation of destination-existence checks for orphan detection is that broken routes are only detected when the destination no longer exists. The audit strictly reports findings based on reading the current code, meaning undetected inconsistencies may persist if the destination folder remains present but invalid.