# US08-05 — Automate Container Deployment Acceptance

Epic: [E08](../E08-container-deployment.md)

As a release owner, I want one automated gate that proves the deployed container, so the
packaged application is verified the same way the host application is.

## Acceptance criteria

- One documented command provisions the composition from the built image against a
  temporary fixture library and an isolated data volume, and destroys it afterwards.
- A browser journey against the containerized application covers discovery, duplicate
  review, analysis, album proposal, rename, upload preflight, and archive views.
- An upgrade journey runs the previous published image, then the new one, and asserts
  migrations, journals, jobs, and the thumbnail cache survive.
- A restart journey kills both containers mid-job and asserts resume without duplicate
  side effects.
- Security gates run against the deployed instance: unauthenticated access refused,
  forged forwarded headers refused, paths outside the mounted library roots refused, and
  no secret in container logs.
- Evidence is retained per run and the gate fails on any skipped required check.

## Automated tests

- The container acceptance suite runs on a `phase_h` marker in CI on `main` and before a
  published deploy; earlier epic suites keep running unchanged.

## Dependencies

- US08-01 through US08-04