Release 0.11.0: board info and the flash partition table

[Zenofex]

Version bump, lockfile, changelog. No code changes: everything here is on main and was reviewed in #27.

What ships

  4 partitions on nor0
    u-boot           0x00020000 @ 0x00000000  read-only
    kernel           0x00100000 @ 0x00020000
    rootfs           0x006c0000 @ 0x00120000
    art              0x00010000 @ 0x007f0000  read-only

bdinfo and the mtdparts table, with the mask_flags read-only marker — the column that says which partitions an operator at that prompt can rewrite.

Both parsers were dead code before #27: across all 31 public corpus logs they produced nothing, while two of those logs carry a full bdinfo dump. Both were gated on the prompt regex matching the line where the command was typed, and Boot-> bdinfo is not U-Boot's default prompt.

Why MINOR

New output. No flag renamed or removed, no exit-code policy change, no output-format schema broken.

Verification

• cargo test --workspace: 369 passed, 0 failed
• clippy --workspace --all-targets -- -D warnings and fmt --all --check: clean
• cargo build --release then bootintel --version reports bootintel 0.11.0
• Nine fixtures in the shared expectation, eight of them real captures, reproduced byte for byte by both implementations

Both version bumps landed first try — fourth release running for docs/releasing.md step 1, which exists because the bootintel-detectors pin is not derived by cargo.

After merge: dispatch cli-release for 0.11.0 with publish_crates, verify the draft against SHA256SUMS, publish and mark latest, then move the tap (step 7) and sync the in-repo reference copy.

🤖 Generated with Claude Code