Windows storage audit and cleanup

Use Windows APIs and native PowerShell. Produce a measured space budget, concrete cleanup candidates, and evidence of any authorized changes. Preserve the user's retained apps, games, documents, development state, and recovery requirements across turns.

Establish the scope

• Inventory physical disks and volumes before picking roots. A removable boot drive can expose several letters; an old registry install path can now point to an unrelated volume. Use live files and volume identity as evidence.
• Record used/free bytes and time before scanning. Freeze any reduction target against that baseline. Use GiB consistently, or label decimal GB explicitly.
• Compare retained data with the target early. If protected content alone exceeds the desired final occupancy, explain that constraint; offer a revised target, supported resource reduction, or migration without treating those alternatives as authorized.
• Put machine-specific paths, reports, manifests, and receipts in a private task output directory. Keep the installed skill free of device inventories and private runtime data.

Scan

Read measurement.md for native inventory commands, Python discovery on Windows, and administrator supplementation.

Run the bundled scanner with explicit roots and a new output directory: