# v0.3.5-alpha.0 Release Notes

## Summary

`0.3.5-alpha.0` clarifies the setup split between a human terminal and an AI/non-TTY shell.

Historical v0.3.5 behavior split human terminal setup from AI/non-TTY setup. Current behavior supersedes that split: `ph init` installs Persona Harness config/rules and OpenCode plugin config only, while `npx ph bootstrap backend` prepares the backend profile, policy, accepted plan, and workflow templates.

## Changed

- `ph init` no longer falls through to the generic interactive-intake TTY error in non-TTY contexts.
- Non-TTY `ph init` explained the setup split that is now expressed as:
  - minimal install path: run `npx ph init`;
  - backend-ready path: run `npx ph bootstrap backend`;
  - custom profile path: run `npx ph intake --interactive` or `npx ph intake --default backend`.
- Persona injection guidance now tells agents not to attempt interactive prompts from AI/non-TTY shells.
- README and workflow role docs now separate the user interview path from the AI bootstrap path.

## Supported Flow

Human setup:

```bash
npm install -D persona-harness@alpha
npx ph init
# answer the backend interview
npx ph policy init
npx ph plan --auto-accept
```

AI/non-TTY setup:

```bash
npx ph bootstrap backend
```

## Verification

- `npm test -- tests/persona-harness-init.test.ts tests/phase0-hooks.test.ts tests/persona-harness-interactive-intake.test.ts`
- `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`
- non-TTY `ph init` smoke
- TTY `ph init` smoke
- `ph bootstrap backend` smoke

## Known Gaps

- Interactive terminal behavior is intentionally not guaranteed inside every OpenCode/Codex TUI agent shell.
- `ph bootstrap backend` remains the deterministic AI/non-TTY fast path.
- This release still does not certify generated application product quality.