ef755bac81
The read-only-attribute theory (and the predicted AM_RDO unlink shim) was wrong. A diagnostic recursive walk showed every entry writable (ro=false) and succeeded via path-based deletion, so the real blocker was std::fs::remove_dir_all's openat/unlinkat/fdopendir usage against esp-idf's path-based FATFS VFS. Update the increment-A/B checklist accordingly.
Postmortems
Bench + bring-up debugging write-ups: what broke, how we found the root cause, and the decisions that came out of it. One file per incident, named
YYYY-MM-DD-<slug>.md. These capture why a spike stalled or a design turned — the kind of context that's expensive to reconstruct later.Project overview:
../../README.md. Bring-up spikes:../v0.1-mvp-technical.md.
| Date | Incident | Status |
|---|---|---|
| 2026-07-05 | Spike 3 (SD) — card rejects CMD59 (SPI-mode CRC) | Paused — awaiting a compliant microSD; wiring + firmware proven |
| 2026-07-05 | Spike 7 (git push) — ADR-004 kill-switch fired: gix can't push over HTTPS | Turned — pivoted to libgit2; git mechanics proven on desktop, device build next |