23 lines
782 B
Markdown
23 lines
782 B
Markdown
# US05-04 — Verify, Retry, and Resolve Uncertain Uploads
|
|
|
|
Epic: [E05](../E05-immich-upload.md)
|
|
|
|
As a user, I want uncertain uploads verified before retry so a lost response cannot
|
|
create duplicate server assets.
|
|
|
|
## Acceptance criteria
|
|
|
|
- Retry policy distinguishes safe failures from accepted-but-unknown outcomes.
|
|
- Verification compares recorded local bytes with authoritative available evidence.
|
|
- Changed-after-upload bytes create a visible stale warning and block unsafe actions.
|
|
- Manual resolution records evidence and audit history; it never silently assumes success.
|
|
|
|
## Automated tests
|
|
|
|
- Fault tests cover timeout before acceptance, acceptance then lost response, parser
|
|
uncertainty, safe retry, changed bytes, and repeated verification.
|
|
|
|
## Dependencies
|
|
|
|
- US05-03
|