# HarnessLink 17.18.0 release notes

5 changes, released Nov 13, 2026.

### Added

- `hnl prune`: native files built for another operating system or CPU, in the packages HarnessLink installs, listed by package with sizes and removed on confirmation (`--dry-run`, `--yes`, `--root <dir>` to list another directory without touching it). Detection is structural — prebuildify/napi/native layouts, platform packages and npm `os`/`cpu`/`libc`, and Mach-O/ELF/PE headers — so a universal binary carrying this machine's slice, WebAssembly and shell shims named `.exe` are kept, and a package that ships no build for this machine is reported instead of emptied. Reinstalling a package restores its files.
- The same pass runs automatically after every harness install and update, from the installers, and once ~90 s after the service starts (bounded, in the background): `cleanup.platformPrune`, on by default, `hnl prune off` to stop it. On one Mac it reclaimed 265 MB across five packages.
- `hnl doctor` area "Platform purity": foreign payloads, an installed `hnl` built for another machine, and update leftovers beside it (`hnl.old-<id>.exe` parked by install.ps1, abandoned `hnl.next`) — removed by `hnl doctor --fix`, with the `hnl.previous` rollback copy always kept.
- **A release binary can no longer carry anything that confers server authority (ADR-99).** Every compiled binary is scanned before it is hashed into the manifest, and the build fails on private key material, `.env` content, Worker (`cloud/`) source, our D1/R2/Vectorize names or account ids, test code, `.git` metadata or a build-machine path — and on any bundle that so much as reads one of those files. Check any binary yourself: `bun scripts/release-payload-scan.ts <file>`.

### Changed

- `docs/CLOUD_SETUP.md` now says measurably what a release binary gives a reader. The client's JavaScript and every embedded prompt can be recovered from it, so what protects the product is the private repository, the proprietary licence, server-side enforcement, signed releases and modified-client flagging — not secrecy of the client.

Update HarnessLink and every installed harness to its current release:

hnl update

New machine? Install with:

curl -fsSL https://harnesslink.sh/install.sh | bash

[Newer: 17.19.0](https://harnesslink.sh/releases/17.19.0) · [Older: 17.17.4](https://harnesslink.sh/releases#v17.17.4) · [All releases](https://harnesslink.sh/releases) · [Atom feed](https://harnesslink.sh/releases.atom)
