25 lines
794 B
Markdown
25 lines
794 B
Markdown
# US03-04 — Review and Approve Proposals in the Browser
|
|
|
|
Epic: [E03](../E03-album-proposals.md)
|
|
|
|
As a user, I want to inspect evidence, edit a proposal, and approve it so I retain
|
|
control over album naming.
|
|
|
|
## Acceptance criteria
|
|
|
|
- The view shows source album, suggested name, evidence summary, rationale, confidence,
|
|
validation issues, and affected count.
|
|
- Edits validate promptly; collisions and invalid names are actionable.
|
|
- Approval requires explicit action and rejects stale state visibly.
|
|
- Reload preserves edits and approval state through the API.
|
|
|
|
## Automated tests
|
|
|
|
- UI tests cover editing, errors, collision guidance, approval, stale conflict, and
|
|
keyboard operation.
|
|
- Playwright asserts no file path changes occur during proposal approval.
|
|
|
|
## Dependencies
|
|
|
|
- US03-03
|