@zackees/soldr 0.8.19 → 0.8.21

package/README.md

@@ -18,7 +18,7 @@ Third-party comparison (soldr vs Swatinem/rust-cache vs ...): published from `za
 
 *[performance details](https://zackees.github.io/soldr/)*
 
-Cold builds are a wash; warm and cross-worktree share are where soldr's wrapper architecture pays off. Full historical trend + interactive view: [zackees.github.io/soldr](https://zackees.github.io/soldr/). For the swatinem/rust-cache comparison (GHA target-dir caching, a different layer) see [PERF.md](PERF.md#readme-comparison-bars-issue-785).
+Cold builds are a wash; clean-target reconstruction from a warm compiler cache and cross-worktree sharing are where soldr's wrapper architecture pays off. The README chart's clean-target row intentionally deletes `target/`; it does not claim Cargo's intact-target freshness fast path. Full historical trend + interactive view: [zackees.github.io/soldr](https://zackees.github.io/soldr/). For the swatinem/rust-cache comparison (GHA target-dir caching, a different layer) see [PERF.md](PERF.md#readme-comparison-bars-issue-785).
 
 **Instant tools. Instant builds. One command.**
 
@@ -169,13 +169,13 @@ When you run `soldr`, the tool should do the obvious thing:
 - pick MSVC on Windows by default
 - fetch the tool you asked for
 - cache it locally
-- fetch and manage zccache so Rust builds get transparent caching without manual wrapper setup
+- run the built-in zccache service so Rust builds get transparent caching without manual wrapper setup
 
 If soldr solves that one problem well, it becomes a super tool: the command you reach for first, because it makes the rest of the stack behave.
 
 - **Tool acquisition** (the crgx half): Need `maturin`, `cargo-dylint`, or any crate binary? soldr fetches a pre-built binary from GitHub Releases in seconds. No `cargo install` from source. Cached locally for instant reuse. On `0.5.x`, this is still an upstream trust decision rather than a repo-side trust guarantee; see [docs/TRUST_BOUNDARIES.md](./docs/TRUST_BOUNDARIES.md).
 
-- **Compilation caching** (the zccache half): `soldr cargo ...` now fetches and manages a pinned `zccache` release for Rust builds. soldr owns the zccache daemon/session wiring and keeps managed zccache artifacts under Soldr's cache root.
+- **Compilation caching** (the zccache half): `soldr cargo ...` uses the zccache service compiled into Soldr. soldr owns the daemon/session wiring and keeps its object store under the active Soldr root at `cache/zccache/daemon-state/embedded-v1/<zccache-version>/objects`, so production and development roots remain isolated.
 
 ```bash
 # Build through soldr's front door:
@@ -240,11 +240,26 @@ files touched. What you get over `build-backend = "maturin"`:
 - **Compilation caching** — rustc invocations run under soldr's
   `RUSTC_WRAPPER`, so repeat builds hit the cache.
 
-Local PEP 517 builds use a lightweight `dev` profile by default: line-table
-debug information, no LTO, and incremental compilation. Explicit maturin/Cargo
-profiles and `SOLDR_PEP517_PROFILE` remain authoritative; release pipelines
+Local PEP 517 builds use an explicit fast `dev` profile by default:
+`opt-level = 0`, 256 codegen units, line-table debug information, no LTO, and
+incremental compilation. Explicit Maturin/Cargo settings and
+`SOLDR_PEP517_PROFILE` remain authoritative per setting; release pipelines
 should select their release profile explicitly.
 
+Successful wheel and editable builds print a one-line cache and timing summary
+to stderr. Set `SOLDR_PEP517_STATS=off` to silence it; `SOLDR_PEP517_STATS=full`
+(and detected verbose `pip`/`uv` frontends) also prints the complete session
+statistics payload.
+
+Soldr also caches the last successful wheel for each project/build mode under
+`<effective-soldr-root>/pep517/wheels/`. The backend asks the selected soldr
+binary for this root, so official (`.soldr`), development (`.soldr-dev`), and
+custom roots remain separate even when `SOLDR_CACHE_DIR` was initially unset.
+Before packaging it scans source and staged-artifact
+metadata (relative path, size, and modification time); an unchanged tree
+hardlinks the cached wheel into pip's requested output directory and skips
+wheel rebuilding/compression. Set `SOLDR_PEP517_WHEEL_CACHE=off` to opt out.
+
 Projects whose packaging backend is not maturin can use soldr as a managed
 wrapper by selecting a delegate in `pyproject.toml`:
 
@@ -367,7 +382,13 @@ If you also have many separate test binaries, consider consolidating them under
 - **Front-door builds**: `soldr cargo ...` is the primary build UX.
 - **Invisible caching**: `soldr cargo ...` uses a soldr-managed zccache by default, with `soldr --no-cache cargo ...` as the opt-out.
 - **Real cache controls**: `soldr status`, `soldr cache`, and `soldr clean` report and manage the soldr-managed zccache state, while `soldr purge` removes all Soldr-managed cache artifacts for bug clearing and benchmarking.
-- **One cache boundary**: soldr keeps its own tools, zccache session state, and managed zccache artifacts under `~/.soldr/` by default. Use `SOLDR_CACHE_DIR` to move that root.
+- **One cache boundary**: official soldr keeps its tools and cache state under `~/.soldr/`; development builds use `~/.soldr-dev/`. Use `SOLDR_CACHE_DIR` to select an explicit root.
+- **Bounded while idle**: the long-lived daemon owns only its selected root,
+  checks pressure every five minutes, expires old state daily, and installs no
+  OS scheduler. Embedded zccache defaults to 5% of the filesystem clamped to
+  40–200 GiB, becomes aggressive for entries older than four days near full,
+  and expires artifacts after 30 days. Production, development (`.soldr-dev`),
+  custom, and standalone `.zccache` roots never sweep one another.
 - **Disposable-worktree friendly on Windows**: for build orchestration, soldr can relocate itself under `~/.soldr/runtime/soldr-self/` so `RUSTC_WRAPPER` does not keep using a worktree-local `soldr.exe`; stale runtime copies are cleaned up periodically.
 - **Pre-built first**: Download a pre-built binary before compiling from source. Fall back gracefully.
 - **Cargo-compatible**: soldr preserves normal cargo arguments instead of forcing a separate workflow.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zackees/soldr",
-  "version": "0.8.19",
+  "version": "0.8.21",
   "description": "Instant Rust tools and builds from one command.",
   "license": "BSD-3-Clause",
   "homepage": "https://github.com/zackees/soldr",