US06-06 — Automate Phase F End-to-End Acceptance #37
Notifications
Due Date
No due date set.
Blocks
Depends on
#38 US07-01 — Complete Donor Migration and Freeze the CLI Archive
domverse/photoanalyzer
#32 US06-01 — Configure and Preflight Archive Destinations
domverse/photoanalyzer
#33 US06-02 — Transfer, Verify, and Remove Active Sources
domverse/photoanalyzer
#34 US06-03 — Preserve Offline Identity and Review Evidence
domverse/photoanalyzer
#35 US06-04 — Plan and Execute Safe Restores
domverse/photoanalyzer
#36 US06-05 — Operate Archive and Restore in the Browser
domverse/photoanalyzer
Reference: domverse/photoanalyzer#37
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source specification: delivery_backlog/stories/US06-06-phase-f-e2e.md
US06-06 — Automate Phase F End-to-End Acceptance
Epic: E06
As a delivery owner, I want archive lifecycle automation so removal, offline behavior,
recovery, and restore are proven without risking real files.
Acceptance criteria
every interruption point, offline deduplication, mount return, restore, and collision.
restart; no source is removed before archive verification.
Automated tests
Dependencies
Claimed for implementation on branch
us/US06-06-automate-phase-f-end-to-end-acceptance.Submitted for review: #82
Tests passed:
work_item/scripts/python -m unittest discover -s work_item/tests -vwork_item/scripts/python -m pytest tests -qwork_item/scripts/python -m pytest -m phase_f -qCompleted and merged via PR #82.