# v0.3.9-alpha.6 Release Notes

## Version

`v0.3.9-alpha.6`

## Dist Tag

`alpha`

During the alpha pilot, `alpha` is the tester-facing dist-tag. `latest` may lag
behind `alpha`, so verify both before treating default install as current.

## Summary

This prerelease packages the post-build closure checklist added after the
`persona-harness@0.3.9-alpha.5` Windows SSH real-use trial exposed closure
friction.

It includes:

- `d9dcd0a fix(cli): guide post-build workflow closure`;
- `fde990c docs: record post-build closure guidance`.

Persona Harness remains an AI coding workflow rail + evidence + continuation
harness. This release is not eval proof, PH superiority proof, generated app
product-quality certification, AST/linter enforcement, or an OpenCode/model
quality claim.

## What Changed

### Post-build closure checklist

- `workflow continue` and `workflow check` now show a compact post-build closure
  checklist when app generation appears to have happened but reports are still
  templates and a ticket remains pending.
- The checklist tells agents to:
  - avoid generating a new app;
  - fill the implementation report and mark it report-filled;
  - fill the review report and mark it report-filled;
  - review/archive the current requirement candidate;
  - run `workflow finish implement`.

## Boundaries

- This is a product workflow surface release.
- The finish gate is not weakened.
- No enforcement is added.
- No eval-core, fixture, policy, or scorer behavior changes are included.
- If reports/evidence are still templates, the CLI does not claim build, test,
  or runtime success as confirmed.
- Model follow-through risk remains.
- Published registry smoke has confirmed the alpha6 no-token product workflow
  surface; see the smoke section below.

## Verification

Release-prep verification for this worktree:

```bash
npm test
npm run typecheck
npm run build
npm run check:docs
npm run smoke:product-mvp
npm pack --dry-run
git diff --check
```

Observed result on 2026-06-28:

- `npm test`: passed, 69 files / 454 tests.
- `npm run typecheck`: passed.
- `npm run build`: passed.
- `npm run check:docs`: passed.
- `npm run smoke:product-mvp`: passed.
- `npm pack --dry-run`: passed for `persona-harness@0.3.9-alpha.6`.
  - filename: `persona-harness-0.3.9-alpha.6.tgz`;
  - package size: `382.0 kB`;
  - unpacked size: `1.5 MB`;
  - shasum: `217087f5aa5331b1fb45543f5be625850d7d3924`;
  - total files: `373`.
- `git diff --check`: passed.

## Publish Notes

- Publish with `npm publish --tag alpha` only after all verification commands
  pass.
- Do not intentionally move `latest` during this manual release unless
  separately approved.
- If npm requires OTP/2FA, stop after the first failure and hand off the exact
  command for the user to run.

## Published Registry Facts

`persona-harness@0.3.9-alpha.6` exists on the npm registry.

Registry facts observed after user-completed OTP publish:

- version: `0.3.9-alpha.6`;
- gitHead: `7b090bd26068a24d2fd7da5b9b7da680847c3a04`;
- dist.shasum: `e5c8c8efa17eac8e51f49e8f65e4daa579d72468`;
- dist-tags: `alpha=0.3.9-alpha.6`, `latest=0.3.9-alpha.3`.

`latest` was not moved.

## Published Registry Smoke

External Smoke confirmed the alpha6 registry package on a Windows D-drive clean
workspace.

Observed facts:

- install: `npm install -D persona-harness@alpha`;
- installed package: `persona-harness@0.3.9-alpha.6`;
- registry facts: `alpha=0.3.9-alpha.6`, `latest=0.3.9-alpha.3`;
- gitHead: `7b090bd26068a24d2fd7da5b9b7da680847c3a04`;
- dist.shasum: `e5c8c8efa17eac8e51f49e8f65e4daa579d72468`;
- remote workspace: `D:\persona-harness-smoke-alpha6-registry-20260628-220759`;
- local archive:
  `/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/alpha6-registry-windows-d-smoke-20260628-220724`.

Smoke result:

- no-token idea-first path passed: init/default backend, doctor, bootstrap,
  draft/approve/split/next/continue/check;
- Korean `TODO 웹 서비스 만들래` was preserved in the `workflow next` title and
  `workflow continue` task-card context;
- `workflow continue` showed task-card context, next command/action, archive
  candidate, no-completion guidance, and the post-build closure checklist;
- `workflow check` also showed the closure path in pending/template state;
- the remaining WARN was expected because reports were templates, the current
  requirement was pending, and evidence was missing, so completion stayed
  blocked.

This closes the alpha6 product workflow surface cycle. It is still product
surface smoke only: no eval, model, OpenCode, A/B, PH superiority, or generated
app quality certification is claimed. The full implementation real-use trial was
not rerun for alpha6.

## Single Implementation-To-Finish Trial

External Smoke also ran a single implementation-to-finish proxy trial against
the alpha6 registry package.

Observed facts:

- install/init/doctor/bootstrap/idea-first/continue passed;
- OpenCode ran once with bounded `gpt-5.4-mini-fast` and read
  README/profile/plan/task context;
- the model generated a Java/Spring/Gradle todo API with a Gradle wrapper;
- `gradlew.bat test` and `gradlew.bat build` reached `BUILD SUCCESSFUL` during
  the OpenCode run;
- runtime/bootRun was attempted, but the model did not return to workflow
  closure;
- implementation and review reports remained `Status: template`;
- `req-1` remained pending;
- `workflow finish implement` correctly blocked because implementation report
  filled status, review report filled status, and pending `req-1` fixes were
  required;
- backend-shape was mostly PASS, with a verification-report WARN because reports
  lacked test/build/bootRun output.

Artifacts:

- remote workspace:
  `D:\persona-harness-smoke-alpha6-single-finish-20260628-235621`;
- local archive:
  `/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/alpha6-single-finish-trial-20260628-235621`.

Classification:

- this is a closure structure/follow-through failure;
- it is not an install, encoding, stack steering, or finish-gate bug;
- the finish gate was correct and should not be weakened.

Decision:

- A-lite closure wording/checklist patches are not sufficient after this trial;
- move to B: the workflow rail needs state-machine design;
- no more closure wording/checklist patches should be the primary response;
- next CLI work should be a design draft, not implementation.

Boundary:

- this is product usability smoke, not eval, A/B, proof, generated app production
  quality certification, or PH superiority evidence.

## Post-Alpha6 Structural Follow-Up

After alpha6, `5df7dc1 feat(cli): add workflow closure planner` implemented the
first B slice as a read-only workflow closure planner:

- `workflow closure status --json` exposes closure state and blockers;
- `workflow closure next --json` exposes the first actionable blocker and next
  command sequence;
- `workflow finish implement` remains the final authority;
- the planner does not add `closure run`, auto-fill reports, auto-archive
  tickets, finish workflows, weaken gates, or claim retroactive success for the
  alpha6 single finish trial.

The design contract is
`docs/current/workflow-closure-state-machine-design.md`. This is next-release
candidate context only; it is not eval proof, PH superiority proof, generated
app quality certification, or a published alpha6 behavior change.