# Review / Closeout: Interactive Pi Questionnaire Extension

## Summary
Implementation matches the ticket scope and acceptance criteria. The ticket can be considered **Done pending a scoped commit** of only the questionnaire-related files and explicitly intended policy-reference changes.

## Files Reviewed
- `tickets/done/2026-06-06-interactive-pi-questionnaire-extension.md`
- `.pi/extensions/questionnaire.ts`
- `.pi/extensions/README.md`
- `AGENTS.md`
- `docs/question-asking-policy.md`

## Verification
Automated:
- `git status --short && git diff -- tickets/done/2026-06-06-interactive-pi-questionnaire-extension.md .pi/extensions/questionnaire.ts .pi/extensions/README.md AGENTS.md docs/question-asking-policy.md` — confirmed target files plus many unrelated dirty/untracked files exist.
- `NODE_PATH=/usr/local/lib/node_modules:/usr/local/lib/node_modules/@earendil-works/pi-coding-agent/node_modules node ... createJiti ...` — loaded `.pi/extensions/questionnaire.ts`; registered `tools:["questionnaire"]`, `commands:["questionnaire-demo"]`.
- `pi --no-extensions -e .pi/extensions/questionnaire.ts --list-models questionnaire-smoke` — exited `0`.

Manual:
- Static review confirms schema includes question `id`, optional `label`, `prompt`, and option arrays.
- Static review confirms selectable options, custom responses, option extension text, back/forward navigation, review screen, and submitted result text paths are implemented.
- Ticket records user-performed interactive `/questionnaire-demo` validation after `/reload` with two submitted answers.
- `AGENTS.md` and `docs/question-asking-policy.md` both instruct use of interactive `questionnaire` over plain numbered lists for multi-question / closed selectable questions.

## Critical Issues
- None found.

## Warnings / Follow-ups
- Manual interactive evidence covers the happy-path demo selection flow only; custom response, option extension text, back/edit, cancel, and review-submit gating were verified statically but not recorded as manually exercised.
- `.pi/extensions/questionnaire.ts` duplicates the questionnaire UI logic between the demo command and tool execution path; acceptable for this pilot, but a future refactor should reuse one UI runner to reduce drift.
- Working tree contains substantial unrelated dirty/untracked work. Commit must be path-scoped to avoid mixing unrelated changes.

## Rollback Notes
- Remove `.pi/extensions/questionnaire.ts`.
- Revert the `.pi/extensions/README.md` questionnaire line.
- Revert questionnaire-policy additions in `AGENTS.md` and `docs/question-asking-policy.md` if the tool is not adopted.
- If committed, use a scoped revert of the questionnaire commit rather than broad working-tree reset because unrelated dirty work exists.