Show status messages on the display

- Clock firmware: 'Connecting to WiFi...' and 'Getting the time...' at
  boot, 'Crashed!' in the OTA-only modes, and 'No WiFi' with the time
  when WiFi is down for over a minute (new DisplayController screen)
- Recovery app: shows its reason, the setup WiFi name, or its IP address,
  then powers the display off (flipdots keep the image)
- StatusScreen and drawTextLines shared by both apps
- Driver: ESP begin() no longer draws 'ESP Connected'
- Tests: No WiFi screen, short reason texts (70 total)

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

CLAUDE.md

@@ -110,9 +110,12 @@ See README.md for the overview.
   USB only), ota_0/ota_1 = clock firmware. `esp32_usb` uploads to 0x110000
   (`board_upload.offset_address`) so it never overwrites the recovery app. Check with
   `pio run -e <env> -t envdump` (`ESP32_APP_OFFSET`) after changing upload settings.
-- The recovery app compiles `esp32/logic/boot_policy.cpp`, `esp32/system/system_store.cpp`
-  and `esp32/system/boot_target.cpp` (see its `build_src_filter`). Keep those free of
-  clock-firmware dependencies. Both apps share NVS namespace `flipdot`. RTC memory is
+- The recovery app compiles `esp32/logic/boot_policy.cpp`, `esp32/system/system_store.cpp`,
+  `esp32/system/boot_target.cpp`, `esp32/nano_link/nano_link.cpp`,
+  `esp32/display/status_screen.cpp` and `esp32/display/text.cpp` (see its
+  `build_src_filter`). Keep those free of clock-firmware dependencies.
+- Status messages (`StatusScreen`) are at most 14 characters per line, 2 lines. The
+  recovery app powers the display off after each message (flipdots keep the image). Both apps share NVS namespace `flipdot`. RTC memory is
   not shared between the apps (different layouts).
 - `rebootToRecovery()` selects the factory partition, which erases otadata. The recovery
   app later selects the clock slot again (`startMainFirmware()`), so the clock firmware