Build the screens with ESPHome 2026.9 and keep its build memory in the app's own storage, give the CYD 94 KB more room, and stop a timer from counting one second too many (0.2.89)

The add-on ships ESPHome 2026.9.0: it builds an ESP32 with ESP-IDF itself
and keeps a compiler cache. firmware.py gives the CLI its own storage in
/data (ESPHOME_DATA_DIR /data/esphome, which the ESPHome Device Builder no
longer wipes on start; ESP-IDF and ccache in /data/idf, at most 1 GB;
compilers limited to the core count as PlatformIO ran them), removes the
unused PlatformIO once before the first ESP-IDF build, and leaves the new
folders out of backups.

Firmware 0.2.75: assertion_level SILENT in every board's esp32 block, the
core logs from INFO, and clock_parts() in runtime_model.h replaces sscanf.
timer_left() caps a running timer at its duration (the screen's clock runs
up to a second behind Home Assistant's). The packages keep min_version
2026.6.2, the top-level online_image and OTA passwords for new screens, so
an add-on or Device Builder that isn't updated yet keeps building every
screen; CI now builds both boards with the add-on's ESPHome and with
min_version. ESP-IDF's error names stay on, and build_flags stay under
platformio_options, because ESPHome 2026.9's LVGL reads only those.

tools/check.sh: 478 Python tests, 19/19 C++, editor; --firmware PASS with
ESPHome 2026.6.2 (CYD 87.7 %), 2026.8.1 (88.3 %) and 2026.9.0 (86.4 %,
was 91.5 %). Both bench screens OTA'd and watched for half an hour;
ESP Screens as a local add-on on the Yellow built both profiles
(CYD 1,037 s first build, 41 s unchanged). Details:
docs/TEST_RESULTS_0289.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

packages/boards/cyd-2432s028.yaml

@@ -386,6 +386,11 @@ esp32:
   framework:
     type: esp-idf
     advanced:
+      # ESP-IDF's assert texts (file, line and condition of every check) stay out of the firmware (0.2.75+), 49 KB on
+      # the CYD: a failed assert still stops and restarts the screen, and its backtrace still points at the line.
+      # Every board sets it (tests/test_easy_package.py). ESP-IDF's error names stay: without them ESPHome's own
+      # error lines only say "UNKNOWN ERROR".
+      assertion_level: SILENT
       # ESPHome recommends this itself in the boot log. Yields ~40KB extra IRAM
       # and a smaller binary, and every KB counts on this board.
       sram1_as_iram: true
@@ -554,7 +559,9 @@ script:
   - id: ui_self_test
     mode: single
     then:
-      - logger.log: "UI_TEST START: page/overlay render stress, no HA actions"
+      - logger.log:
+          format: "UI_TEST START: page/overlay render stress, no HA actions"
+          level: INFO  # the core logs from INFO; logger.log is DEBUG by default
       - lambda: 'ESP_LOGI("ui_test", "Light sliders: %s", light_controls::self_test() ? "PASS" : "FAIL");'
       - lambda: 'id(calibration_active) = false;'
       - lvgl.page.show: home_page
@@ -610,7 +617,9 @@ script:
             - delay: 150ms
             - lvgl.widget.hide: alert_overlay
       - lambda: 'if (!id(ui_refresh).is_running()) id(ui_refresh).execute();'
-      - logger.log: "UI_TEST COMPLETE"
+      - logger.log:
+          format: "UI_TEST COMPLETE"
+          level: INFO
 
   # The two scripts that drive the backlight as a light action; the Guition drives it through its set_backlight script.
   - id: alert_dismiss