Token Harness 0.1.31 — Desktop application and guided benchmark recovery

Token Harness 0.1.31 — Desktop application and guided benchmark recovery

0.1.31 ships a native desktop application, retained configuration history and
reviewed benchmark controls. It also includes deterministic quality checks and
managed exploratory four-arm benchmarks added after 0.1.30.

Installation

Download the matching asset from the 0.1.31 release:

• Windows x64: install the setup EXE and open Token Harness.
• Linux x64: install the DEB or extract the TAR.GZ into a permanent directory and
  run token-harness-desktop.
• macOS Intel or Apple Silicon: open the matching DMG/ZIP and copy the application
  into Applications.

Each desktop package includes its own Node runtime. Choose File → Open project
to select your coding project. Keep the installed runtime in a stable location while
owned hooks reference it. Windows packages are unsigned; macOS packages use ad-hoc
signing without notarization. WSL remains a separate CLI environment.

For the CLI:

npm install --global token-harness@0.1.31
token-harness --version
token-harness

The version must be 0.1.31. Restart an already running application to load the
updated interface. Desktop updates use manual replacement of the published package.

What changed

• Native Windows x64, Linux x64 and macOS x64/arm64 applications share the guided UI
  and transaction engine. Releases attach all native packages and SHA-256 checksums.
• Results retains the latest 20 current-project operations across reopen. Reviewed
  recovery targets the latest eligible configuration transaction; package operations
  and arbitrary historical transactions remain outside this control.
• Start or finish a comparison records manual baseline/optimized captures and
  explicit quality outcomes, with retained progress. It executes no coding task or
  check and does not infer quality from token counts.
• Overview → Health and updates → Review benchmark recovery discovers the current
  project's active prepared-arm lease, previews restoration and restores saved
  configuration after a single-use approval. Drift, corrupt backups and invalid
  checkpoints preserve recovery data. Recovery retains measurements without finishing
  the capture or recording a quality result.
• Advanced CLI benchmarks support approved direct executable checks, immutable quality
  provenance, schema-1 reading, exploratory four-arm reports and reviewed temporary
  configuration preparation/restoration. Each measurement class and quota window
  remains separate; one four-arm set is not statistical evidence.

The Harness Remote test guide explains how
to use the same Machine/project, record a paired task and exercise prepared-arm
recovery. Factorial preparation, scheduling and handoff remain advanced workflows.

Verification scope

The feature PRs #378,
#380,
#381,
#382 and
#383 are merged. The latest
feature candidate passed native Windows, macOS and Linux CI and all four desktop
package/smoke targets. Local validation passed 2,525 tests with nine expected skips,
typecheck, source lint, formatting, build and bundle smoke.

Release-candidate CI,
merged-main CI and
exact-tag publication
passed. The tag workflow completed native builds, full tests, guided real-runtime
setup/update smoke, package installation checks, provenance/SBOM attestations,
npm Trusted Publishing and npm-latest verification.

The published npm tarball matches the GitHub asset byte-for-byte. Its isolated
installation reports 0.1.31, exposes the expected CLI and contains the same bundle
as the reviewed source build. The provenance signature, release workflow, tag and
source commit were verified. All seven desktop checksum entries match GitHub's
asset digests.

Tarball SHA-256: 4fd88149e58c50b6bc602186f3c31b5195b4ffd3524eaed002227ba11366dd80.
CLI bundle SHA-256: 658f80509bd88cce6826979eadadcdd1ebdf3f86837ac1eb61a1dbc8c5adb477.

Recovery verification is config-only. Unit fixtures, packaged smoke and desktop
builds do not prove native provider execution or savings. Windows published-artifact
verification (#255/#359), repeated isolated quality-gated measurements (#360), broader
desktop lifecycle/workflow coverage (#379), and broad promotion remain separate work.
Earlier runtime observations retain their original versions and scope; this release
makes no new token, subscription-quota or API savings claim.

Release source

Version preparation: PR #384. Immutable tag v0.1.31 points to merged main commit c9a90f0996a66addffa42f2ea4ab2aa5c3b62746.