# v0.3.8-alpha.0 Release Notes

## Version

`v0.3.8-alpha.0`

## 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 focuses on workflow reliability for long Java/Spring backend implementation runs.

The main problem addressed is that a generated project can satisfy technical constraints, but `ph workflow finish implement` still reports a bare pending ticket with too little guidance. This release makes pending tickets visible, gives the AI a clear continuation path, and prevents completion claims while workflow tickets remain open.

## Added

- Pending ticket detail in `ph workflow finish implement` failure output:
  - ticket id;
  - title;
  - task-card path;
  - `npx ph workflow next`;
  - `npx ph workflow archive <ticket>` when the ticket has been reviewed and completed.
- Technical-constraints satisfied-candidate guidance.
  - Technical constraints are not auto-archived.
  - When workflow reports, read coverage, profile read coverage, stack alignment, command discipline, and evidence are already passing, the finish output says the technical-constraints ticket may already be satisfied and should be archived only after review.
- Pending ticket context in `ph workflow continue`.
- Runtime reliability guard lines for implementation and continuation rails.

## Changed

- `.persona` projects without a ready backend profile now get clearer implementation-rail guidance:
  - interactive path: `npx ph intake --interactive`;
  - AI/non-TTY fast path: `npx ph bootstrap backend`.
- Runtime implementation guidance now states:
  - read `.persona/project-profile.jsonc` before implementation;
  - do not implement if the profile exists but has not been read;
  - do not generate a stack that conflicts with the profile;
  - continue pending workflow tickets instead of claiming all work is complete.
- Requirements runtime guidance now keeps prompt-only requirements on the draft/review-before-implementation rail unless the user has approved the draft.

## Verification

Repository verification from the current worktree:

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

Observed result on 2026-06-24:

- `npm test`: passed, 47 files / 308 tests.
- `npm run typecheck`: passed.
- `npm run build`: passed.
- `npm pack --dry-run`: passed.

Focused session verification:

- CLI workflow focused tests passed.
- Runtime/Injection focused tests passed.
- Built CLI smoke covered:
  - `workflow --help`;
  - `workflow check`;
  - `workflow finish implement` with pending ticket output;
  - `workflow continue` with pending ticket output.

## Known Gaps

- Technical-constraints tickets are only surfaced as review/archive candidates. They are not auto-completed.
- Prompt-only requirements still need a stronger end-to-end clean smoke after this package is published.
- Evidence summaries can still be noisy for intent-heavy runs.
- This release does not certify generated application product quality.

## Next

- Publish `persona-harness@0.3.8-alpha.0` with the `alpha` tag after final approval.
- Run one clean workflow smoke after publish:
  - `ph bootstrap backend`;
  - prompt/README requirements;
  - `workflow split`;
  - implementation;
  - `workflow finish implement`.