Bootstrap project and safe work-item workflow
This commit is contained in:
22
delivery_backlog/stories/US04-06-phase-d-e2e.md
Normal file
22
delivery_backlog/stories/US04-06-phase-d-e2e.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# US04-06 — Automate Phase D End-to-End Acceptance
|
||||
|
||||
Epic: [E04](../E04-guarded-renaming.md)
|
||||
|
||||
As a delivery owner, I want exhaustive automated rename journeys so every crash point
|
||||
and stale condition is proven safe.
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
- Journeys cover plan/export, confirmation, valid apply, case-only rename, collision,
|
||||
stale source, cancellation boundary, every journal crash point, recovery, and rollback.
|
||||
- Stable IDs, hashes, asset set, journal, and UI state are asserted after restart.
|
||||
- Story IDs US04-01 through US04-05 map to passing automated tests.
|
||||
|
||||
## Automated tests
|
||||
|
||||
- One command runs API, filesystem fault-injection, and Playwright rename suites.
|
||||
- Phases A–C remain green and the source fixture corpus remains unchanged.
|
||||
|
||||
## Dependencies
|
||||
|
||||
- US04-01 through US04-05
|
||||
Reference in New Issue
Block a user