mirror of
https://github.com/ruvnet/RuView.git
synced 2026-10-18 21:00:22 -05:00
Mathew Beaneandclaude-flow
a4f80e63a2
Records the decision behind the two preceding firmware commits: why an OTA'd image has to confirm itself, the health signals (STA IP plus one CSI frame accepted by the stream sender), the 30 s minimum uptime and 120 s deadline, the FORCE_FAIL test hook, ota_state in /ota/status, and the httpd stack sizing. MEASURED 2026-09-29: - ESP32-S3 (16 MB, rollback bootloader): OTA push to ota_1, HTTP 200; "httpd stack after POST /ota: 4900 of 8192 bytes never used"; pending_verify then valid; still valid on ota_1 after a hard reset. A FORCE_FAIL build pushed to ota_0 rolled back to ota_1 after ~30 s. - ESP32-C6 (4 MB layout, rollback bootloader): push to ota_1, HTTP 200; pending_verify then valid ~28 s later; still valid after a hard reset. Not yet verified: the 120 s no-IP timeout path, a true power cycle (an RTS hard reset was used), and forced rollback on the C6. Numbered 379: main has up to ADR-378 and open PRs claim nothing higher (2026-10-02). Co-Authored-By: claude-flow <ruv@ruv.net>