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

US07-07 — Automate Full Release Acceptance #44

New Issue
Open
opened 2026-07-13 13:10:54 +02:00 by domverse · 0 comments
domverse commented 2026-07-13 13:10:54 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US07-07-release-e2e.md

US07-07 — Automate Full Release Acceptance

Epic: E07

As a release owner, I want one reproducible automated release gate so every user story
and complete workflow is proven before real-library mutation is enabled.

Acceptance criteria

  • A story-to-test matrix contains every backlog story with no missing, skipped, or
    failing required test.
  • One fresh-environment journey runs discovery, duplicate review, safety, analysis,
    EXIF verification, album proposal, rename, rescan, upload, archive, offline
    deduplication, restore, and full process restarts.
  • Security, migration, donor parity, crash recovery, accessibility, responsive UI,
    browser console/network, fixture reproducibility, and archive safety gates pass.
  • A read-only real-library dry run produces an explicitly approved reconciliation
    report before mutation can be configured.

Automated tests

  • One documented release command provisions and destroys the full isolated stack and
    retains signed/versioned evidence.
  • Chromium passes every change; supported cross-browser and full soak suites pass for
    release; all earlier epic suites run unchanged.

Dependencies

  • US07-01 through US07-06
Source specification: [delivery_backlog/stories/US07-07-release-e2e.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US07-07-release-e2e.md) # US07-07 — Automate Full Release Acceptance Epic: [E07](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E07-hardening-release.md) As a release owner, I want one reproducible automated release gate so every user story and complete workflow is proven before real-library mutation is enabled. ## Acceptance criteria - A story-to-test matrix contains every backlog story with no missing, skipped, or failing required test. - One fresh-environment journey runs discovery, duplicate review, safety, analysis, EXIF verification, album proposal, rename, rescan, upload, archive, offline deduplication, restore, and full process restarts. - Security, migration, donor parity, crash recovery, accessibility, responsive UI, browser console/network, fixture reproducibility, and archive safety gates pass. - A read-only real-library dry run produces an explicitly approved reconciliation report before mutation can be configured. ## Automated tests - One documented release command provisions and destroys the full isolated stack and retains signed/versioned evidence. - Chromium passes every change; supported cross-browser and full soak suites pass for release; all earlier epic suites run unchanged. ## Dependencies - US07-01 through US07-06
domverse added this to the E07 — Hardening and Release milestone 2026-07-13 13:10:54 +02:00
domverse added the priority/criticaltype/testarea/backendarea/testing labels 2026-07-13 13:10:54 +02:00
domverse added a new dependency 2026-07-13 13:11:34 +02:00
#39 US07-02 — Harden API Authorization and Path Boundaries
domverse added a new dependency 2026-07-13 13:11:34 +02:00
#40 US07-03 — Harden Media and Metadata Edge Cases
domverse added a new dependency 2026-07-13 13:11:35 +02:00
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse added a new dependency 2026-07-13 13:11:35 +02:00
#42 US07-05 — Deliver Backup and Operational Recovery
domverse added a new dependency 2026-07-13 13:11:35 +02:00
#43 US07-06 — Validate Performance and Resource Bounds
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:48 +02:00
domverse added the status/backlog label 2026-07-13 13:52:57 +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/testing priority/critical status/backlog type/test
Milestone
No items
No Milestone E07 — Hardening and Release
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#38 US07-01 — Complete Donor Migration and Freeze the CLI Archive
domverse/photoanalyzer
#39 US07-02 — Harden API Authorization and Path Boundaries
domverse/photoanalyzer
#40 US07-03 — Harden Media and Metadata Edge Cases
domverse/photoanalyzer
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse/photoanalyzer
#42 US07-05 — Deliver Backup and Operational Recovery
domverse/photoanalyzer
#43 US07-06 — Validate Performance and Resource Bounds
domverse/photoanalyzer
Reference: domverse/photoanalyzer#44
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?