## Summary
## Linked issues
## Affected areas
- [ ] detect / SFDP parsing
- [ ] catalog (chip names / manufacturers / fallback table)
- [ ] erase
- [ ] program
- [ ] verify
- [ ] read
- [ ] protect / reset
- [ ] doctor / test
- [ ] CLI (flags, argument parsing, output)
- [ ] transport (Pico de Gallo bridge)
- [ ] documentation (README, HARDWARE-DEBUG, rustdoc)
- [ ] CI / tooling
## Testing performed
- [ ] `cargo fmt --check`
- [ ] `cargo clippy --all-targets --locked -- -D warnings`
- [ ] `cargo test --locked`
- [ ] Tested on real hardware — which Pico de Gallo (rev + firmware) and which
flash chip? Paste the relevant `detect` / `info` / `verify` output below.
- [ ] Not tested on hardware — and here is why that is safe / not applicable:
## Documentation
- [ ] README / `HARDWARE-DEBUG.md` / rustdoc updated to match this change.
- [ ] No user-visible behavior changed; no docs needed.
## Checklist
- [ ] Commits follow Conventional Commits with a correct scope.
- [ ] `Cargo.lock` is committed alongside any `Cargo.toml` change; I ran with `--locked`.
- [ ] New public items have rustdoc.