Use current guidance first¶
For new work, get started with published Harness 1.6.0. This archive keeps earlier guides, candidate instructions and observation records available under their original versions. An archived result does not qualify a newer artifact or a different platform.
Published 1.5.1¶
- Harness 1.5.1 guide: the preserved installation procedure and original limits.
- 1.5.1 release record: the original source, distributions and qualification.
Published 1.5.0¶
- Harness 1.5.0 guide: historical installation, capabilities and limits.
- 1.5.0 verification record: original environment, command and form observations.
- Released 1.5.0 documentation: release notes, CLI procedures and saved-memory guidance.
- 1.5.0 candidate tutorials: candidate observations, distinct from published-wheel checks.
Screenshots in the goals guide retain their Harness 1.5.0 capture labels. Their saved example wording and state records are unchanged.
1.5.1 preparation¶
- Archived preparation guide: the original guide, before the final release source and artifact were selected.
- Preparation record: the metadata-only candidate wheel, source pins and limitations at that time.
- Preparation walkthroughs: retained navigation, planning, research and continuity observations with their artifact boundaries.
- Complete preparation Help source: the unchanged source snapshot for every topic before this publication update.
Statements that 1.5.1 was unpublished describe that preparation period. For the actual released files and checks, read the 1.5.1 release record.
Published 1.3.0 and earlier candidate work¶
- 1.3.0 tutorials: the original four walkthroughs and their verification boundaries.
- 1.3.0 release notes: the release's stated behavior and limits.
- Earlier next-release candidate tutorials: historical candidate evidence, not current installation instructions.
Read the evidence in context¶
Each link identifies a version or preparation state. Published software checks, synthetic maintainer walkthroughs, illustrative outputs and independent user acceptance are different evidence. Keep Windows limitations and provider-call boundaries with the record that states them. Nothing in this archive grants execution, paid calls or approval of a saved request.