windowsweep 1.1.0 → 1.2.0

package/AI-INTEGRATION-GUIDE.md

@@ -22,7 +22,7 @@ summary**, and every human-readable line goes to stderr. `--json` also implies `
 
 ## What `--yes` covers, and what it never covers
 
-`--yes` auto-confirms **regenerable caches only**: sections 0-3, 5-10, 21, and 12-14 when the console is
+`--yes` auto-confirms **regenerable caches only**: sections 0-3, 5-10, 21, and 12-13 when the console is
 already elevated.
 
 | Never covered by `--yes` | Behaviour |
@@ -75,7 +75,7 @@ choice, and says so.
  "freed_bytes":0,"estimated_bytes":0,
  "sections":[{"section":1,"status":"ran","freed_bytes":0}],
  "candidates":[],"targets":[],
- "refusals":[],"log_file":"...","report_file":"..."}
+ "refusals":[],"excluded":[],"log_file":"...","report_file":"..."}
 ```
 
 | Key | Meaning |
@@ -88,12 +88,18 @@ choice, and says so.
 | `estimated_bytes` | What a dry-run says a real run would remove. `0` in a real run |
 | `sections[]` | One entry per section attempted: `section`, `status`, `freed_bytes` |
 | `candidates[]` | What an interactive section offered: `section`, `index`, `path`, `bytes`, `idle_days`, `project`. Always present, empty when none were collected |
-| `targets[]` | Scan mode only: `section`, `label`, `path`, `bytes`. Always present, empty otherwise |
-| `refusals[]` | Human-readable reasons a section was refused in batch mode |
+| `targets[]` | Scan mode only: `section`, `label`, `path`, `bytes`, `newest_write_utc`. Always present, empty otherwise |
+| `refusals[]` | Human-readable reasons a section was refused in batch mode, plus one `excluded: <path>` line per honoured `--exclude-path` |
+| `excluded[]` | Every path an exclusion actually kept, listed once each. Empty means "nothing was excluded", never "not reported" |
 | `log_file`, `report_file` | Absolute paths, or `null` under `--no-report` |
 
 `status` is one of `ran`, `dry-run`, `skipped`, `refused`, `failed`.
 
+`newest_write_utc` is ISO 8601 UTC (`2026-09-08T13:14:15Z`) - the newest of write, access and creation time
+found anywhere under that target, which is the same rule the idle gate uses. It is **`null`** when the
+target is absent or holds no files, rather than a zero date a caller would sort as if it were real. It is
+emitted only under `--json`, because computing it needs the file walk that `--json` already performs.
+
 ## Where output lands
 
 | Item | Path |
@@ -122,11 +128,9 @@ answered by a script, so `--elevate` does not belong in an unattended context.
 
 ## Guarantees
 
-- **No network calls of its own.** The self-test greps the source for HTTP and socket calls and fails the run
-  if it finds one. There is no telemetry and no update check.
-- **Every deletion passes one chokepoint** with a declared root, and is refused if it falls outside it.
-- **Protected paths are refused regardless of flags**: drive roots, Windows, Program Files, the profile root,
-  personal folders, credentials, toolchains, browser and editor state. No flag bypasses this.
+- - **No network calls of its own**. Self-test check [9] greps every source file for `Invoke-WebRequest`, `Invoke-RestMethod`, `Net.WebClient`, `HttpClient`, `Sockets.TcpClient`, `curl.exe` and `wget`, and fails the run if it finds one. There is no telemetry and no update check. `--report-issue` and `--feedback` hand a URL to the user's browser after they confirm, and neither belongs in an unattended run.
+- - **Every deletion of anything on the user's machine passes one chokepoint** with a declared root, and is refused if it falls outside it. windowsweep's own logs, reports and fixtures are the exception, reachable only through `--cleanup-logs`, `--prune-history` and `--uninstall-data`.
+- - **Protected paths are refused regardless of flags**: every drive root, fifteen declared roots (Windows, System32, SysWOW64, both Program Files folders, ProgramData, `C:\Users` with Default and Public, the profile root, and the AppData Roaming, Local and LocalLow folders), 66 protected subtrees, 50 path patterns and 13 file names. Two paths are declared exceptions - `%LOCALAPPDATA%\Android\Sdk\.temp` and `.downloadIntermediates` - and there are no others. No flag bypasses any of it.
 - **Junctions and symlinks are removed as links, never followed.**
 - **`--dry-run` and `--scan` write nothing** but the log and the report.
 - **Section numbers are a public contract.** 0-25 today; a section may be retired as a no-op, and a number is
@@ -188,8 +192,8 @@ In `--json` mode every section brackets itself on **stderr**:
 ```
 
 `status` is one of `ran`, `dry-run`, `skipped`, `refused`, `failed`. Scan mode also fills `targets[]`
-(`section`, `label`, `path`, `bytes`) in the final JSON line. `candidates` and `targets` are always present,
-empty when nothing was collected.
+(`section`, `label`, `path`, `bytes`, `newest_write_utc`) in the final JSON line. `candidates` and `targets`
+are always present, empty when nothing was collected.
 
 ## The read-only audits
 

package/CHANGELOG.md

@@ -9,6 +9,62 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [1.2.0] - 2026-09-08
+
+### Added
+
+- **`targets[].newest_write_utc` in `--scan --json`.** ISO 8601 UTC, the newest of write, access and creation
+  time found anywhere under the target - the same rule the idle gate uses - or `null` when the target is
+  absent or holds no files. It costs no extra walk: under `--json` the size pass already enumerates every
+  file, so the timestamp comes out of that same enumeration. A human `--scan` keeps the faster path.
+- **`protected` in `--list --json`.** `subtrees` (every protected folder, resolved for this machine) and
+  `categories` (the same four sentences `--list-targets` prints). Both readers now take the category list
+  from one constant, so the machine-readable copy cannot quietly promise less than the console does.
+- **`excluded[]` in the `--json` summary**, naming every path an exclusion actually kept, once each.
+
+### Changed
+
+- **`--exclude-path` is honoured in every section, not only section 17.** It was parsed globally and read by
+  exactly one consumer, so someone who excluded a folder was protected in one section and silently not in the
+  other twenty-five. It is now enforced at the deletion chokepoint itself - the one place every section
+  already passes through - and an excluded path is refused, logged as `excluded: <path>` and reported in
+  `excluded[]`. The same reach applies to `excludePaths` in the config file. **No deletion behaviour widens:
+  `--exclude-path` only ever refuses more.** A path that is both protected and excluded still reports the
+  protected reason, because that is the promise no flag can lift.
+
+### Fixed
+
+- 🔴 **`--exclude-path` only ever refused the path you named, never anything inside it.** The normalised
+  prefix was built with a PowerShell literal `'\'`, which is **two** characters, so the prefix ended in a
+  doubled backslash and no child path could ever match it. Excluding a folder protected the folder and
+  nothing in it - which is the opposite of what anyone excluding a folder means. The self-test check that
+  was supposed to cover this asserted only on the excluded path itself, so it passed throughout; it now
+  asserts on a child, and the fix was watched failing on the original bug reintroduced.
+- 🔴 **A dry-run counted files a real run would skip.** `Remove-StaleFiles` applied the protection guard
+  only in its real-run loop, so the rehearsal's estimate included protected and excluded files that the run
+  then refused - for exactly the files a person most wants the two numbers to agree about. One filter now
+  decides both, and a check proves a dry-run and a real prune report the same count and the same bytes.
+- **`--help` said `--permanent` covers "Sections 18/19".** It reaches **18, 19 and 23**: `Send-ToRecycleBin`
+  is called from `modules/personal.ps1` (18, 19) and from `modules/orphaned_appdata.ps1` (23). Someone who
+  passed `--permanent` believing it applied to two sections would have had section 23's orphaned
+  application data deleted outright instead of recycled. The reference docs already said 18, 19 and 23;
+  only the engine's own help text - the one place a person actually reads it from - was wrong.
+- **Section 22 declared `Dev = $true` with no behavioural branch**, so `--list --json` advertised a developer
+  flag that changed nothing. It now reads `false`, and the Dev column in `docs/sections.md` agrees.
+- 🔴 **`--scan` parsed `--developer` and `--not-developer` and then never read them.**
+  `Resolve-DeveloperMode` ran only for the walkthrough, the menu, `--all` and `--only`, so in scan mode the
+  flag reached `DeveloperFlag` and nothing looked at it: section 0 printed `Developer mode: not decided yet`
+  whatever you passed, and `--json` returned `developer: null`. The desktop window sends those flags to
+  `--scan` and could not read back the setting it had just sent. A scan now resolves it from the flag or the
+  saved answer and stops there - it may not ask the question, may not write `config.json`, and may not invent
+  a decision you never made, so with neither a flag nor a saved answer it still reports "not decided yet",
+  which is the truth. **No scan result changes:** the scan reports what is on disk, not what a run would
+  remove, and `Show-ScanTable` never read the developer answer in the first place.
+- **The hibernation target's one-line note contradicted the section's own explanation two lines below.** It
+  said `reduced` keeps Fast Startup "at roughly 40% of RAM", which is the size of the **whole** file; the
+  section intro says `reduced` is about half of that. The note now states the figure once, on the thing it
+  belongs to: the full file is about 40% of RAM and `reduced` keeps roughly half that.
+
 ## [1.1.0] - 2026-09-04
 
 ### Added

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Ahsan Mahmood
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Ahsan Mahmood
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -4,7 +4,7 @@
 
 <h1>windowsweep</h1>
 
