24 lines
834 B
Markdown
24 lines
834 B
Markdown
# US06-06 — Automate Phase F End-to-End Acceptance
|
||
|
||
Epic: [E06](../E06-archive-lifecycle.md)
|
||
|
||
As a delivery owner, I want archive lifecycle automation so removal, offline behavior,
|
||
recovery, and restore are proven without risking real files.
|
||
|
||
## Acceptance criteria
|
||
|
||
- Journeys cover preflight blockers, copy/verify/remove, same-filesystem behavior,
|
||
every interruption point, offline deduplication, mount return, restore, and collision.
|
||
- API, journal, manifest, paths, hashes, previews, and durable state are asserted after
|
||
restart; no source is removed before archive verification.
|
||
- Story IDs US06-01 through US06-05 map to passing automated tests.
|
||
|
||
## Automated tests
|
||
|
||
- One command runs archive fault-injection, black-box API, and Playwright suites.
|
||
- Phases A–E remain green.
|
||
|
||
## Dependencies
|
||
|
||
- US06-01 through US06-05
|