# v0.6.0-rc.4 Release Notes

## Version

`v0.6.0-rc.4`

## Dist Tag

Published dist-tag: `next`.

`0.6.0-rc.4` is published on npm `next`. The accepted External registry-smoke
archive is:

`/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/rc060-rc4-registry-smoke-20260705T110131Z`

Registry smoke used npm registry only by installing `persona-harness@next`; no
local tarball evidence was used. Registry state:

- `persona-harness@latest=0.5.0`;
- `persona-harness@next=0.6.0-rc.4`;
- `persona-harness@alpha=0.3.9-alpha.8`.

`persona-harness@next` and explicit `persona-harness@0.6.0-rc.4` resolve to
version `0.6.0-rc.4`, gitHead
`cf6835697f47da5a2a8372d00fc47e263ee781f8`, shasum
`76565f6e7d244595fa338bb646ea7888d8d5255a`, and integrity
`sha512-8oBVX1vmudoNZCJEVXNdx/lJnPITKD0cW2OGk6Bv963oibNwyo+itxYquRNr8JlDQR7RKDmcQ5XTCVlIP9weaw==`.
`persona-harness@latest` remains `0.5.0`, gitHead
`c0f1085a5182cdd17411bd043173aabc9a76b30e`, shasum
`3a7c43e4807e7cc8bd1b6c697746d6334ee56b09`; `latest` did not move.
Local and remote `v0.6.0-rc.4` tags point to
`cf6835697f47da5a2a8372d00fc47e263ee781f8`. The GitHub release exists and is
prerelease/not draft.

## Stable Deferral

Stable `0.6.0` is not being prepared in this release. HARDEN-2 remains blocked
because the prerequisite stable gate is not met: `0.6.0` stable is not
published and external tester recruitment for stable has not started.

H1-6a repeated-output compression failed the real rail-entry precheck:

- control/current rail entry: `3/5`;
- Summary-header candidate rail entry: `1/5`;
- delta: `-40pp`;
- non-inferiority: not met.

Compression remains NO-GO and unimplemented. `0.6.0-rc.4` is a prerelease
`next` package, not a stable release or default movement.

## Summary

`0.6.0-rc.4` prepares the accepted HARDEN-1 hardening after the published rc3
line while keeping the product center gate-first: deterministic finish/closure
gates, PH-generated evidence, read-only status/report surfaces, and
default-off continuation previews.

This prep does not claim product efficacy, token/provider-token saving,
navigation benefit, app quality, full-TDD/test sufficiency, broad reliability,
closure guarantee, autonomous completion, generated-app certification,
deterministic enforcement, production-ready delegation, reliable automatic
subagent orchestration, automatic completion/downgrade/removal, CodeGraph/LSP
default/effectiveness, or broad product behavior.

## Included Since rc3

- H1-0 preflight PARTIAL: the rc3 final docs record closed and Stage 18
  tokens-per-verified-completion telemetry was recorded, but the real n>=5
  rail-entry regression gate initially remained unresolved and later failed for
  H1-6a compression.
- H1-1 blocker-step contract: workflow continuation loops stop on unmapped
  blockers before consuming retry/iteration budget, and failed-finish human
  output points to Persona Harness configuration/maintainer escalation instead
  of direct finish/check rerun loops.
- H1-3 deterministic blocker order and chain-depth contract, plus H1-2
  mechanical finish regression coverage for a tiny finish-reachable
  Java/Spring-shaped fixture.
- H1-4 block-level toolchain fail-closed behavior and human mapped toolchain
  follow-up. Built-in `controller.persistence-import` remains default `warn`;
  explicit block-level ast-grep/toolchain-dependent conventions add a walkable
  `convention-toolchain-missing` closure blocker when the toolchain is missing
  or fails.
- H1-5 atomic writes and fail-safe reads split by file family. This is not a
  repo-wide all-writes atomicity claim.
- H1-6a real precheck failed: repeated-output compression remains NO-GO and
  unimplemented.
- H1-6b structured finish summary derivation: failed
  `workflow finish implement` human summaries are derived from structured
  closure blocker/required-fix objects instead of reparsing rendered
  `Closure blocker:` text. Stage 20 summary shape, H1-1 escalation wording,
  and H1-4 mapped toolchain guidance are preserved.

## Registry Evidence Notes

The final rc4 registry smoke observed required package entries including these
release docs, `dist/io/atomic-file.*`, `dist/cli/workflow-required-fix.*`,
`dist/cli/workflow-output.js`, closure, loop, ralph-loop, and Role Checklist
Relay surfaces. Registry install/version/help passed. Failed finish plus
repeated finish, closure JSON, H1-4 toolchain path, H1-1 unmapped path,
representative H1-5 atomic/corrupt-state behavior, and retained rc3
workflow-loop/ralph-loop/relay surfaces were smoke-tested.

H1-6b finish `Summary:` appeared before `Required fixes:`, detailed blockers
remained, and closure JSON parsed. No H1-6a compression wording appeared.
H1-4 `convention-toolchain-missing` used mapped install/configure/lower-level
guidance plus rerun `npx ph workflow check`, and JSON mapped to
`install-convention-toolchain`. H1-1 unmapped custom blocker retained
escalation wording, JSON had `unmapped-blocker` with no direct command,
`workflow loop` dry-run stopped at zero iterations, and ralph-loop reported the
unmapped next step.

Caveats: initial H1-4/H1-1 fixtures had prerequisite blockers ahead, so
isolated populated reruns were used to put target blockers first. H1-5 coverage
is representative, not a full repeat of every H1-5 family.

## 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:

- `0.6.0-rc.4` published to `next`;
- stable remains `latest=0.5.0` and stable `0.6.0` is deferred;
- H1-6a compression remains NO-GO and unimplemented;
- H1-6b structured finish summary derivation is accepted;
- no stable/latest movement.