Skip to content

Attune Harness 1.5.0

Choose a tag to compare

@silversurfer562 silversurfer562 released this 19 Oct 15:39
· 21 commits to main since this release
v1.5.0
7caa86a

Attune Harness 1.5.0

This release ships verified merged Windows components while deferring full Windows parity. Strict acceptance criteria remain unchanged.

  • Preview and run accepted tests in a captured copy, retaining output, checkpoints and check evidence.
  • Read configured raw, personal and curated file-memory roots within the documented path and identity limits.
  • Retain the merged saved-memory and task-intent checkpoint, with its documented pending storage acceptance.
  • Offer the experimental native-memory transport with offline evidence; live-provider acceptance remains open.

Read the versioned release notes and README for installation, compatibility and evidence boundaries. Python 3.10 or later is required. Base installation: uv tool install 'attune-harness==1.5.0'.

Verification

Source: 7caa86ab6d476e9599b08ff75a81bc816e60c382. Exact-main CI settled with 30 successful checks and one intentional skip, including the hosted Windows Server 2022/2025 and Python 3.10/3.12 software checks. The build-only rehearsal passed. These results do not establish full Windows parity.

Production run 39268577008 passed after environment approval. Both files downloaded from PyPI match that run's SHA256SUMS exactly. A fresh noneditable PyPI base install on macOS arm64/Python 3.12.2 passed pip check and 32 installed CLI cases, including the complete R2 journey with zero model calls. This does not qualify upgrades, every saved-work migration, GUI behavior or additional Windows configurations.

Published distribution SHA-256
attune_harness-1.5.0-py3-none-any.whl 532bedcdf9d8ded86919c4a09c49714386f2228f566acfc6633c354ee6153046
attune_harness-1.5.0.tar.gz 1d524bd6ac7a2cd1b770c45745c666c8113fe20902e91b78634b0d013e406669

Deferred acceptance

Full Windows parity, strict arbitrary-descendant stop and recovery, full saved-store acceptance and the historical eight-writer busy-failure cause, live native-memory acceptance, Windows 11 standard-user desktop journeys and Windows shell qualification remain open. See the versioned readiness record. Package publication does not deploy the separate Help or deck materials.