# v0.3.7-alpha.1 Release Notes

## Version

`v0.3.7-alpha.1`

## Dist Tag

`alpha`

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

## Summary

This alpha tightens workflow completion gates for Java/Spring backend generation.

The key change is that Persona Harness no longer lets an AI-facing implementation run finish without evidence that `.persona/project-profile.jsonc` was read. This addresses the external-test failure mode where a project profile existed, but the generated output drifted into a different stack.

## Added

- `profile read coverage` in `ph workflow check`.
- `project profile read coverage must be recorded` blocking reason in `ph workflow finish implement`.
- Project-profile read fields in `.persona/workflow/implementation-report.md` templates:
  - `Project profile read method`;
  - `Project profile ranges read`.
- Review checklist item requiring project profile read evidence.
- AI-facing implementation guidance to read `.persona/project-profile.jsonc` before implementation.

## Changed

- Workflow PASS now requires all of:
  - accepted plan;
  - filled implementation report;
  - filled review report;
  - README read coverage when `README.md` exists;
  - project-profile read coverage when the backend profile is ready;
  - command discipline PASS;
  - Java/Spring/Gradle stack alignment PASS.
- Existing workflow noise tests now include profile read evidence so raw-shell noise classification is not confused with profile coverage failure.
- `.persona-continuation-test-fixtures/` is ignored as local test output.

## Fixed

- AI runs that ignore `.persona/project-profile.jsonc` can no longer finish cleanly when a backend profile is present.
- External-test cases where profile exists but generated output uses the wrong stack now have a clearer next action:
  - read the project profile;
  - record profile read method/range;
  - align generated stack with Java/Spring/Gradle.

## Verification

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

All passed on 2026-06-24.

Manual CLI smoke:

- Created a temporary backend profile project.
- Confirmed `ph workflow check` reports `profile read coverage: project profile exists but profile read coverage is empty` when the implementation report and evidence omit `.persona/project-profile.jsonc`.
- Confirmed `ph workflow finish implement` fails with `project profile read coverage must be recorded`.
- Added project-profile read evidence.
- Confirmed `ph workflow check` becomes PASS and `ph workflow finish implement` becomes PASS.

Clean OpenCode verification after push:

- Clean project path: `/Users/yongtae/Desktop/persona-clean-profile-read-check`.
- Prompt: `README.md 보고 구현해줘`.
- OpenCode read `README.md` through `npx ph bearshell` ranges.
- OpenCode read `.persona/project-profile.jsonc` before implementation.
- Generated Java/Spring Gradle Equipment Rental API.
- `npx ph review backend-shape` reported PASS for Gradle only, package layers, domain repository ports, infrastructure adapters, service storage/id sequence ownership, domain behavior, DTO boundary, `bootJar`, and verification report.
- `npx ph bearshell --shell 'gradle test'` passed.
- `npx ph bearshell --shell 'gradle build'` passed.
- HTTP smoke passed for equipment create/list and missing-equipment rental 404.
- After archiving both workflow tickets, `npx ph workflow finish implement` passed.

## Known Gaps

- Profile read coverage verifies that the profile was read; it does not yet compare every profile option such as `JPA` versus `JdbcTemplate`, package mode, or DTO strictness against generated files.
- `workflow split` can split technical constraints into a separate ticket even when the main implementation already satisfies them; the AI did not automatically archive that second ticket in the clean run.
- `ph workflow check` can remain WARN for non-blocking raw shell environment probes even after final verification is rerun through `npx ph bearshell`.
- Evidence summary still shows many intent/unknown records and only a subset of generated Java role targets.
- This release does not certify generated application product quality.

## Next

- Add a narrower profile-to-output alignment check for selected backend profile fields.
- Improve workflow ticket closure when technical-constraint tickets are already satisfied by the generated code.
- Improve evidence summary readability for intent-heavy runs.