Issues

• F-44: Threading-model task table drift

  bazauto/esp-layout-controller#47 · Filter by author bazauto opened on Sep 25, 2026

• F-43: CI hardening

  bazauto/esp-layout-controller#46 · Filter by author bazauto opened on Sep 25, 2026

• F-42: Protocol hygiene odds and ends

  bazauto/esp-layout-controller#45 · Filter by author bazauto opened on Sep 25, 2026

• F-41: Seesaw encoder read timing loses rotation

  bazauto/esp-layout-controller#44 · Filter by author bazauto opened on Sep 25, 2026

• F-40: WiFi credentials saved before they work; set_config error reboots the device

  bazauto/esp-layout-controller#43 · Filter by author bazauto opened on Sep 25, 2026

• F-39: NVS writes on the LVGL task

  bazauto/esp-layout-controller#42 · Filter by author bazauto opened on Sep 25, 2026

• F-38: Hot-path logging and repaint cost

  bazauto/esp-layout-controller#41 · Filter by author bazauto opened on Sep 25, 2026

• F-37: WiThrottle throttle updates unvalidated

  bazauto/esp-layout-controller#40 · Filter by author bazauto opened on Sep 25, 2026

• F-36: Operator credential and session cookie travel in cleartext

  bazauto/esp-layout-controller#39 · Filter by author bazauto opened on Sep 25, 2026

• F-35: Orchestrator roster refused above ~35 locos

  bazauto/esp-layout-controller#38 · Filter by author bazauto opened on Sep 25, 2026

• F-34: JMRI config screen connect/disconnect faults

  bazauto/esp-layout-controller#37 · Filter by author bazauto opened on Sep 25, 2026

• F-33: Task stack headroom unmeasured

  bazauto/esp-layout-controller#36 · Filter by author bazauto opened on Sep 25, 2026

• F-32: Main screen LVGL tree leaks on every return to it

  bazauto/esp-layout-controller#35 · Filter by author bazauto opened on Sep 25, 2026

• F-31: JMRI heartbeat task deleted from outside, possibly mid-send

  bazauto/esp-layout-controller#34 · Filter by author bazauto opened on Sep 25, 2026

• F-30: Transport callback slots unsynchronised and clobbered by the UI

  bazauto/esp-layout-controller#33 · Filter by author bazauto opened on Sep 25, 2026

• F-29: Documented lock order is the reverse of what the code does

  bazauto/esp-layout-controller#32 · Filter by author bazauto opened on Sep 25, 2026

• F-28: Every function is momentary under the orchestrator transport

  bazauto/esp-layout-controller#31 · Filter by author bazauto opened on Sep 25, 2026

• F-27: No emergency stop; track power button turns power on when the state is unknown

  bazauto/esp-layout-controller#30 · Filter by author bazauto opened on Sep 25, 2026

• F-26: OrchestratorClient::m_client destroyed under a concurrent sender

  bazauto/esp-layout-controller#29 · Filter by author bazauto opened on Sep 25, 2026

• F-25: Physical knobs not gated on the link; optimistic update outlives a failed send

  bazauto/esp-layout-controller#28 · Filter by author bazauto opened on Sep 25, 2026

• F-24: No automatic recovery after a WiFi, orchestrator or JMRI outage

  bazauto/esp-layout-controller#27 · Filter by author bazauto opened on Sep 25, 2026

• F-23: WiThrottle heartbeat (JMRI dead-man stop) never armed

  bazauto/esp-layout-controller#26 · Filter by author bazauto opened on Sep 25, 2026

• F-22: WiThrottle reconnect leaks a socket and silently loses the session

  bazauto/esp-layout-controller#25 · Filter by author bazauto opened on Sep 25, 2026

• F-21: Use-after-free when returning to the main screen

  bazauto/esp-layout-controller#24 · Filter by author bazauto opened on Sep 25, 2026

• F-20: Orchestrator: taking over a moving loco starts from speed 0

  bazauto/esp-layout-controller#23 · Filter by author bazauto opened on Sep 25, 2026