# 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