dev-prune-darwin-arm64 1.17.0 → 1.19.0

package/README.md

@@ -52,7 +52,7 @@ gigabytes hostage for a build you are not running.
 
 `dev-prune` finds those directories across every Git repository you register, and deletes
 them — but only after proving the exact command that puts them back would succeed. It
-knows twenty-four package managers, not just the obvious four: Composer, Bundler, Mix,
+knows twenty-five package managers, not just the obvious four: Composer, Bundler, Mix,
 CocoaPods and Terraform are as first-class as npm and pip. It is a single Rust binary,
 installs its own background schedule, and answers to two names: `dev-prune` and `devp`.
 
@@ -115,6 +115,11 @@ All three download the prebuilt binary for your platform, verify its published S
 put it on `PATH`, and run `dev-prune setup`. Pass `--no-auto-setup` / `-NoAutoSetup` to
 skip that last step.
 
+A binary you download and run by hand asks first instead: the first attended run opens
+the settings walkthrough before anything is installed, finishing it is the yes, and
+quitting it means nothing is installed — durably, until you say otherwise with
+`devp setup`.
+
 Re-run any of them whenever you like. An install that is already current, complete and on
 `PATH` is left exactly as it is and exits `0` without downloading; an older one is updated
 in place; a newer one is not downgraded. `--force` / `-Force` writes it again regardless.
@@ -127,17 +132,23 @@ problem.
 ### From a package manager
 
 ```bash
-npm install -g dev-prune      # or: npx dev-prune status
-bun add -g dev-prune          # same package, through bun
-pnpm add -g dev-prune
-yarn global add dev-prune     # Yarn 1.x
-uv tool install dev-prune     # or: uvx dev-prune status
-pipx install dev-prune
-pip install dev-prune
-cargo binstall dev-prune      # fetches the prebuilt release archive
-cargo install dev-prune       # builds from source, needs Rust 1.88+
+npm install -g dev-prune@latest    # or: npx dev-prune status
+bun add -g dev-prune@latest        # same package, through bun
+pnpm add -g dev-prune@latest
+yarn global add dev-prune@latest   # Yarn 1.x
+uv tool install dev-prune@latest   # or: uvx dev-prune status
+pipx install --force dev-prune
+pip install --upgrade dev-prune
+cargo binstall dev-prune           # fetches the prebuilt release archive
+cargo install dev-prune            # builds from source, needs Rust 1.88+
 ```
 
