Token Harness 0.1.30 — Attributed app evidence and paired comparisons

Token Harness 0.1.30 — Attributed app evidence and paired comparisons

0.1.30 makes Results show each coding app's attributed optimizer output, observed routing
callbacks and current allowance readings. It repairs paired comparisons so five-hour and weekly
quota evidence remain visible together with the actual quality gates.

Installation

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

The version must be 0.1.30. These commands also work in PowerShell. Restart an already running
dashboard to load the updated Results interface.

What changed

• Coding-app rows use separately aggregated events with an explicit app identity. Shared and
  unattributed history stays under its optimizer; configuration does not assign it to an app.
• Runtime routing callbacks and current quota balances appear as separate evidence, with source,
  observation and reset timestamps. Callback activity and remaining quota are not savings.
• Paired benchmarks retain every comparable quota window, including simultaneous five-hour savings
  and weekly growth. The existing primary comparison and verdict remain compatible.
• Actual baseline and optimized quality gates remain visible even when efficiency usage is missing.
  A positive allowance claim cannot borrow a different pair's passing quality gate; attributed
  routing without comparable usage stays unmeasured for savings.
• Results distinguish missing, unfinished and unreadable comparisons. Record a comparison opens
  a read-only guide to the existing benchmark-start/finish collectors, without creating a baseline,
  running a task or inventing a quality outcome.
• Output history remains all-project and period-filtered. Paired quality/quota evidence remains
  current-project; callbacks and current balances retain their own observation dates.

Verification scope

PR #371 and merged-main CI passed on Windows,
macOS and Linux. Local review validation passed 2,418 tests with nine expected skips, plus typecheck,
lint, formatting, build and bundle smoke. Regression coverage includes independent quota windows,
negative deltas, cached/reset-crossing rejection, quality-only and unknown-quality outcomes,
no-usage routing and shared/multi-app output attribution.

Release preparation also passed five version/packaging contract tests, formatting, lint, build,
bundle smoke, package staging, temporary tarball installation and exact version/tag validation.

Publication requires release-candidate cross-platform CI, exact-tag build, guided real-runtime smoke,
package installation checks, provenance/SBOM attestations, npm Trusted Publishing and npm-latest
verification.

Existing published 0.1.28 Linux callback/lifecycle observations
retain their exact build scope. Windows published-artifact checks, actual native child-model
selection and paired quality-gated savings measurements remain separate work. This release improves
evidence reporting and makes no new token, quota or API savings claim.

Full changelog: v0.1.29…v0.1.30

Publication completed through the exact-tag release workflow, including real-runtime smoke, package installation, provenance/SBOM attestations and npm-latest verification.