tinyusb.git/docs/superpowers/followup/pr3803-pci-rebind-stranding.md, branch codex/class-reference-docs Unnamed repository; edit this file 'description' to name the repository. http://cgit.235523.xyz/tinyusb.git/atom/docs/superpowers/followup/pr3803-pci-rebind-stranding.md?h=codex%2Fclass-reference-docs 2026-08-18T05:19:09Z docs: hand off follow-up work as per-PR plans 2026-08-18T05:19:09Z hathach thach@tinyusb.org 2026-08-17T12:20:32Z urn:sha1:c7290c4d3167766055f492de43f1ede83940e23c Records the convention in CLAUDE.md -- deferred work is a SEPARATE scope that deserves its own PR, written by another session, so it is handed off as a writing-plans doc in docs/superpowers/followup/pr<NNN>-<topic>.md rather than accumulated in the PR that found it. Five handoffs from #3803: flasher_recover (convoy-safe recovery for J-Link boards, seven validated on the rig), the blindness reporting gaps, the usbtest recovery reserve, the IAR re-run spec, and the pci-rebind stranding question. Each carries what is already established with its citations and measurements, what remains, and why it was split out. One doc per follow-up, not one per PR: a per-PR file invites unrelated work into the same document and rots as a unit.