dangernoodle-io / breadboard / 30866896656

97%

push

github

feat: wire TELEM wide-routing gate into s_log_vprintf (#1216)

Wires the B1-831 PR-2 decision core into bb_log's s_log_vprintf call
site: a TELEM-tagged log line now stays console-only in the default
config (CONFIG_BB_LOG_TELEM_ROUTE_EVENTS=n), skipping the ring, the
bb_log_event forwarder queue (the live GET /api/events?topic=log
consumer), and the optional UDP mirror. Console output is unaffected.

- bb_log_telem_should_route_wide(): the single function the call site
  and host tests both exercise, parsing just the tag out of the
  formatted line before deferring to bb_log_telem_route_wide().
- bb_log_telem_route_set()/route_get(): runtime override for the
  boot-time CONFIG_BB_LOG_TELEM_ROUTE_EVENTS default. No production
  consumer calls the setter yet; it is reachable only from host tests
  today, and the doc comments/Kconfig help now say so plainly instead
  of overclaiming a wired runtime flip.
- The call site carries its own #if CONFIG_BB_LOG_TELEM_ROUTING guard,
  matching the CMake SRCS gate, so disabling the knob still links
  (falls back to unconditional wide routing).
- The UDP mirror send (step 5) is now gated by the same route_wide
  decision as the ring and forwarder queue, closing a leak where a
  TELEM line stayed off the ring/forwarder but still went out over the
  network unconditionally with CONFIG_BB_LOG_UDP_SINK=y. bb_log.c is
  ESP_PLATFORM-only (s_log_vprintf never compiles on host), so this
  specific gate cannot be host-test-covered directly; verified instead
  by a build-time positive/negative symbol check plus a manual mutant
  test showing the host suite does not catch a regression here.
- BB_LOG_TELEM_TAG (Kconfig) is unbounded but the parse buffer is a
  fixed 48-byte cap; a build-time _Static_assert in
  bb_log_telem_route.c now fails loudly on an over-long configured tag
  instead of silently truncating and going permanently inert at
  runtime.

B1-831 PR-3.


Claude-Session: https://claude.ai/code/session_0119nuE2NZM... (continued)

8296 of 8858 branches covered (93.66%)

Branch coverage included in aggregate %.

8 of 8 new or added lines in 1 file covered. (100.0%)

14032 of 14187 relevant lines covered (98.91%)

2658.75 hits per line