+Each command installs the latest version *and* updates an existing copy — the same
+line works for both. That is what the `@latest`, `--force` and `--upgrade` spellings
+are for: the bare forms report "already installed" and change nothing, which looks
+like an update and isn't. (`cargo install` rebuilds on its own whenever a newer
+version exists.)
+
 The [npm](https://www.npmjs.com/package/dev-prune) and
 [PyPI](https://pypi.org/project/dev-prune/) packages **contain the binary** — there is no
 download step at install time, so they work under `npm ci --ignore-scripts`, behind a
@@ -185,8 +196,8 @@ brew install https://raw.githubusercontent.com/Life-Experimentalist/dev-prune/ma
 scoop install https://raw.githubusercontent.com/Life-Experimentalist/dev-prune/main/packaging/scoop/dev-prune.json
 ```
 
-WinGet is [submitted and in review](https://github.com/microsoft/winget-pkgs/pull/422809);
-`winget install VKrishna04.dev-prune` starts resolving when that pull request merges.
+dev-prune is not in WinGet yet — `winget install VKrishna04.dev-prune` does not
+resolve. On Windows, use Scoop or the install script instead.
 
 The two Python entry points differ in where they land. `pip install` follows whichever
 environment is active, so inside a virtualenv `devp` lives in that venv's `Scripts`/`bin`
@@ -320,8 +331,8 @@ so they are worth copying rather than typing.
 | [Open VSX](https://open-vsx.org/extension/VKrishna04/dev-prune) | **`VKrishna04.dev-prune`** | The same extension, for VSCodium, Cursor, Windsurf, Positron and Kiro. |
 | [SchemaStore](https://www.schemastore.org/) | **`.devprune.json`** | The config schema, by filename. No extension and no `$schema` key needed. |
 
-[WinGet](https://github.com/microsoft/winget-pkgs/pull/422809) is submitted and in
-review. It is not in the table because it does not resolve yet.
+WinGet is not in the table because dev-prune is not in `winget-pkgs` yet, so
+`winget install VKrishna04.dev-prune` does not resolve.
 
 Two of those rows are not installs of dev-prune at all. SchemaStore is why JetBrains
 IDEs, Visual Studio, Neovim and Zed validate `.devprune.json` with nothing installed —
@@ -617,7 +628,7 @@ process that leaves a dirty working tree is a surprise.
 | 🐳 **Container report**                        | `devp caches docker` (also `podman`, `nerdctl`, `finch`, Apple's `container`, or `containers` for all of them plus local Kubernetes clusters) breaks a container engine's disk into images, containers, local volumes and build cache, each with what the engine itself calls reclaimable, and prints the prune commands narrowest first with what each takes with it. `devp caches clear docker` then runs the narrow ones for you, after asking, and counts them in `devp stats` — **never a volume**, and never from a scheduler or a hook. `devp caches` carries a one-line summary per engine, outside its own total |
 | 📊 **Cache report**                            | `devp caches` sizes every package manager cache and store on the machine — npm to cargo to conda, Maven, Gradle, NuGet, vcpkg, Conan, Composer, CocoaPods, Hex, Bundler, pub, SwiftPM, Terraform, Poetry, PDM and Deno — and prints the command that clears each. It also finds the stores that belong to no package manager at all and are routinely the largest things in the list: the Playwright and Puppeteer browser bundles, the Cypress binary cache, the Electron and electron-builder download caches, and the HuggingFace hub — a whole browser or model per version, and nothing ever removes the old one. The report is read-only; `devp caches clear <manager>` runs that command for you, after asking. `devp config set cache_max_gb default=10` says how big is too big — for every manager at once, or per manager with `default=10,npm=4` — and marks the ones past it — `devp caches clear --over-cap all` then empties exactly those, still only when you type it. Each manager also says how many of your registered repositories use it and what that works out to per repository, and `devp caches clear --unused all` empties the ones nothing uses at all. pnpm is reported once per filesystem, because a store it hardlinks into `node_modules` cannot cross one and projects kept off the system disk get a store of their own. Nothing on a schedule ever touches a cache, and Maven's `~/.m2/repository` is never cleared at all — it holds artifacts `mvn install:install-file` put there that no remote can hand back |
 | 🩺 **`devp doctor`**                           | One read-only pass that ends by naming the *single* reason a repository would or would not be pruned. Runs no package manager, repairs nothing, safe to run twice. `devp doctor --fix` then mends what it found — installed-but-broken only                                                                                                                 |
-| 🤖 **Self-installing automation**              | OS-native scheduler (Task Scheduler, LaunchAgent, systemd user timer) and non-blocking Git hooks, installed at install time and restored after an upgrade. `auto_setup`, `auto_hooks`, `auto_daemon` or `DEV_PRUNE_NO_AUTO_SETUP=1` turn it off                                                                                                             |
+| 🤖 **Self-installing automation**              | OS-native scheduler (Task Scheduler, LaunchAgent, systemd user timer) and non-blocking Git hooks, installed once the first run’s walkthrough is accepted (quitting it installs nothing) and restored after an upgrade. `auto_setup`, `auto_hooks`, `auto_daemon` or `DEV_PRUNE_NO_AUTO_SETUP=1` turn it off                                                                                                             |
 | ⚡ **0ms opt-out**                             | An `ignore.devprune.json` in a repository root is honoured by file presence alone — no read, no parse. It applies at registration as well: a bulk scan (`devp init`, and the scheduled pass's own discovery) will not register a repository that holds it, so a repository can decline before it ever reaches `devp status`. `devp link <path>` still registers one, because naming a single repository is not a bulk scan                                                                                                                                                                                                                                                       |
 | 🔌 **`--json` on every reporting command**     | `run`, `status`, `stats`, `trust` and `caches` each emit one versioned document on stdout, diagnostics on stderr. Built for scripts and agents                                                                                                                                                                                                              |
 | 🧠 **AI agent skill**                          | A token-lean `SKILL.md` embedded in the binary; `devp skill` exports it and prints onboarding prompts for Claude Code, Gemini Antigravity, Cursor, Windsurf, Copilot and OpenClaw, and the repository doubles as a Claude Code plugin marketplace                                                                                                                                                                           |
@@ -648,7 +659,7 @@ process that leaves a dirty working tree is a surprise.
 | `devp doctor [PATH]`   | `--fix`                                                             | Diagnoses the installation, or one repository — ending with the single reason a pass would or would not touch it. `--fix` repairs what the checks found; it never performs a first-time install                                                               |
 | `devp config [ACTION]` | `get`, `set`, `show`, `wizard`, `project`, `daemon`, `hook`, `icon` | Global settings, per-repository `.devprune.json`, scheduler, Git hooks, file manager icons                                                                                                                                                                    |
 | `devp setup`           | `--status`                                                          | Installs any missing integration; `--status` only reports                                                                                                                                                                                                     |
-| `devp update`          | `--offline`, `--install`                                            | Prints the installed version, checks GitHub for a newer release, shows the upgrade command for your install channel; `--install` runs that upgrade through the channel that owns this copy                                                                    |
+| `devp update`          | `--offline`, `-y`, `--install`                                      | Prints the installed version, checks GitHub for a newer release, shows the upgrade command for your install channel, then asks `[y/N]` before installing when there is one; `-y` answers yes, `--install` skips the report and installs straight away |
 | `devp skill`           | `--agent <editor>`                                                  | Exports `SKILL.md` and prints AI agent onboarding prompts; `--agent` writes per-repository rules for 16 editors — Cursor, Windsurf, Antigravity, Cline, Roo, Kilo Code, Continue, Amazon Q, Kiro, Trae, Junie, Gemini CLI, Zed, Copilot, Aider or `AGENTS.md` |
 | `devp man`             | `--dir <dir>`                                                       | The manual as man pages, generated from the same argument definitions `--help` prints; alone it emits `devp(1)` to stdout, `--dir` writes the full set                                                                                                        |
 | `devp uninstall`       | `--deep`                                                            | Removes the scheduler, hooks, both binaries and every other installed copy it can find on the machine; `--deep` also clears configuration                                                                                                                     |
@@ -702,11 +713,11 @@ Adapters detect the project, verify the lockfile, and own the bloat directories:
 A required binary that is missing is a reason to skip, never a reason to delete: if `npm`
 is not on `PATH`, the `node_modules` it owns is left exactly where it is.
 
-The eight build-tool adapters ship **disabled**, because a build tree is regenerated
+The nine build-tool adapters ship **disabled**, because a build tree is regenerated
 by recompiling, not downloading — it costs more to get back. `devp config set
 enable_cargo true` / `enable_gradle true` / `enable_maven true` / `enable_swift true` /
 `enable_dart true` / `enable_mix_build true` / `enable_vcpkg true` /
-`enable_cmake_build true` switches them on, and their candidates wait for
+`enable_cmake_build true` / `enable_dotnet_build true` switches them on, and their candidates wait for
 `build_idle_days` (45 by default), applied as the *maximum* of it and `idle_days` — the
 build-tool gate only ever makes pruning later, never earlier.
 
@@ -816,7 +827,7 @@ once on a first install — so the defaults are something you agreed to rather t
 inherited — and again after an upgrade adds a setting you have never been shown.
 
 If you already know what you want, `devp config recommended` is the one-command version:
-it turns on the eight adapters and build trees that are off by default because they are
+it turns on the nine adapters and build trees that are off by default because they are
 not universally wanted, and leaves `allow_manifest_rewrite` — the one recommendation
 that edits files Git tracks — named, explained and off unless you add
 `--with-cautious`. `devp config show` lists whatever you have not taken yet.
@@ -854,7 +865,7 @@ rather than downloading. That is the whole reason each one is a switch.
 
 | Key | Default | Meaning |
 | :--- | :---: | :--- |
-| `enable_cargo` … `enable_cmake_build` | `false` | Turn on an opt-in build-tool adapter; `build_idle_days` (`45`) gates all eight |
+| `enable_cargo` … `enable_dotnet_build` | `false` | Turn on an opt-in build-tool adapter; `build_idle_days` (`45`) gates all nine |
 
 **Shared download caches** — one key, because the cap only ever marks.
 
@@ -1002,6 +1013,11 @@ non-blocking `post-commit`, `post-checkout` and `post-merge` Git hooks that regi
 repositories as you visit them. Both are reinstated after an upgrade if anything went
 missing.
 
+None of it arrives unasked. A machine that has never agreed opens the settings
+walkthrough on its first attended run, before anything is installed: finishing the
+walkthrough is the yes, quitting it is a durable no, and `devp setup` changes the
+answer whenever you like.
+
 ```bash
 devp setup --status              # what is installed, what is not, and why
 devp config set auto_setup false # stop the unattended pass entirely

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-prune-darwin-arm64",
-  "version": "1.17.0",
+  "version": "1.19.0",
   "description": "Prebuilt dev-prune binary for darwin arm64. Installed automatically by the 'dev-prune' package; not meant to be depended on directly.",
   "os": ["darwin"],
   "cpu": ["arm64"],