Bring the guides up to date with the code of the last releases (docs only)

README_EXTENDED rendered everything from "Direct control" to "Override YAML" as raw text on
GitHub since 0.2.74: the full-page pictures ended without a blank line. It also gains the
media card, Page buttons, the ··· menu's Identify/Copy/Export/Import, Try it, and where
SCREEN_FIRMWARE_VERSION lives now. EASY_SETUP's settings table drops Show clock and gets
Back to page 1; SETTINGS.md points at web/src/store.ts and packages/core.yaml; GUITION.md
had the GT911 mirrored and cache settings that left the profile on 2026-09-12;
TROUBLESHOOTING still named TILE_COUNT and files deleted in 0.2.50; CALIBRATING put
Calibrate touch in ESP Screens instead of Home Assistant. RELEASING gets the compatibility
notes of 0.2.73 to 0.2.85 and the GitHub release step.

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

docs/CALIBRATING.md

@@ -17,7 +17,8 @@ panel, a loose connection, unstable power, or random outliers.
 
 ```yaml
 packages:
-  display: ...        # what ESP Screens put there
+  display: ...                                   # what ESP Screens put there
+  local_overrides: !include kitchen.local.yaml   # idem
   calibration: !include calibration.yaml
 ```
 2. Check the data cable and the USB port with `python -m serial.tools.list_ports`.
@@ -122,8 +123,9 @@ No `-s CALIBRATION_ON_BOOT true` is given here; the profile keeps it `false`.
 Then check the real thing: the tiles, the navigation and a few taps in the corners.
 
 Most screens never need this. A CYD shows its calibration on the screen itself when
-it first starts, and ESP Screens has **Calibrate touch** for a repeat. This USB route
-is for a panel that stays off after that, or for a measurement report.
+it first starts, and its **Calibrate touch** button in Home Assistant (on the screen's
+ESPHome device) starts it again. This USB route is for a panel that stays off after that,
+or for a measurement report.
 
 If calibration mode was opened only via the API, you can close it: