# v0.3.2-alpha.2 Release Notes

## Version

`v0.3.2-alpha.2`

## Dist Tag

`alpha`

During the alpha pilot, `latest` is also synchronized to the current alpha build to avoid stale default installs. This is not a stable support claim.

## npm Package

`persona-harness@0.3.2-alpha.2`

## Summary

This hotfix makes the workflow implementation rail surface generated Java files after creation. A clean TUI or OpenCode run should no longer leave only `README.md` evidence when the agent follows `npx ph workflow implement`; it should run Java role discovery and then read representative generated Java files.

## What Changed

- `ph workflow implement` now tells agents to run:

```bash
npx ph bearshell --shell 'find src/main/java src/test/java -name "*.java" 2>/dev/null | sort'
```

- The Java role discovery hook now recognizes shell and bearshell output, not only direct glob/find/list tool names.
- The implementation report template now includes:
  - Java role discovery method
  - Java role files discovered
  - Java role files read
- Historical v0.3.2 behavior temporarily let `ph init` create a ready default backend profile; current alpha behavior supersedes this, so `ph init` is minimal and `ph bootstrap backend` prepares the backend-ready profile/plan/report state.
- `ph plan --auto-accept` is available for alpha smoke tests that should not stop on a manual accept step.
- `ph plan` and `ph workflow implement` now stop when the profile is missing, draft, malformed, or incomplete.

## Why

Fresh clean-run evidence showed that some generated projects had real Java files but only `README.md` evidence. That meant the implementation workflow could create files without leaving observable role-specific evidence for Controller, Service, Repository, DTO, and Domain files.

The fix keeps the current report-only model: it does not certify generated code quality and does not enforce rule compliance. It makes the expected workflow evidence visible when the agent follows the implementation rail.

## Verification

Pre-publish commands:

```bash
npm test -- tests/phase0-java-role-discovery.test.ts tests/persona-harness-workflow-check.test.ts
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
npm publish --dry-run --tag alpha
```

Publish result:

- `npm publish --tag alpha`: passed for `persona-harness@0.3.2-alpha.2`.
- `npm view persona-harness@alpha version`: `0.3.2-alpha.2`.
- `npm dist-tag add persona-harness@0.3.2-alpha.2 latest`: blocked by npm OTP requirement, so `latest` remains `0.3.2-alpha.1` until OTP authorization is provided.

Expected clean-run evidence:

- `role-discovery` entries for generated Java files.
- `model-input` entry for `<java-role-read-follow-up>`.
- role counts for Controller, Service, Repository, request DTO, response DTO, Domain, and Java common files when those files exist.

## Supported Scope

- Java/Spring backend MVP.
- AI-facing implementation workflow rail.
- Report-only workflow diagnostics and evidence gate.
- Local/OpenCode clean project verification.

## Not Supported

- Generated app product-quality certification.
- Automatic proof that every generated Java file was semantically understood.
- AST/linter/build rule enforcement.
- Frontend, infra, or desktop productization.
- Full Test -> Feat -> Refactor workflow.

## Next

- Reinstall `persona-harness@alpha` in a clean project and rerun a short request such as `README.md 보고 구현해줘`.
- Confirm evidence includes generated Java role discovery, not only README evidence.