title: Docker release upgrade user journey

scenario:
  id: docker-release-upgrade-user-journey
  surface: docker-podman-hosting
  category: docker-podman-hosting.image-release-and-validation
  coverage:
    primary:
      - docker.release-workflow
      - docker.release-path-install
  objective: Verify a published baseline can be configured, upgraded to the candidate tarball, and still complete the core release journey.
  successCriteria:
    - A published baseline installs and is configured with mock provider, plugin, and ClickClack channel state.
    - The candidate package replaces the baseline package.
    - The upgraded install still passes agent, plugin CLI, channel status, outbound message, Gateway, and inbound reply checks.
  docsRefs:
    - docs/help/testing.md
    - docs/help/testing-updates-plugins.md
    - docs/concepts/qa-e2e-automation.md
  codeRefs:
    - scripts/e2e/release-upgrade-user-journey-docker.sh
    - scripts/e2e/lib/release-upgrade-user-journey/scenario.sh
    - scripts/e2e/lib/release-user-journey/assertions.mjs
  execution:
    kind: script
    path: test/e2e/qa-lab/runtime/docker-e2e-lane.ts
    summary: Runs the existing release-upgrade-user-journey Docker E2E lane and records QA Lab evidence for release-path upgrade coverage.
    args:
      - --lane
      - release-upgrade-user-journey