domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US06-04 — Plan and Execute Safe Restores #35

New Issue
Closed
opened 2026-07-13 13:10:50 +02:00 by domverse · 3 comments
domverse commented 2026-07-13 13:10:50 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US06-04-restore.md

US06-04 — Plan and Execute Safe Restores

Epic: E06

As a user, I want archived assets restored to collision-free active paths so I can
recover originals without losing identity or previous decisions.

Acceptance criteria

  • Restore preflight requires the correct archive identity, matching bytes, capacity,
    safe destination, and no conflicting lease.
  • Restore copies, closes, verifies, atomically publishes, and registers an active
    occurrence while preserving asset identity and stage history.
  • Collisions never overwrite; mismatches become stale/divergent states.
  • Restore is journaled, resumable, and idempotent.

Automated tests

  • Tests cover offline media, wrong volume, normal restore, collision, changed archive
    bytes, interruption, repeated restart, and preserved decisions.

Dependencies

  • US06-03
Source specification: [delivery_backlog/stories/US06-04-restore.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US06-04-restore.md) # US06-04 — Plan and Execute Safe Restores Epic: [E06](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E06-archive-lifecycle.md) As a user, I want archived assets restored to collision-free active paths so I can recover originals without losing identity or previous decisions. ## Acceptance criteria - Restore preflight requires the correct archive identity, matching bytes, capacity, safe destination, and no conflicting lease. - Restore copies, closes, verifies, atomically publishes, and registers an active occurrence while preserving asset identity and stage history. - Collisions never overwrite; mismatches become stale/divergent states. - Restore is journaled, resumable, and idempotent. ## Automated tests - Tests cover offline media, wrong volume, normal restore, collision, changed archive bytes, interruption, repeated restart, and preserved decisions. ## Dependencies - US06-03
domverse added this to the E06 — Archive Lifecycle milestone 2026-07-13 13:10:50 +02:00
domverse added the type/featurearea/backendpriority/criticalarea/filesystem labels 2026-07-13 13:10:50 +02:00
domverse added a new dependency 2026-07-13 13:11:29 +02:00
#34 US06-03 — Preserve Offline Identity and Review Evidence
domverse added a new dependency 2026-07-13 13:11:30 +02:00
#36 US06-05 — Operate Archive and Restore in the Browser
domverse added a new dependency 2026-07-13 13:11:31 +02:00
#37 US06-06 — Automate Phase F End-to-End Acceptance
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:47 +02:00
domverse added the status/backlog label 2026-07-13 13:52:54 +02:00
domverse added status/in-progress and removed status/backlog labels 2026-08-16 19:22:34 +02:00
domverse self-assigned this 2026-08-16 19:22:34 +02:00
domverse commented 2026-08-16 19:22:35 +02:00
Author
Owner
Copy Link

Claimed for implementation on branch us/US06-04-plan-and-execute-safe-restores.

Claimed for implementation on branch `us/US06-04-plan-and-execute-safe-restores`.
domverse added status/review and removed status/in-progress labels 2026-08-16 19:49:01 +02:00
domverse commented 2026-08-16 19:49:02 +02:00
Author
Owner
Copy Link

Submitted for review: #80

Tests passed:

  • work_item/scripts/python -m unittest discover -s work_item/tests -v
  • work_item/scripts/python -m pytest tests -q
  • work_item/scripts/python -m pytest tests/integration/test_restore.py -q
Submitted for review: https://git.domverse-berlin.eu/domverse/photoanalyzer/pulls/80 Tests passed: - `work_item/scripts/python -m unittest discover -s work_item/tests -v` - `work_item/scripts/python -m pytest tests -q` - `work_item/scripts/python -m pytest tests/integration/test_restore.py -q`
domverse added status/done and removed status/review labels 2026-08-16 19:49:24 +02:00
domverse commented 2026-08-16 19:49:25 +02:00
Author
Owner
Copy Link

Completed and merged via PR #80.

Completed and merged via PR #80.
domverse moved this to Done in Photo Analyzer Delivery on 2026-08-16 20:00:12 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/backend area/filesystem priority/critical status/done type/feature
Milestone
No items
No Milestone E06 — Archive Lifecycle
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees domverse
1 Participants
Notifications
Due Date
No due date set.
Blocks
#36 US06-05 — Operate Archive and Restore in the Browser
domverse/photoanalyzer
#37 US06-06 — Automate Phase F End-to-End Acceptance
domverse/photoanalyzer
Depends on
#34 US06-03 — Preserve Offline Identity and Review Evidence
domverse/photoanalyzer
Reference: domverse/photoanalyzer#35
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?