# v0.3.1-alpha.0 Release Notes

## Version

`v0.3.1-alpha.0`

## 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.1-alpha.0`

## Summary

This alpha focuses on AI-facing workflow diagnostics. It makes short OpenCode TUI prompts such as "README 보고 구현해줘" more likely to route through plan status, workflow checks, bounded command execution, implementation reports, review reports, and backend-shape observation.

## What Changed

- Added report-only local diagnostics: `ph workflow check`, `ph doctor`, `ph smoke`, `ph feedback`, `ph evidence summary`, and `ph review backend-shape`.
- Added AI-facing workflow rails: `ph workflow start implement` and `ph workflow finish implement`.
- Kept strict lower-level workflow gates: `ph workflow guard implement` and `ph workflow guard final`.
- Added npm dist-tag visibility to `ph doctor`.
- Added workflow command-discipline WARNs for raw shell usage or missing `npx ph bearshell` evidence in filled workflow reports.
- Added codegraph-first guidance for code structure analysis and change-impact review in AI-facing injection/workflow prompts.
- Tightened short implementation guidance so agents should run `npx ph workflow start implement`, `npx ph bearshell`, `npx ph plan --report-filled ...`, and `npx ph workflow finish implement`.
- Narrowed workflow-noise classification so raw final verification remains blocking, while an initial raw smoke that is rerun through `npx ph bearshell` can recover to `ph workflow finish implement` PASS.
- Clarified README positioning: humans install and initialize; AI agents use the `ph` command surface during planning, implementation, verification, and reporting.

## Install

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

## Supported Scope

- Java/Spring backend MVP.
- Gradle-first backend workflow.
- OpenCode plugin injection for Java/Spring backend Clean Code guidance.
- AI-facing local workflow command surface.
- Report-only diagnostics and backend-shape observation.

## Not Supported

- Generated app product-quality certification.
- Rule compliance enforcement through AST/linter/build gates.
- Frontend, infra, or desktop productization.
- Full Test -> Feat -> Refactor workflow.
- `ph bearshell` sandboxing.

## Verification

Commands to run before release:

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

- `npm test`: 36 files, 218 tests passed.
- `npm run typecheck`: passed.
- `npm run build`: passed.
- `npm run report:rules`: PASS, 0 diagnostics.
- `npm run check:scope:strict`: PASS, 0 diagnostics.
- `npm run check:injection-value`: PASS, current evidence window 3/3, decision `continue-java-mvp`.
- `npm pack --dry-run --json`: `persona-harness@0.3.1-alpha.0`, 216 files, 215.5 kB package size.
- `npm publish --dry-run --tag alpha`: passed for `persona-harness@0.3.1-alpha.0`.
- `npm publish --tag alpha`: attempted, blocked by npm `EOTP` browser/OTP authentication requirement before registry publish.
- Clean short-TUI smoke: `README 보고 구현해줘` reached `ph workflow finish implement` PASS after final verification was rerun through `npx ph bearshell`; no direct `.persona/rules` read tool lines were observed.

## Package Contents Notes

- Includes `dist`, `README.md`, language README files, `LICENSE`, `CHANGELOG.md`, `.persona/harness.jsonc`, `.persona/rules`, current release docs, and the Java programming shared-skill reference subset.
- Excludes generated evidence, experiments, `.persona-test-fixtures`, inactive OMO reference skills, and Java no-excuse fixture files from package contents.

## Known Gaps

- Command-discipline warnings are visible but not blocking.
- OpenCode behavior still varies by model and runtime context.
- This release does not make `ph` a standalone agent runner; it is a workflow surface for OpenCode/Codex-style agents.
- codegraph-first guidance is AI-facing guidance only; Persona Harness does not install or require a codegraph MCP server.
- Actual npm publish still requires completing npm browser/OTP authentication; registry dist-tags remain on `0.3.0-alpha.3` until that succeeds.

## Release Automation

- `[ ]` tag matches `package.json` version
- `[ ]` GitHub Actions verify job passed
- `[ ]` npm publish job passed
- `[ ]` GitHub release notes were created

## Next

- Complete npm browser/OTP authentication and rerun `npm publish --tag alpha`.
- Validate this package with an external tester after publish.