# Complete SD Qualifier Gate 2 release-plan acceptance

Status: complete
Type: campaign
Updated: 2026-08-17
Next Action: none
Campaign ID: 005-complete-sd-qualifier-gate2-release-plan-acceptance
Campaign Number: 005
Outcome: Reach a documented Gate 2 GO on one reviewed SD Qualifier release, immutable qualification plan, qualified fixtures, and the frozen firmware bundle.
Primary Focus Areas: sd-qualifier-app
Supporting Focus Areas: smi-firmware, hpt-media-logging, usb-host-publication, controller-automation, power-fault-control, qualification-release
Depends On: 004-produce-and-freeze-corrected-firmware-bundle
Decision: none
Detour For: none
Return To: none
Completion Gate: Release, plan, fixture, deployment, and bundle-admission checks pass with zero unresolved open or active Gate 2 findings.
Completion Evidence: work/evidence/campaign-005-sd-qualifier-gate2-checkpoint-20260817.md
Completion Date: 2026-08-17
Completion Order: 6
Disposition: completed

## Request Context

Priority: 4
Target: `http://srv-rpi00.local/sd-qualifier/`
Repository Coordination: local Tool Shed in `E:\dev\high_point\7520553_SMI_FW`
Coordination: coordinated
Execution Route: work2
Parent: `work/checklists/checklist-sd-card-supply-change-project-closeout.md`
Implementation Workpackage: `work/wp/active/wp-controller-neutral-sd-qualification-and-independent-a-b-execution.md`

## Goal

Complete SD Qualifier Gate 2 against the frozen corrected firmware handoff:
consolidate one reviewed application release line, integrate the governing
machine-readable contract, register the contract-complete immutable plan,
deploy the exact release, and prove it ready for clean campaign creation.

## Dependency gate

Require request `004` to provide one immutable corrected Release firmware
bundle, exact hashes, source/build identity, target evidence, known limitations,
and rollback. If any identity is missing or changes, do not code, deploy, import,
or create a campaign.

## Required work

1. Keep this local Tool Shed as the project source of truth. Access the Pi and
   its repository/runtime as implementation targets; do not create a competing
   `ts2` planning queue.
2. Capture a fresh read-only live checkpoint and a restore-verified database
   backup through the exact deployed Compose inputs. Require 11 terminal
   campaigns, zero open campaigns, and zero active operations before mutation.
3. Resolve the exact deployed worktrees, commits, overrides, image digests,
   migrations, and protected configuration identities. Consolidate the accepted
   independent-A/B, dashboard SSE, campaign-detail performance, and terminal
   closeout changes into one reviewed release line.
4. Integrate `SMI-SDQ-CONTRACT-V1` into that release line and register a new
   immutable, contract-complete `CARD_FAMILY_INITIAL` execution-plan revision
   covering permitted conclusions, A/B leaves/frontiers, budgets,
   prerequisites, evidence admission, recovery, endurance, final scrub/CID,
   aggregation, and reviewer gates.
5. Pass fixtures for pass, fail, blocked, inconclusive, pause/resume, restart,
   duplicate submission, exhausted budget, evidence reuse, independent A/B
   concurrency, final review, and no command replay. Fix every coding issue
   revealed before deployment.
6. Import/admit only the exact request `004` firmware bundle and verify all
   hashes and metadata. Do not program either controller.
7. Deploy the exact reviewed SDQ release through the protected appliance path.
   Verify migrations, health, restart/no-replay, authenticated UI,
   dashboard/detail performance, contract/plan projection, backup, rollback,
   and source/image identity.
8. Produce a Gate 2 `GO`/`NO-GO` evidence record and update local Tool Shed.
   `GO` requires every software, plan, release, deployment, and bundle-admission
   check to pass.

## Boundaries

- Do not reopen, delete, relabel, migrate, or reuse credit from historical
  campaigns.
- Do not create the clean campaign in this request; request `006` owns it.
- Do not program firmware, issue controller commands, cycle power, run
  destructive media tests, or move SD cards.
- Do not expose credentials, replace protected configuration with defaults, or
  launch Compose from a checkout that differs from live deployment metadata.

## Completion gate

Complete only on a documented Gate 2 `GO` with one reviewed SDQ release, exact
image/rollback identity, passing fixtures and live checks, one admitted frozen
firmware bundle, and zero open campaigns or active controller operations.
