# Prove USB VBUS adapter regeneration safety

Status: complete
Type: campaign
Updated: 2026-08-17
Next Action: none
Campaign ID: 008-prove-usb-vbus-adapter-regeneration-safety
Campaign Number: 008
Outcome: Close the diagnostic-only USB VBUS workpackage by proving one clean e2 regeneration and canonical rebuild preserve the user-owned adapter while vendor SSP power stubs remain unchanged, without target action or production lifecycle expansion.
Primary Focus Areas: power-fault-control
Supporting Focus Areas: smi-firmware, usb-host-publication, qualification-release
Depends On: 002-checkpoint-sd-qualification-and-tool-shed-state
Decision: none
Detour For: none
Return To: none
Completion Gate: The regeneration and canonical Debug/Release build evidence passes, the adapter survives unchanged, vendor SSP stubs match baseline, no unrelated generated churn is admitted, and the workpackage is truthfully completed.
Completion Evidence: work/evidence/usb-vbus-adapter-regeneration-safety-closeout-20260817.md
Completion Date: 2026-08-17
Completion Order: 3
Disposition: completed

## Request

Primary workpackage: `work/wp/active/wp-migrate-usb-vbus-control-out-of-ssp.md`.

Use the canonical managed e2 builder. First checkpoint unrelated work, then
perform exactly one clean regeneration and Debug/Release rebuild under the
separate authorization recorded in `Decision`. Compare the user adapter and
vendor SSP files with their admitted baselines, reject unrelated generated
churn, and perform no controller, USB-drive, or production lifecycle action.

## Completion Check

The regeneration and canonical Debug/Release build evidence passes, the adapter survives unchanged, vendor SSP stubs match baseline, no unrelated generated churn is admitted, and the workpackage is truthfully completed.