-<p><strong>Safe-by-default Windows cleanup CLI - developer-aware, dry-run first, zero install via npx.</strong></p>
+<p><strong>Developer-aware Windows cleanup CLI: dry-run first, personal folders refused, zero install via npx.</strong></p>
 
 [![npm version](https://img.shields.io/npm/v/windowsweep.svg)](https://www.npmjs.com/package/windowsweep)
 [![downloads](https://img.shields.io/npm/dm/windowsweep.svg)](https://www.npmjs.com/package/windowsweep)
@@ -19,16 +19,18 @@
 
 > [!IMPORTANT]
 > **This tool deletes files.** Most of what it removes are caches that rebuild themselves; personal files it
-> lists go to the Recycle Bin; two sections (emptying the Recycle Bin, clearing event logs) are permanent and
-> gated behind a separate flag. Start with `npx windowsweep --scan`, which deletes nothing, then
+> lists go to the Recycle Bin; and two sections - emptying the Recycle Bin, clearing event logs - are
+> permanent, with no undo of any kind. Those two sit behind `--i-understand-deep`, along with the hibernation
+> file and disk-image compaction. Start with `npx windowsweep --scan`, which deletes nothing, then
 > `npx windowsweep --dry-run --all --yes`, which shows exactly what a real run would remove.
 > **Windows only** - npm refuses to install it elsewhere.
 
-`windowsweep` reclaims the disk space that quietly disappears on a Windows machine: package-manager and build
-caches, browser and app caches, Windows temp and update leftovers, stale `node_modules`, half-finished downloads.
-It is a PowerShell tool with a thin Node launcher, so `npx windowsweep` runs it with nothing to install. What
-sets it apart is restraint: it asks whether you are a developer and keeps the caches you used in the last
-100 days, it names every path before touching it, it never follows a junction, and it makes no network calls.
+What it reclaims is the disk space that quietly disappears on a Windows machine: package-manager and build caches,
+browser and app caches, Windows temp and update leftovers, stale `node_modules`, half-finished downloads.
+It names every path before it touches one, keeps the caches you used in the last 100 days, never follows a
+junction and makes no network calls at all. One question on the first run decides whether your developer caches
+are pruned on the idle gate or cleared completely. A PowerShell engine sits behind a thin Node launcher, so `npx
+windowsweep` runs it with nothing to install.
 It is the Windows member of a family with [linux-cleanup](https://github.com/aoneahsan/linux-cleanup) and
 [macleanup](https://github.com/aoneahsan/macleanup).
 
@@ -41,7 +43,7 @@ It is the Windows member of a family with [linux-cleanup](https://github.com/aon
 | **Platforms** | Windows 10 (1809+) and Windows 11 |
 | **Install size** | ~109 kB packed · ~366 kB unpacked · 44 files · no dependencies |
 | **Undo** | Recycle Bin for personal files; none for caches (they regenerate) |
-| **Status** | Stable · actively maintained |
+| **Status** | Stable · 1.1.0, released 2026-09-04 |
 
 <a id="table-of-contents"></a>
 ## 🧭 Table of Contents&nbsp;[#](#table-of-contents)
@@ -57,6 +59,7 @@ It is the Windows member of a family with [linux-cleanup](https://github.com/aon
 - [💻 Command Line](#command-line)
 - [🧪 Examples](#examples)
 - [🎛️ Advanced Features](#advanced-features)
+- [🖥️ Desktop app](#desktop-app)
 - [🚑 Recovery & Troubleshooting](#recovery-troubleshooting)
 - [🚧 Limitations](#limitations)
 - [❓ FAQ](#faq)
@@ -78,8 +81,8 @@ Yarn and npm caches, Gradle, Cypress and Playwright browsers, Android emulator i
 `node_modules` for a project you finished in spring, editor caches, two hundred profiles' worth of Chrome cache.
 Clearing them by hand means keeping a private list of paths and remembering which ones bite back.
 
-A cleaner that wipes every cache it finds trades one problem for another: the next `yarn install` re-downloads
-twelve gigabytes and your afternoon is gone. `windowsweep` takes the narrower path.
+A cleaner that clears every cache it finds trades one problem for another: the next `yarn install` downloads
+the lot again, and your afternoon is gone. `windowsweep` takes the narrower path.
 
 | | `windowsweep` | Windows Disk Cleanup / Storage Sense | A wipe-everything cleaner |
 |---|---|---|---|
@@ -93,22 +96,25 @@ twelve gigabytes and your afternoon is gone. `windowsweep` takes the narrower pa
 
 Nothing here can promise a number. How much comes back depends on your disk; `--scan` measures it.
 
-**Not the right tool when** you want a graphical, set-and-forget cleaner; when you are on Linux or macOS (use the
-siblings); when you want an undo for caches (there is none - they regenerate); or when you are looking for a
-security scanner or a registry cleaner. It reclaims disk space, nothing else.
+**Not the right tool when** you want a set-and-forget cleaner that runs itself; when you are on Linux or macOS (use
+the siblings); when you want an undo for caches (there is none - they regenerate); or when you are looking for a
+security scanner or a registry cleaner. The rest of what it cannot do is under [Limitations](#limitations). It
+reclaims disk space, nothing else.
 
 <a id="features"></a>
 ## ✨ Features&nbsp;[#](#features)
 
 - **Developer mode** - one question on the first run. Yes keeps package, build and test-runner caches used in
   the last 100 days and the newest version of every versioned tool; no clears them completely.
-- **26 numbered sections** - from package-manager caches to Windows Update leftovers, plus four read-only
-  audits (global packages, orphaned app data, idle programs, startup items), each naming its paths before it
-  acts. Numbers are a public contract.
-- **One deletion chokepoint** - refuses drive roots, Windows, Program Files, your profile root, personal
-  folders, credentials, toolchains and browser or editor state; asserts every deletion sits inside its declared
-  target; never follows a junction or symlink; handles paths beyond 260 characters; skips files another program
-  has open.
+- **26 numbered sections** - from package-manager caches to Windows Update leftovers, plus three read-only
+  audits (global packages, idle programs, startup items) that report and delete nothing. Orphaned application
+  data is a fourth 1.1.0 section and is **not** an audit: it asks you to pick, row by row, and what you pick
+  goes to the Recycle Bin. Every section names its paths before it acts, and the numbers are a public
+  contract.
+- **One deletion chokepoint** - refuses drive roots, Windows, Program Files, your profile root, personal folders,
+- credentials, toolchains and browser or editor state; asserts every deletion sits inside its declared target; never
+- follows a junction or symlink; handles paths beyond 260 characters; skips files another program has open. Self-test
+- check [6] walks every directory and file target and fails if one resolves inside a protected path.
 - **A dry-run that writes nothing** - `--dry-run` short-circuits every deletion and every destructive command
   and reports an exact estimate. `--scan` and `--list-targets` are read-only.
 - **Personal files go to the Recycle Bin** - partial downloads and large stale files are listed, you pick, and
@@ -120,18 +126,19 @@ security scanner or a registry cleaner. It reclaims disk space, nothing else.
 - **Running-app guard** - an open browser, editor or app keeps its caches; the tool tells you which to close.
 - **Session reports** - schema-versioned JSON, exportable to Markdown or a self-contained HTML page, plus
   `--json` for scripts.
-- **Self-test** - 151 checks prove the guards on your machine with a real junction, a 400-character path and
+- **Self-test** - 151 checks prove the guards on your machine with a real junction, a 445-character path and
   a dry-run fixture before you trust it.
-- **Offline by design** - zero network calls, no telemetry, no update check. Crash bundles stay on disk.
+- **Offline by design** - the command-line tool makes zero network calls: no telemetry, no update check.
+  Self-test check [9] fails the build on an HTTP or socket call in the source. Crash bundles stay on disk.
 
 <a id="platform-support"></a>
 ## 📱 Platform Support&nbsp;[#](#platform-support)
 
 | Platform | Supported | Notes |
 |---|---|---|
-| Windows 11 | ✅ | Same engine and PowerShell hosts; a real run on Windows 11 is on the verification list ([roadmap](https://github.com/aoneahsan/windowsweep/blob/main/remaining-work-summary.md)) |
+| Windows 11 | ✅ | Same engine and PowerShell hosts; a real run on Windows 11 is on the verification list ([project status](https://github.com/aoneahsan/windowsweep/blob/main/docs/features/windowsweep-completion/00-tracker.json)) |
 | Windows 10 (1809 and later) | ✅ | The primary development target; every real run so far |
-| Windows Server 2019+ | ⚠️ | Uses nothing newer than 1809; CI runs the self-test and a dry-run on Windows Server (`windows-latest`) on every push, but no real cleanup has been run on Server |
+| Windows Server 2019+ | ⚠️ | Uses nothing newer than 1809; CI runs the self-test and a dry-run on Windows Server (`windows-latest`) on every push to `main` and every pull request, but no real cleanup has been run on Server |
 | Linux | ❌ | `os: ["win32"]` makes npm refuse to install; use [linux-cleanup](https://github.com/aoneahsan/linux-cleanup) |
 | macOS | ❌ | Use [macleanup](https://github.com/aoneahsan/macleanup) |
 
@@ -178,7 +185,7 @@ survives `npx` evictions. Full detail:
 <a id="quick-start"></a>
 ## 🚀 Quick Start&nbsp;[#](#quick-start)
 
-Prove the guards, look, rehearse, then clean:
+Prove the guards, look, rehearse, then reclaim:
 
 ```powershell
 npx windowsweep --self-test
@@ -205,7 +212,7 @@ comes back but costs minutes, *Recycle Bin* is recoverable until you empty it (`
 | 1 | Package-manager caches (npm, yarn, pnpm, bun, deno, pip, uv, Composer, NuGet, Cargo, Go, pub) | rebuilds | - | safe · developer-gated |
 | 2 | Build-tool caches (Gradle, Maven, Android, Unity, JetBrains) | rebuilds | - | safe · developer-gated |
 | 3 | Test-runner browsers (Cypress, Playwright, Puppeteer) - newest kept | rebuilds | - | safe · developer-gated |
-| 4 | Android emulators idle N+ days | slow | - | opt-in |
+| 4 | Android emulators idle N+ days | slow | - | opt-in, developer-gated |
 | 5 | Docker: dangling layers, build cache, unused images older than N days | rebuilds | - | safe · developer-gated |
 | 6 | Editor caches, dead workspace storage, uninstalled extension folders | rebuilds | - | safe |
 | 7 | Browser caches, every profile (Chrome, Edge, Brave, Vivaldi, Opera, Firefox, ...) | rebuilds | - | safe |
@@ -218,10 +225,10 @@ comes back but costs minutes, *Recycle Bin* is recoverable until you empty it (`
 | 14 | Component store cleanup (DISM) | rebuilds | yes | opt-in |
 | 15 | Hibernation file off or reduced | config | yes | deep |
 | 16 | Clear Windows Event Logs | **permanent** | yes | deep |
-| 17 | Stale project build artefacts (`node_modules`, `dist`, `.next`, `target`, ...) | rebuilds | - | interactive |
+| 17 | Stale project build artefacts (`node_modules`, `dist`, `.next`, `target`, ...) | rebuilds | - | interactive, developer-gated |
 | 18 | Partial / orphan downloads | Recycle Bin | - | interactive |
 | 19 | Large stale personal files in Downloads | Recycle Bin | - | interactive |
-| 20 | Docker Desktop / WSL disk-image compaction | config | yes | deep |
+| 20 | Docker Desktop / WSL disk-image compaction | config | yes | deep, developer-gated |
 | 21 | Disk usage report | report | - | safe |
 | 22 | Global packages audit (npm, pnpm, yarn, bun, deno) - never uninstalls | report | - | safe · audit only |
 | 23 | Orphaned application data under AppData | Recycle Bin | - | interactive |
@@ -234,14 +241,14 @@ comes back but costs minutes, *Recycle Bin* is recoverable until you empty it (`
 `--profile audit` is where they live. Every section is documented in
 [Sections 0-25](https://github.com/aoneahsan/windowsweep/blob/main/docs/sections.md).
 
-### Clean interactively
+### Reclaim interactively
 
 ```powershell
 windowsweep            # guided walkthrough, one confirmation per step
 windowsweep --menu     # jump to one section; toggle dry-run and auto-yes
 ```
 
-### Clean unattended
+### Reclaim unattended
 
 ```powershell
 windowsweep --all --yes
@@ -307,9 +314,10 @@ windowsweep [mode] [options]
 | `--temp-days N` | `3` | Idle window for temp folders |
 | `--purge-all` | off | 🔥 Clear cache targets completely instead of pruning idle files |
 | `--developer`, `--not-developer`, `--forget-developer` | saved answer | Override or re-ask the developer question |
-| `--scan-roots "P1;P2"`, `--exclude-path P` | auto | Section 17 roots and exclusions |
+| `--scan-roots "P1;P2"` | auto | Section 17 project roots |
+| `--exclude-path P` | - | A tree to leave alone, in **every** section (repeatable) |
 | `--hiberfil off\|reduced\|keep` | ask | What section 15 does |
-| `--permanent` | off | Sections 18/19 delete instead of using the Recycle Bin |
+| `--permanent` | off | Sections 18, 19 and 23 delete instead of using the Recycle Bin |
 | `--select L`, `--select-file P` | off | Answer an interactive section's selection in advance, by index or by path - the one way sections 17/18/19/23 run unattended |
 | `--notify` | off | A Windows notification when the run ends |
 | `--json`, `--quiet`, `--no-color`, `--ascii`, `--no-report`, `--cleanup-logs` | off | Output and record controls |
@@ -322,12 +330,12 @@ Every flag, exit code and environment variable:
 
 | Goal | Command |
 |---|---|
-| See what is reclaimable, risk-free | `windowsweep --scan` |
+| See what is reclaimable, without deleting anything | `windowsweep --scan` |
 | Rehearse tonight's cleanup | `windowsweep --dry-run --all --yes` |
-| Reclaim the most space as a developer | `windowsweep --profile dev --yes` |
+| Reclaim the most space as a developer | `windowsweep --profile dev --yes --dry-run` first; the `dev` profile includes interactive section 17, so a real `--yes` run exits 3 unless you add `--select-file` |
 | Reclaim everything a non-developer can | `windowsweep --all --yes --not-developer` |
-| Find `node_modules` in projects idle 6 months | `windowsweep --only 17 --days 180 --scan-roots "D:\work"` |
-| Free the browser caches after closing the browsers | `windowsweep --only 7 --yes` |
+| Find `node_modules` in projects idle 6 months | `windowsweep --only 17 --days 180 --scan-roots "D:\work" --dry-run` |
+| Reclaim the browser caches after closing the browsers | `windowsweep --only 7 --yes` |
 | Run the admin sections | `windowsweep --profile system --yes --elevate` |
 | Weekly unattended run | `windowsweep --install-task` |
 | Machine-readable output for a script | `windowsweep --all --yes --json` |
@@ -347,7 +355,24 @@ Every flag, exit code and environment variable:
   [Docs](https://github.com/aoneahsan/windowsweep/blob/main/docs/admin-and-elevation.md)
 - **Report export** - schema-versioned JSON to Markdown or a self-contained HTML page, no extra tools.
   [Docs](https://github.com/aoneahsan/windowsweep/blob/main/docs/reports-and-logs.md)
-- **Crash bundles** - captured locally on an unexpected exit, never transmitted.
+- **Crash bundles** - the command line writes one locally on an unexpected exit, never transmitted.
+
+<a id="desktop-app"></a>
+## 🖥️ Desktop app&nbsp;[#](#desktop-app)
+
+A Tauri window that drives this engine rather than reimplementing it: it runs the bundled `windowsweep.ps1` with `--json --no-color` and carries no cleanup logic of its own. The chokepoint, the protected lists and every refusal are the command line's.
+
+- **A run you can watch.**
+- **A picker** for the four sections that ask a person to choose.
+- **Settings, most of them flags.**
+
+Screen by screen: [Desktop app](https://github.com/aoneahsan/windowsweep/blob/main/docs/desktop.md).
+
+The engine still makes no network calls at all. The window sends usage and crash reports to improve the product for everyone, and there is no switch. Never sent: a file path, a folder name, a drive label, your user name, your machine name, or the contents of anything. Sign-in is separate and optional.
+
+The installer is not signed with a paid code-signing certificate, so SmartScreen warns on first run. Every release publishes a SHA-256 checksum and a minisign signature the app's own updater checks; neither is a code-signing certificate. What to do about the dialog: [Desktop app](https://github.com/aoneahsan/windowsweep/blob/main/docs/desktop.md).
+
+Download the `.msi` or the `.exe` installer from [Releases](https://github.com/aoneahsan/windowsweep/releases). What each one installs, and what Windows says the first time: [Desktop app](https://github.com/aoneahsan/windowsweep/blob/main/docs/desktop.md).
 
 <a id="recovery-troubleshooting"></a>
 ## 🚑 Recovery & Troubleshooting&nbsp;[#](#recovery-troubleshooting)
@@ -375,7 +400,7 @@ More: [Troubleshooting](https://github.com/aoneahsan/windowsweep/blob/main/docs/
   newest of write, access and creation time - a file can only look fresher than it is, never older. Some old
   caches survive the default window; `--days` and `--purge-all` exist for that.
 - **Admin sections need an elevated console** and a UAC click; a Scheduled Task runs the safe batch only.
-- **Disk Cleanup (section 13) cannot preview** how much it will free; its dry-run lists the handlers only.
+- **Disk Cleanup (section 13) cannot preview sizes.** Its dry-run names the handlers it would run and nothing more.
 - **No automated test suite beyond `--self-test`.** Correctness rests on the self-test's fixtures, dry-runs and
   real runs on Windows 10 and 11.
 
@@ -387,8 +412,10 @@ Not from a protected folder, and not without asking. Documents, Desktop, Picture
 hard refusals. Section 17 lists build artefacts in idle projects and removes only what you select.
 
 **Does it phone home?**
-No. Zero network calls, no telemetry, no update check. The self-test greps the source for HTTP and socket
-calls; `--report-issue` opens your browser at a pre-filled page you submit yourself.
+Not the command-line tool. Zero network calls, no telemetry, no update check. The self-test greps the source for
+HTTP and socket calls; `--report-issue` opens your browser at a pre-filled page you submit yourself. The desktop
+window is a separate program and does send usage and crash reports. What it never sends is listed under [Desktop
+app](#desktop-app).
 
 **Why keep files used in the last 100 days?**
 Because a developer's caches are what make the next install fast. `--days 30` or `--purge-all` when you want
@@ -417,8 +444,9 @@ More: [FAQ](https://github.com/aoneahsan/windowsweep/blob/main/docs/faq.md).
 | [Admin sections and elevation](https://github.com/aoneahsan/windowsweep/blob/main/docs/admin-and-elevation.md) | before running the system profile or touching the hibernation file |
 | [Reports and logs](https://github.com/aoneahsan/windowsweep/blob/main/docs/reports-and-logs.md) | parsing the JSON or finding a log |
 | [AI integration guide](https://github.com/aoneahsan/windowsweep/blob/main/AI-INTEGRATION-GUIDE.md) | an agent or a script runs it for you |
+| [Desktop app](https://github.com/aoneahsan/windowsweep/blob/main/docs/desktop.md) | you want the window rather than the command line |
 | [Troubleshooting](https://github.com/aoneahsan/windowsweep/blob/main/docs/troubleshooting.md) | something failed |
-| [Roadmap and remaining work](https://github.com/aoneahsan/windowsweep/blob/main/remaining-work-summary.md) | you want to know what is verified, what is planned (1.1, the docs site) and what is still open |
+| [Project status](https://github.com/aoneahsan/windowsweep/blob/main/docs/features/windowsweep-completion/00-tracker.json) | you want to know what is verified and what is still open: every phase and sub-task with its state and evidence |
 
 <a id="changelog"></a>
 ## 🔄 Changelog&nbsp;[#](#changelog)

package/VERSION

@@ -1 +1 @@
-1.1.0
+1.2.0