ESP32 CSI firmware README has inconsistent flash offset and provisioning path

[Fewmanism]

While preparing a real ESP32-S3 bring-up from a fresh clone, I found two documentation inconsistencies in firmware/esp32-csi-node/README.md:

1. Quick Start / Flashing sections show app flashed at 0x10000:

0x10000 firmware/esp32-csi-node/build/esp32-csi-node.bin

But the repo partition tables define ota_0 at 0x20000:

partitions_display.csv: ota_0 app ota_0 0x20000 ...
partitions_4mb.csv:     ota_0 app ota_0 0x20000 ...

The QEMU section also uses 0x20000. The release binaries also include ota_data_initial.bin, suggesting the manual flash command should likely flash app at 0x20000 and include OTA data at 0xf000.

2. Quick Start says:

python scripts/provision.py ...

but the file in this repo is:

firmware/esp32-csi-node/provision.py

These mismatches make first hardware bring-up easy to misflash or fail from the documented commands.

[ruvnet]

Thanks @Fewmanism — both inconsistencies fixed in #562.

1. Flash offset 0x10000 → 0x20000 in both occurrences (matches partitions_display.csv / partitions_4mb.csv which put ota_0 at 0x20000). Also added the missing 0xf000 ota_data_initial.bin line — release bundles ship this binary and without it the bootloader can refuse to boot after a factory wipe.
2. scripts/provision.py → firmware/esp32-csi-node/provision.py. There are actually two provision.py files in the repo right now (a stale 275-line copy in scripts/ and the canonical 348-line one in firmware/esp32-csi-node/ that has the provision.py: esptool v5 incompat + NVS partition wipes existing keys when partial update #391 full-replace semantics fix); README now points at the canonical one. The stale duplicate is a separate cleanup.

🤖 Generated with claude-flow