23 lines
752 B
Markdown
23 lines
752 B
Markdown
# US03-05 — Automate Phase C End-to-End Acceptance
|
||
|
||
Epic: [E03](../E03-album-proposals.md)
|
||
|
||
As a delivery owner, I want automated proposal journeys so generation, editing, and
|
||
approval remain deterministic and non-mutating.
|
||
|
||
## Acceptance criteria
|
||
|
||
- Journeys cover evidence aggregation, success, provider failure, invalid name,
|
||
collision, editing, stale approval, valid approval, reload, and restart.
|
||
- Tests assert provider inputs, persisted versions, and unchanged fixture paths.
|
||
- Story IDs US03-01 through US03-04 map to passing automated tests.
|
||
|
||
## Automated tests
|
||
|
||
- One command runs Phase C API and Playwright suites with the deterministic provider.
|
||
- Phase A–B end-to-end suites remain green.
|
||
|
||
## Dependencies
|
||
|
||
- US03-01 through US03-04
|