# Persona Harness v0.3.0-alpha.3 Release Notes

## Version

`v0.3.0-alpha.3`

## Dist Tag

`alpha`

## npm Package

`persona-harness@0.3.0-alpha.3`

## Summary

This alpha tightens the Java/Spring backend planning workflow before implementation and improves continuation evidence when OpenCode stops mid-run.

It also records fresh positive package-flow and `bootJar` evidence, but it is still an alpha workflow/tooling release, not a generated app quality guarantee.

## What Changed

- Added `ph plan --implement` so short implementation prompts route through an accepted `.persona/workflow/plan.md`.
- Added `ph plan --next` and `ph plan --resume` for interrupted workflow continuation.
- Added Read Coverage fields to implementation reports so agents record read method/ranges instead of checkbox-only claims.
- Added `ph help`, `ph language`, and a `user-language` intake question for tester-facing setup.
- Tightened package-flow guidance toward `presentation/application/domain/infrastructure`.
- Tightened executable Spring Boot build guidance so `:bootJar SKIPPED` is not treated as a valid build pass.
- Documented fresh ON evidence where package-flow and `bootJar` behavior both passed.

## Install

Current alpha install:

```bash
npm install -D persona-harness@alpha
npx ph init
```

Pinned install:

```bash
npm install -D persona-harness@0.3.0-alpha.3
npx ph init
```

## Supported Scope

- Java/Spring backend Clean Code MVP.
- OpenCode plugin injection for Java/Spring backend targets.
- `ph init`, `ph intake`, `ph policy`, `ph plan`, `ph bearshell`.
- Local workflow artifacts under `.persona/workflow`.
- Metadata/evidence capture for injected rules and selected file roles.

## Not Supported

- Stable `1.0.0` support guarantees.
- Generated application product-quality certification.
- Rule compliance enforcement through AST/linter/build gates.
- Frontend, infra, or desktop app productization.
- Automated TDD workflow.

## Verification

Commands run for release metadata verification:

```bash
npm test
npm run typecheck
npm run build
npm run report:rules
npm run check:scope:strict
npm run check:injection-value
npm pack --dry-run --json
npm publish --dry-run --tag alpha
```

Result:

- Tests passed: 32 files, 190 tests.
- Rule diagnostics passed with 0 findings.
- Scope diagnostics passed in strict mode.
- Injection value decision remained `continue-java-mvp`.
- `npm pack --dry-run --json` passed for `persona-harness-0.3.0-alpha.3.tgz` with 191 files, 198.2 kB package size, and 735.1 kB unpacked size.
- `npm publish --dry-run --tag alpha` passed for `persona-harness@0.3.0-alpha.3`.
- `npm publish --tag alpha` published `persona-harness@0.3.0-alpha.3`.
- Registry verification passed: `persona-harness@alpha` resolves to `0.3.0-alpha.3`.
- Registry verification passed: `persona-harness@latest` resolves to `0.3.0-alpha.3`.

## Package Contents Notes

- Includes `dist`.
- Includes root README and language README files.
- Includes Apache-2.0 `LICENSE`.
- Includes `.persona/harness.jsonc` and `.persona/rules`.
- Includes release docs and Java shared-skill reference subset.
- Excludes generated evidence, experiments, `.persona-test-fixtures`, and `.omo`.

## Known Gaps

- OpenCode can still stop before code generation on large clean-project requests.
- `ph plan --resume` prints a continuation prompt; it does not automatically continue OpenCode.
- Evidence is model-dependent and small-sample.
- package-flow and `bootJar` guidance are report/prompt guidance, not enforcement gates.

## Release Automation

- `[x]` tag matches `package.json` version
- `[ ]` GitHub Actions verify job passed for this release path
- `[x]` npm publish completed manually
- `[x]` GitHub release notes were created

## Next

Collect external tester feedback from the published `alpha`/`latest` package path.