# v0.3.8-alpha.5 Release Notes

## Version

`v0.3.8-alpha.5`

## 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 is a workflow rail, continuation, and backend-shape false-positive reduction release.

Persona Harness should be described as an AI coding workflow rail + evidence + continuation harness. It is not a Java Clean Code quality guarantee, generated app product-quality certification, AST/linter, or enforcement engine.

## What Changed

- Repositioned release-facing docs around workflow rails, evidence traces, and continuation state.
- Added a runtime hook/evidence boundary so evidence writes are best-effort and evidence write failures do not reject the host hook.
- Guarded injection context loading failures, including the case where `.persona/project-profile.jsonc` is unexpectedly a directory, so those failures do not propagate as hook rejection.
- Strengthened Gradle wrapper consistency guidance so generated Java/Spring projects are expected to produce and use real wrapper files:
  - `gradlew`;
  - `gradlew.bat`;
  - `gradle/wrapper/gradle-wrapper.jar`;
  - `gradle/wrapper/gradle-wrapper.properties`.
- Added failed verification continuation guidance so compile/test/build failures remain unfinished workflow work.
- Reduced backend-shape false positives for:
  - Domain/DTO naming;
  - entity-name mentions inside DTO messages;
  - backend-shape verification evidence visibility.
- Kept backend-shape as report-only guidance. It is not an AST/linter/enforcement gate.
- Kept normal injection/evidence behavior intact while making failure paths safer for the host runtime.

## External Smoke

Long continuation finish PASS smoke result: successful for workflow rail closure.

Install/source:

- install source: local `npm pack` tarball;
- registry `alpha`/`latest`: stale for the tested commits, so registry package was not used;
- local HEAD: `d0eb111 fix(cli): reduce backend shape domain dto false positives`;
- package version during smoke: `0.3.8-alpha.4`;
- included commits: `99752aa`, `cd646f0`, `d0eb111`;
- archive: `/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/long-continuation-20260625-142053-d0eb111`;
- summary: `summary.md`;
- final artifact: `windows/artifact-copy-final.zip`.

Observed flow:

- Windows clean ON project used the same `Inventory Lending API` README.
- Initial run timed out at 600 seconds after README/profile read, workflow implement/split/next, and Java/Spring/Gradle generation.
- Continuation 1 timed out at 900 seconds after reports fill, Gradle wrapper creation, and `test`/`build`/`bootRun` execution. Some stale verification wording remained.
- Continuation 2 exited 0 after reports were updated, `req-1` was archived, and `workflow finish implement` passed.

Final workflow state:

- `implementation-report.md`: filled.
- `review-report.md`: filled.
- `req-1`: archived.
- final `workflow finish implement`: PASS exit 0.
- final `workflow check`: WARN, but blocking items were cleared:
  - reports filled;
  - verification failure none;
  - stack alignment OK;
  - pending none;
  - Java role read coverage present.

Gradle evidence:

- `gradlew` generated.
- `gradlew.bat` generated.
- `gradle/wrapper/gradle-wrapper.jar` generated.
- `gradle/wrapper/gradle-wrapper.properties` generated.
- `gradlew.bat test`: BUILD SUCCESSFUL.
- `gradlew.bat build`: BUILD SUCCESSFUL.
- `bootRun` started the server and then timed out while running.

Backend-shape PASS evidence:

- Spring Boot app.
- Gradle runtime.
- Gradle only.
- Maven absent.
- fake shim absent.
- layer/package structure.
- Controller/Service/Repository/DTO/Domain boundary.
- Domain repository port.
- Infrastructure repository adapter.
- Service storage/id sequence ownership.
- Domain behavior.
- DTO boundary.
- bootJar.

Remaining backend-shape WARN candidates:

- Entity direct exposure.
- Verification report.

Other evidence:

- `.persona/evidence` present.
- `profileSummaryInjected` confirmed.
- Java role read coverage evidence confirmed.
- fake `gradle-shim.js`, Java `HttpServer`, and Express/CommonJS workarounds were not observed.

## Verification

Repository verification from the release prep worktree:

```bash
npm test
npm run typecheck
npm run build
npm pack --dry-run
npm run check:docs
```

Observed result on 2026-06-25:

- `npm test`: passed. Scope diagnostics PASS, docs taxonomy diagnostics PASS, 56 files / 355 tests.
- `npm run typecheck`: passed.
- `npm run build`: passed.
- `npm pack --dry-run`: passed for `persona-harness@0.3.8-alpha.5`.
  - Filename: `persona-harness-0.3.8-alpha.5.tgz`
  - Total files: 336
- `npm run check:docs`: passed.

## Known Gaps

- This release does not certify generated app product quality.
- Runtime hook/evidence boundary hardening is a host-stability improvement, not generated app quality certification.
- Evidence means read/injection/workflow traces, not a quality score.
- A/B and ON/OFF smoke results remain stack-steering signals with sample-size, non-blind, same-operator, model/version, prompt, timeout, and continuation limitations.
- AST/linter/build-failure enforcement is still not part of Persona Harness.
- Registry stale must be resolved by publishing the next prerelease; this release prep does not publish.

## Recommended Before Publish

- Publish only as a prerelease alpha.
- Keep release messaging focused on workflow rail closure, continuation reliability, and backend-shape false-positive reduction.
- Do not describe the long continuation smoke as generated app product quality certification.