# v0.6.0 Release Notes

## Version

`v0.6.0`

## Dist Tag

Stable publish dist-tag: `latest`.

QA accepted the final External registry smoke for `persona-harness@latest=0.6.0`.
The accepted archive is:

`/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/stable-060-registry-smoke-20260705T041031Z`

Registry facts after final smoke:

- `persona-harness@latest=0.6.0`;
- explicit `persona-harness@0.6.0` resolves to the same package;
- gitHead `13b1f1b79884e2214c0b41a735b87cdd6d65ee00`;
- shasum `ffd77996263cffb858bd977edb73b03cf2820c75`;
- integrity
  `sha512-0dY/LqXYuSD7/G/GsALoE0RBKClikt1MPVR6GvbXRieBiSDh5CEt0JNP0RxJ8Ur3howsURYeaFQX8aRhSzKP0A==`;
- dist-tags are `latest=0.6.0`, `next=0.6.0-rc.4`, and
  `alpha=0.3.9-alpha.8`;
- local and remote `v0.6.0` point to
  `13b1f1b79884e2214c0b41a735b87cdd6d65ee00`;
- GitHub release `v0.6.0` is stable: `isDraft=false`,
  `isPrerelease=false`.

## Stable Basis

`0.6.0` prepares the accepted HARDEN-1 line for stable after the stable
decision cycle S-0 through S-3:

- S-0 corrected the stable blocker: H1-6a compression NO-GO itself did not
  block stable; the shipped failed-finish human `Summary:` header's inferior
  real-session rail-entry evidence did.
- S-1 established `gate-fixture.2` with control rail entry `10/10`.
- S-2 regated the shipped `Summary:` header and accepted FAIL decision input:
  control `10/10`, Summary-header candidate `9/10`, delta `-10pp`,
  non-inferiority false, decision `FAIL_RECOMMEND_HEADER_OFF_FOR_S3`.
- S-3 removed the failed-finish human `Summary:` header and QA/External
  accepted local-current package smoke at commit
  `c7affd7674fc949b373c414974b05010b8dd1f21`.

The prior Summary-header stable blocker is therefore resolved by removal.
Failed `ph workflow finish implement` human output renders `Required fixes:`
and detailed blockers directly. `workflow closure next --json` remains the
machine-readable next-step surface.

## Included Since rc4

- Stable-cycle S-1/S-2/S-3 records and S-3 implementation removing the failed
  finish human `Summary:` header.
- No H1-6a compression implementation. Compression remains NO-GO and
  unimplemented after the failed real precheck.
- H1-6b structured required-fix data remains implementation support, but no
  failed-finish `Summary:` header is rendered in the stable output.

## Final Registry Smoke

The stable registry smoke installed `persona-harness@latest` from npm only; no
local tarball evidence was used. It observed package entries for LICENSE,
localized READMEs, CHANGELOG, stable docs, `dist/io/atomic-file.*`,
`dist/cli/workflow-required-fix.*`, `dist/cli/workflow-output.js`, closure,
workflow-loop/state, ralph-loop/state/tool-output, workflow relay/UI, and
bootstrap multi-agent surfaces.

Basic install, help, version, workflow help, and bootstrap help passed. The S-3
failed-finish human output had no `Summary:` header, kept `Required fixes:`
and detailed blocker diagnostics, and did not show `details unchanged since
last check` or H1-6a compression wording. Generic closure JSON parsed with
`action=next`, `nextStep.id=verify-app`, and first blocker
`verification-unknown`.

The smoke also checked the H1-4 `convention-toolchain-missing` path, mapping to
`install-convention-toolchain` with `commandAfterContent="npx ph workflow
check"`; the H1-1 unmapped path with escalation/no-step-mapping wording,
`unmapped-blocker`, and loop/ralph-loop stop surfaces; representative H1-5
`writeFileAtomic` success/failure cleanup and corrupt ralph-loop state
no-crash behavior; and retained default-off/schema-stable surfaces including
`workflow-ralph-loop.4`, `workflow-loop.1`, and Role Checklist Relay
checklist-first/host-dependent guidance.

The H1-1/H1-4 blocker fixtures reused prior accepted disposable fixture shapes
to isolate target blockers. H1-5 coverage is representative helper and
corrupt-state spot smoke, not repo-wide all-writes atomicity evidence. No real
OpenCode/model/eval run was performed in the stable registry smoke.

## HARDEN-1 Stable Surface

The stable package carries the accepted HARDEN-1 hardening line:

- H1-1 unmapped blocker de-loop and human escalation.
- H1-2 mechanical finish regression coverage.
- H1-3 deterministic blocker order and chain-depth contract.
- H1-4 explicit block-level toolchain fail-closed behavior and mapped human
  guidance.
- H1-5 atomic writes and fail-safe reads by migrated file family only. This is
  not a repo-wide all-writes atomicity claim.
- H1-6a compression NO-GO and unimplemented.
- H1-6b structured required-fix data remains internal support; the human
  Summary header is off.

Stage 18 fixture-scoped completion-integrity evidence remains narrow: OFF
finish PASS `0/10`, internal tool-output trigger finish PASS `10/10`, external
`ph workflow loop` finish PASS `7/10` with cap-risk caveat. This does not prove
default change, product efficacy, broad reliability, token saving, or app
quality.

## External Tester Kickoff

This final stable record is the handoff point for external tester recruitment.
Recruitment is planned/ready to start; no concrete started-recruitment evidence
is recorded here. `PROJECT-PLAN.md` section 4 calls for 3-5 external testers.
Observation should focus on onboarding drop-off, time to first finish,
doctor/feedback usage, whether users value or resent gate blocks,
team-convention demand signals, real fake-shim/gaming incidents, and
tester-driven UX complaints. HARDEN-2 may start only after this stable final
record and tester kickoff status are recorded, and it remains subordinate to
incoming tester feedback.

## Claim Audit

Do not claim:

- product efficacy, navigation benefit, token saving, or provider-token saving;
- app/product quality guarantee;
- full TDD framework, coverage, mutation testing, or test sufficiency;
- broad reliability, closure guarantee, autonomous completion, or generated-app
  certification;
- deterministic role enforcement or production-ready delegation;
- reliable automatic OpenCode subagent orchestration;
- automatic completion, downgrade, removal, or config mutation;
- CodeGraph/LSP default behavior or effectiveness.

Allowed wording:

- stable `0.6.0` is published to npm `latest`;
- current dist-tags are `latest=0.6.0`, `next=0.6.0-rc.4`, and
  `alpha=0.3.9-alpha.8`;
- S-3 removed the failed-finish human `Summary:` header after S-2 regate;
- H1-6a compression remains NO-GO and unimplemented;
- final registry smoke is package-runtime evidence only.