30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# US07-07 — Automate Full Release Acceptance
|
|
|
|
Epic: [E07](../E07-hardening-release.md)
|
|
|
|
As a release owner, I want one reproducible automated release gate so every user story
|
|
and complete workflow is proven before real-library mutation is enabled.
|
|
|
|
## Acceptance criteria
|
|
|
|
- A story-to-test matrix contains every backlog story with no missing, skipped, or
|
|
failing required test.
|
|
- One fresh-environment journey runs discovery, duplicate review, safety, analysis,
|
|
EXIF verification, album proposal, rename, rescan, upload, archive, offline
|
|
deduplication, restore, and full process restarts.
|
|
- Security, migration, donor parity, crash recovery, accessibility, responsive UI,
|
|
browser console/network, fixture reproducibility, and archive safety gates pass.
|
|
- A read-only real-library dry run produces an explicitly approved reconciliation
|
|
report before mutation can be configured.
|
|
|
|
## Automated tests
|
|
|
|
- One documented release command provisions and destroys the full isolated stack and
|
|
retains signed/versioned evidence.
|
|
- Chromium passes every change; supported cross-browser and full soak suites pass for
|
|
release; all earlier epic suites run unchanged.
|
|
|
|
## Dependencies
|
|
|
|
- US07-01 through US07-06
|