dangernoodle-io / breadboard / 29223424946

95%

push

github

fix: compile bb_fsm/bb_lifecycle/bb_tcp_client under the ESP-IDF toolchain in CI (#843)

- add bb_fsm, bb_lifecycle, bb_tcp_client to [capability.smoke].components (link-proof-only, same shape as bb_wifi_ap/bb_bqueue -- no // bbtool:init marker, nothing wires an instance at smoke app-init time)
- all three previously lived only in [capability.core] (host scaffold), so they had NEVER been compiled by the ESP-IDF toolchain -- a different compiler, arch, and warning set than host gcc
- bb_tcp_client has a real espidf backend (platform/espidf/bb_tcp_client/bb_tcp_client.c); bb_fsm and bb_lifecycle are portable single-TU components with no platform/espidf/ directory at all, but still benefit from proving the ESP-IDF toolchain compiles them cleanly
- TaipanMiner's rebuild sits on all three (stratum FSM, stratum transport, mining run-state), so a latent compile break here would land squarely on TM
- verified: clean rebuild of examples/smoke on esp32 (Xtensa) and esp32c3 (RISC-V) compiles all three TUs cleanly with zero warnings/errors


Claude-Session: https://claude.ai/code/session_01WcT1TPAV2UE4VeGuDL7K8p

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

4075 of 4075 branches covered (100.0%)

Branch coverage included in aggregate %.

6611 of 6611 relevant lines covered (100.0%)

7904.1 hits per line