Let Wake only light the screen, and open ESP Screens without a chosen screen (0.2.65)

Wake from Home Assistant counted as a tap: it reset last_touch_ms, the one
clock that standby and Back to page 1 both read. An automation pressing Wake
on every motion therefore held an open card or page 2 up for as long as
someone moved in the room. Back to page 1 now has its own clock, last_use_ms,
written only by the boot, the touchscreen triggers, open_settings from Home
Assistant and the UI self test. Wake, an alert ending and Auto standby on
still restart the standby time, and Wake still brings back the brightness and
the second hand.

The rule moved from the interval into the script back_to_page_1_when_due.
Wake runs it right after waking a dimmed screen, so a page whose time ran out
during standby lights up on page 1 instead of jumping there a second later.

ESP Screens no longer opens the first screen by itself. Until one is picked
the page says "Choose a screen", and with no screens it still offers the
install; both cards start hidden so neither flashes while the page loads.

Checked with 48 host API checks per board, both ESP32 builds, 314 Python and
16 C++ tests, and the editor on the demo home. Firmware 0.2.56.

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

screen_manager/DOCS.md

@@ -35,5 +35,6 @@ about a second and a half, or put the built-in **Settings** card on a page. What
 there appears here within a second, and the other way around.
 
 In Home Assistant every screen also has a **Wake** and a **Sleep** button (firmware 0.2.45 or
-newer). Press them from an automation with `button.press`: Wake does what a tap does, Sleep puts
-the screen in standby right away, also with Auto standby off.
+newer). Press them from an automation with `button.press`: Wake lights the screen up and restarts the
+standby time, Sleep puts the screen in standby right away, also with Auto standby off. Wake is not a
+touch, so an open card or a later page still goes back to page 1 on time (firmware 0.2.56 or newer).