Skip to content

v0.6.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Jul 04:08
v0.6.0
13b1f1b

v0.6.0 Release Notes

Version

v0.6.0

Dist Tag

Planned stable publish dist-tag: latest.

This is a stable release-prep record only until QA publish GO and registry
verification complete. At prep time:

  • persona-harness@latest=0.5.0;
  • persona-harness@next=0.6.0-rc.4;
  • persona-harness@alpha=0.3.9-alpha.8;
  • persona-harness@0.6.0 is expected to be unpublished before publish;
  • no v0.6.0 tag should exist before the publish/tag sequence.

latest must not move until QA approves the exact prep commit for publish and
the Trusted Publisher path publishes 0.6.0 to latest.

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 prep output.

HARDEN-1 Stable Surface

The stable prep 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

PROJECT-PLAN.md section 4 says stable is the trigger for 3-5 external
testers. After stable publish, tester 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 remains post-stable and
may run during the tester observation period, but must yield to 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 prepared for QA review and future publish to latest;
  • pre-publish registry state remains latest=0.5.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;
  • no publish, tag, or dist-tag movement happens during prep.

Automation Metadata

  • Source release notes: docs/current/release/v0.6.0-release-notes.md
  • Package version: 0.6.0
  • Tag: v0.6.0
  • Intended npm dist-tag: latest
  • Acceptance results index: docs/current/acceptance-results/README.md

Claim Boundaries

This GitHub release body is generated from the repository release notes. It does
not add token-saving, provider-token-saving, product-efficacy,
navigation-benefit, app-quality, full-TDD/test-sufficiency, CodeGraph/LSP
default/effectiveness, broad reliability, closure guarantee, Codex support,
code-nav replacement, or automatic downgrade/removal claims.

Assets 2
Loading