# Produce and freeze corrected firmware bundle

Status: complete
Type: campaign
Updated: 2026-08-17
Next Action: none
Campaign ID: 004-produce-and-freeze-corrected-firmware-bundle
Campaign Number: 004
Outcome: Produce one immutable, reproducible corrected Release firmware bundle for SD Qualification handoff.
Primary Focus Areas: qualification-release
Supporting Focus Areas: smi-firmware
Depends On: 003-complete-bounded-hpt-slow-export-firmware-ticket
Decision: none
Detour For: none
Return To: none
Completion Gate: The reviewed source commit, fresh Release build and package, hashes, target evidence, and rollback manifest are recorded and frozen.
Completion Evidence: work/evidence/campaign-004-corrected-firmware-bundle-freeze-20260817.md
Completion Date: 2026-08-17
Completion Order: 5
Disposition: completed

## Request Context

Priority: 3
Target: firmware workspace `E:\dev\high_point\7520553_SMI_FW`
Coordination: guided
Parent: `work/checklists/checklist-sd-card-supply-change-project-closeout.md`
Legacy Request Dependency: `work/tickets/ticket-eliminate-full-history-scan-latency-for-bounded-hpt-customer-exports.md`

## Goal

Turn the completed slow-export correction into one immutable, reproducible
Release firmware bundle that SD Qualifier Gate 2 can admit without guessing
about source, build, profile, artifact, evidence, or rollback identity.

## Dependency gate

Require request `003` and its primary ticket to be complete with passing
Controller A/B large-history evidence and no uncommitted firmware source
changes. If the source or evidence changes during this request, return to
request `003`; do not freeze a moving candidate.

## Required work

1. Resolve and record the exact reviewed source commit, repository state,
   managed builder/toolchain identity, configuration, linker/map identity, and
   qualification profile.
2. Perform a fresh canonical managed Release rebuild and required packaging.
   Validate packaged contents and compute SHA-256 values for every admitted
   binary, manifest, map, and bundle artifact.
3. Confirm the packaged image contains the completed slow-export correction and
   the previously accepted SD/HPT/USB behavior, including the 32 KiB production
   FileX write cap. Do not make source changes in this stage.
4. Create a small versioned handoff manifest linking the exact ticket evidence,
   approved latency budget, A/B target results, build/package results, artifact
   hashes, known limitations, and rollback identity.
5. Verify the bundle is reproducible or document and explain every expected
   nondeterministic field. Store bulky output only in the ignored generated
   evidence area and keep the versioned manifest compact.
6. Do not program controllers, deploy SDQ, import/register the bundle, create a
   campaign, push, or externally release. Request `005` owns SDQ admission.

## Completion gate

Complete only when one exact corrected Release bundle and its versioned
hash-verified handoff manifest exist, the source is frozen at a reviewed commit,
rollback is explicit, and SDQ can consume the bundle without inspecting an
unidentified worktree.

## Closeout

The reviewed correction is frozen at commit
`b6aadb53fbdca20d9858bd8bb463b3b504e18284`. A fresh canonical managed Release
rebuild and two independent package runs produced byte-identical bundle
`smi-00-05-00-cae69f7c7943-75f108d5e2e7-release`. Its Release S-record SHA-256
is `75F108D5E2E77031E107B2D71852545C9FD246B128085CCB7D4F6E256BC37462`.

The versioned handoff manifest records every bundle-member hash, toolchain and
profile identity, exact A/B target evidence, focused regression results, known
limitations, and the explicit emergency rollback. No controller programming,
media move, SDQ import, deployment, push, or release occurred in this campaign.
