feat(companion): core parity -- L1 sends via the core, shared telemetry, schema settings on L1

- L1's MessagesScreen sends through UiCore::sendDirectText / sendChannelText
  (its own copy of send + file + ACK tracking gone).
- ui-core/Telemetry.h: the dashboard fields (numbers, names, formats) and
  sensor readings as text, each frontend passing its Style; L2 Home, L1's
  clock page, lock screen, sensors page and GPS altitude use it.
- L2: the side button held in the first 8 s is the CLI rescue, as on L1.
- L1's repeater radio goes through rptctl.
- L1 Settings are built from SettingsSchema: short labels for small
  screens, SCHEMA_* placeholders expand to the schema's sections, one
  generic row (switch ON/OFF, bars for brightness / volume). 20 hand-written
  rows and their tables gone; L1 implements applyDisplayPrefs /
  applySoundPrefs. settings::text / step / indexOf shared with L2.
- Schema: auto-off gains 5 s; the advert sound scope reads "Direct".

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

docs/development/plan-next.md

@@ -89,8 +89,16 @@ for a second radio). They are L2-specific and block the loop for ~90 s.
 
 ## G. Core parity with L1 SOLO
 
-- [ ] A feature table: L1 SOLO / ui-core / L2 (ui-lvgl). What's missing goes
+- [x] A feature table: L1 SOLO / ui-core / L2 (ui-lvgl). What's missing goes
       into ui-core, not into each UI separately.
+      Done 2026-09-28: L1 sends through UiCore::sendDirectText /
+      sendChannelText; ui-core/Telemetry.h (dashboard fields, sensor
+      readings) for both; CLI rescue on L2 (side button held in the first
+      8 s); L1's repeater radio through rptctl; L1 Settings built from
+      SettingsSchema (short labels, SCHEMA_* placeholders per section; 20
+      hand-written rows gone). Kept per device: Noise measure (L2), screen
+      PIN (L2, a PR pending). Later, as settings are touched: radio switches,
+      keyboard alphabets and chat filters into the schema.
 
 ## H. Before the merge into dev