# v0.3.8-alpha.2 Release Notes

## Version

`v0.3.8-alpha.2`

## 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 narrow follow-up to the v0.3.8 workflow reliability track.

It prepares the runtime and CLI changes that make two release-critical signals easier to observe:

- README/project-bootstrap injection evidence now records whether the backend profile summary was injected into the same block;
- pending workflow ticket guidance now explicitly tells agents not to claim overall completion while pending tickets remain.

This release does not certify generated Java/Spring product quality or full OpenCode implementation completion.

## Added

- `profileSummaryInjected` evidence for phase0 runtime injection records.
- Pending workflow ticket completion guidance in:
  - `ph workflow check`;
  - `ph workflow continue`;
  - `ph workflow finish implement`.

## Changed

- Bootstrap injection evidence documentation now explains that `profileSummaryInjected` distinguishes backend profile summary injection from AGENTS-only signals.
- Pending-ticket CLI output now repeats the completion boundary near the affected ticket/status output.

## External Smoke

External Smoke result: partially successful.

Observed before release prep:

- Install source was a local current-head tarball based on `2757e0e` with the pending workflow guidance commit `bf5bfbb` included.
- `profileSummaryInjected` marker evidence was observed in four README-read phase0 evidence files, including model-input, tool-output, and pending-store evidence.
- Pending tickets `req-1` through `req-4` existed after `workflow split README.md`.
- `npx ph workflow check` printed `Do not claim overall completion while pending tickets remain.`
- `npx ph workflow continue` printed `Do not claim overall completion while this ticket remains pending.`
- `npx ph workflow finish implement` exited 1 and printed `Do not claim overall completion while pending tickets remain.`

OpenCode bounded smoke for `README.md 보고 구현해줘` reached `npx ph workflow implement` plus profile/plan reads, but stopped on a `.persona/policies` policy path issue caused by permission auto-reject. Pending-flow behavior in a full OpenCode implementation was therefore not fully observed.

Follow-up policy path smoke before publish:

- Install source was local current HEAD `59d0f39` packed as `persona-harness@0.3.8-alpha.2` from `/tmp/persona-harness-0.3.8-alpha.2.tgz`.
- Tarball shasum was `76e989d795cc2ce8aa21918865648afbf5073697`.
- Clean project was `/tmp/persona-harness-policies-path-smoke-dzloFo`.
- `.persona/policies` structure was normal: `company/backend.md`, `personal/backend.md`, `overlay.jsonc`, and overlay sources were present.
- Bounded OpenCode command was `timeout 120 opencode run --print-logs --log-level DEBUG "README.md 보고 구현해줘"`.
- The previous `.persona/policies` permission auto-reject did not reproduce.
- Targeted grep found no `external_directory`, `auto-reject`, `permission requested`, `rejected`, or `The user rejected` entries.
- `.persona/policies` appeared only in the `Glob "**/*"` listing and did not proceed to Read, touch, or permission request.
- OpenCode processed README, project profile, workflow backlog, task, plan, and requirements-analysis files before the 120-second bound ended.
- Archive: `/Users/yongtae/Desktop/persona-harness-artifacts/archive/2026-06-24-desktop-persona-runs/v038-alpha2-policies-path-59d0f39`.

Publish judgment for the policy path issue: the `.persona/policies` permission auto-reject can be removed as a publish blocker. This does not certify full OpenCode implementation quality.

## Verification

Repository verification from the release prep worktree:

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

Observed result on 2026-06-24:

- `npm test`: passed. Scope diagnostics PASS, docs taxonomy diagnostics PASS, 51 files / 327 tests.
- `npm run typecheck`: passed.
- `npm run build`: passed.
- `npm pack --dry-run`: passed for `persona-harness@0.3.8-alpha.2`.
  - Filename: `persona-harness-0.3.8-alpha.2.tgz`
  - Total files: 309

## Known Gaps

- External Smoke is partially successful, not a full success.
- OpenCode full implementation quality remains unverified; the bounded run ended at 120 seconds.
- Pending-flow guidance was confirmed through CLI surfaces, but not through a completed full OpenCode implementation run.
- OpenCode was observed directly reading `.persona/rules/backend/...`; that is outside this release-docs update and should be checked separately.
- This release does not certify generated app product quality.
- This release does not add AST, linter, or enforcement gates.

## Recommended Before Publish

- Treat the `.persona/policies` path issue as non-reproduced for publish-blocker purposes.
- Track the direct `.persona/rules/backend/...` read observation as a separate follow-up risk.
- Keep release messaging limited to evidence/guidance observability, not full implementation completion guarantees.