# v0.3.4-alpha.0 Release Notes

## Version

`v0.3.4-alpha.0`

## Dist Tags

Observed after publish:

```json
{
  "latest": "0.3.2-alpha.3",
  "alpha": "0.3.4-alpha.0"
}
```

`alpha` now points to `0.3.4-alpha.0`. `latest` still points to `0.3.2-alpha.3` until the npm dist-tag update is authenticated.

## npm Package

`persona-harness@0.3.4-alpha.0`

## Summary

This alpha strengthens continuation workflow for long README implementations. The goal is to make an interrupted TUI/OpenCode run easier to resume without repeating completed work or drifting away from the accepted plan.

`persona-harness@0.3.4-alpha.0` has been published to npm with the `alpha` tag.

## What Changed

- `implementation-report.md` now asks the agent to record:
  - completed requirements;
  - incomplete requirements;
  - last completed requirement/file;
  - remaining README/plan range;
  - remaining implementation scope;
  - interruption reason;
  - next command/action;
  - next prompt hint.
- `ph plan --next` now detects remaining scope in a filled implementation report and recommends:

```bash
npx ph workflow continue
```

- `ph workflow continue` / `ph plan --resume` now prints:
  - previous read coverage;
  - completed and incomplete requirements;
  - remaining README/plan ranges;
  - remaining implementation scope;
  - interruption reason;
  - next action and prompt hint;
  - unchecked checklist items from `.persona/workflow/plan.md`.
- Workflow report templates were moved to `src/cli/workflow-templates.ts` so `src/cli/plan.ts` stays focused on plan creation.

## Long README Smoke

Smoke setup:

- repo-external temporary project;
- `npx ph init`;
- `npx ph intake --default backend --force`;
- synthetic 260-line `README.md`;
- `npx ph plan --auto-accept`;
- simulated interrupted implementation report:
  - completed: Step 1-40;
  - incomplete: Step 41-260;
  - remaining range: `README 221-end`;
  - interruption reason: first TUI pass stopped after CRUD.

Observed:

- `ph plan --next` printed `Continuation is next`.
- `ph plan --next` recommended `npx ph workflow continue`.
- `ph workflow continue` printed the recorded continuation evidence.
- `ph workflow continue` included plan unchecked items so the next run has both previous progress and accepted-plan context.

## Supported Scope

- Java/Spring backend MVP.
- AI-facing workflow continuation rail.
- Report/evidence-based continuation hints.
- No autonomous OpenCode execution.
- No generated app product-quality certification.

## Not Supported

- Automatic completion of remaining README items without the agent following the continuation prompt.
- TDD workflow productization.
- Frontend, infra, or desktop workflow productization.
- Rule compliance enforcement, AST/linter gates, or generated app quality certification.

## Verification

Pre-publish commands:

```bash
npm test
npm run typecheck
npm run build
npm pack --dry-run
```

Result:

- `npm test`: PASS, 36 test files / 239 tests.
- `npm run typecheck`: PASS.
- `npm run build`: PASS.
- `npm pack --dry-run`: PASS, `persona-harness-0.3.4-alpha.0.tgz`, 233 files, 248.1 kB package size, 959.5 kB unpacked size.
- TypeScript no-excuse checker: PASS on changed TypeScript files.
- Long README continuation smoke: PASS.

## Known Gaps

- Continuation depends on the agent recording accurate implementation-report evidence.
- `ph workflow continue` prints the resume rail; it does not launch or supervise OpenCode by itself.
- Full Test -> Feat -> Refactor workflow remains future scope.

## Install

External testers can install the alpha tag now:

```bash
npm install -D persona-harness@alpha
npx ph init
npx ph bootstrap backend
npx ph plan --auto-accept
```

- First prompt:

```text
README.md 보고 구현해줘
```

- If the run stops early:

```text
npx ph workflow continue 실행하고 남은 요구사항만 이어서 구현해줘
```

## Next

- Authenticate and update npm `latest` to `0.3.4-alpha.0` if default `npm install -D persona-harness` should resolve to this alpha.
- Ask external testers to retry long README implementation using `persona-harness@alpha`.