# v0.3.0-alpha.3 Candidate

## Status

Current decision: `candidate-ready-for-final-package-checks`

`0.3.0-alpha.3` is a reasonable next alpha candidate now that the resume/next workflow gap has a minimal CLI surface and the later package-flow/`bootJar` fresh ON blocker has positive evidence.

## Why This Candidate Exists

`0.3.0-alpha.2` proved the package can be installed and that the plan-aware TUI path can route a short implementation request through `npx ph plan --implement`.

The latest TUI rerun also showed a hard gap:

- `ph plan --implement` was executed.
- the new Read Coverage evidence-field prompt was shown.
- OpenCode read README/profile/policies/rules.
- the implementation stopped before creating `src/`, `build.gradle`, or filled reports.

That means the next alpha should not claim improved end-to-end generation quality unless the workflow can resume incomplete runs.

## Candidate Scope

Include in `0.3.0-alpha.3` if implemented and verified:

- `implementation-report.md` Read Coverage evidence fields
- `ph help`
- `ph language`
- `user-language` intake question
- evidence review for the latest TUI rerun
- `ph plan --next`
- `ph plan --resume`
- package-flow guidance that steers generated Java packages toward `presentation/application/domain/infrastructure`
- `bootJar` guidance/reporting that does not treat `:bootJar SKIPPED` as a valid executable Spring Boot build pass

Do not include as alpha.3 scope:

- frontend productization
- infra productization
- desktop app
- TDD workflow automation
- AST/linter/enforcement gates
- generated app product-quality certification

## Release Gate

Before cutting `v0.3.0-alpha.3`, run:

```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
npm publish --dry-run --tag alpha
```

Also run at least one clean workflow smoke:

```bash
tmp_project=$(mktemp -d)
cd "$tmp_project"
npm init -y
npm install -D persona-harness@alpha
npx ph init
npx ph intake
npx ph policy init
npx ph plan
npx ph plan --accept
npx ph plan --implement
```

## Decision Rule

Cut `0.3.0-alpha.3` when all of these are true:

1. `ph plan --next` and `ph plan --resume` have passing tests and a clean workflow smoke.
2. The package-flow/`bootJar` fresh ON evidence remains documented.
3. `npm pack --dry-run` and `npm publish --dry-run --tag alpha` show the expected package contents.
4. The release notes clearly state that alpha.3 is still an alpha workflow/tooling release, not generated app product-quality certification.

If these checks fail, keep the version at `0.3.0-alpha.2` and continue implementation.

## Known Gaps To Mention If Released

- TUI implementation can still stop before code generation on large clean-project requests.
- Read Coverage evidence fields are generated, but a clean filled report using them has not yet been observed in a completed TUI implementation run.
- OpenCode behavior varies by model and runtime context.
- `ph plan --resume` produces a continuation prompt from local report evidence; it does not automatically continue OpenCode by itself.
- package-flow and `bootJar` evidence is fresh positive evidence, not an enforcement gate.