# Checklist: USB BOT representative delta regression

Status: complete
Type: checklist
Updated: 2026-08-01
Next Action: none; retain the promoted baseline and reopen architecture review for any newer contradictory incident
Parent: work/wp/completed/wp-restore-broad-usb-compatibility-baseline.md

## Goal

Prove the isolated BOT CSW-validation delta does not regress the established
representative device class while minimizing repeat work: one fresh mount/read
observation on the second controller plus one fresh mount/read observation for
each remaining representative specimen on Controller B. Preserve the prior
complete write/publication matrix as predecessor evidence.

## Checklist

- [x] Freeze and deploy the exact Release candidate to Controller B.
- [x] Pass `USB03_32G` first-insertion mount, WAV load/playback, zero-error
  attached state, ordinary removal, and independent unmounted Pi/FAT checks on
  Controller B.
- [x] Verify Controller A has no USB drive attached and its SD CID,
  representative-sector, HPT-ready, hardware, and zero-error baseline passes.
- [x] Deploy exact Release S-record
  `6907F88FB91D5DC58EBF15A918C3993FDE3A076AFAE9DAEFB099899F55932581`
  to Controller A; capture an independent full 4 MiB readback and post-reboot
  no-drive state.
- [x] `USB03_32G` / Controller A: first-insertion configured/high-speed mount,
  acceptance mask `15`, WAV load, final zero-error attached state, ordinary
  removal, and unmounted Pi/FAT closeout.
- [x] `USB01_2G` / Controller B: same bounded mount/read/removal/Pi gate.
- [x] `USB05_4G` / Controller B: same bounded mount/read/removal/Pi gate.
- [x] `USB02_8G` / Controller B: same bounded mount/read/removal/Pi gate,
  preserving its documented pre-existing filesystem condition unless the
  owner separately authorizes repair.
- [x] Confirm no drive required reseating. If a first insertion fails below
  class, preserve the exact state before any retry and reopen architecture
  disposition rather than adding a specimen mitigation.
- [x] Confirm the final controller states have no USB attached, unchanged SD
  identity/readiness, and zero USBX/application/system errors.
- [x] Record a small versioned evidence summary; refresh the work index and
  current workpackage/map state.

## Runtime Closeout

Use this section only when the checklist changes a running system, scheduler, service, or external status surface.

- [x] Both controllers run the exact frozen BOT candidate.
- [x] Each bounded observation ends in a valid mounted session and zero errors.
- [x] Both controllers finish with no USB attached and valid SD/HPT state.
- [x] Rollback/reference baseline is commit `8c2ea719`; BOT source candidate is
  commit `ca6f573a`.
- [x] Raw captures remain under ignored generated-evidence paths; no local
  configuration is changed.

## Verification

Use `script/invoke-usb-workflow-qualification.ps1` for serial-bound state,
workflow, flash, CID, and error captures. Use unmounted, non-correcting Pi
filesystem/FAT checks after each specimen. No destructive media operation,
controller-driven VBUS action, optional SCSI lifecycle, or specimen-specific
production behavior is authorized.
