# Review Progress Observability Implementation Plan

## Goal

Make `/code-review` visibly active during long-running work and retain concise, safe stage summaries in the Pi conversation without changing review or publication semantics.

## Tasks

1. Add typed, optional orchestrator progress events for triage, summary, reviewers, validation, aggregation, failure, and cancellation.
2. Add a Pi progress presenter that animates widget/footer status, renders selected milestones, and cleans up idempotently.
3. Connect preflight, orchestrator, and publication stages in the extension while preserving existing final reports.
4. Add orchestrator and presenter tests for event order, parallel completion counts, animation, safe UI failures, and all cleanup paths.
5. Document `quietStartup`, `pi --verbose`, and the new progress experience in README and changelog.
6. Run formatting/type checks, the complete test suite, and package tarball verification.

## Acceptance Criteria

- The running UI changes at least once per second and always names the active stage.
- Reviewer and validator counters reflect completed work accurately.
- The conversation retains only useful structured milestones and never raw reasoning or subprocess JSONL.
- UI reporting failures do not change review results.
- Timers, widgets, and footer status are removed after success, failure, and cancellation.
- Existing terminal reports and opt-in GitHub publication remain behaviorally unchanged.