App 2.14.0: accent colour after the MG4 paints; car colour probe

The accent is selectable in Settings → Display: Dynamic Red (default),
Volcano Orange, Holborn Blue, Racing Green, Camden Grey, Monument
Silver, Arctic White and Black Pearl. White, silver and black cannot be
an accent on the black screen as they are, so they become light greys
and a pearl blue-grey.

The accent palette is now theme attributes (attrs_accent.xml) with one
overlay per paint (accents.xml), applied before the activity inflates;
layouts, colour lists, drawables and the views that draw in code use
them, including the red tints that were hard-coded. A change recreates
the activity on the same page. Android 9 crashes on gradients with
theme colours, so the battery card is built from layers.

Logs → "Look for the car colour" lists the head unit's system
properties that mention colour, paint or car model, to find out whether
the paint colour can be read from the car.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki

AGENTS.md

@@ -8,7 +8,9 @@ workspace `DESIGN.md` apply; this file contains only telemetry-specific addition
 ## App-specific visual direction (2.2.6)
 
 The user explicitly requested a permanent OLED-black theme, charcoal glass-like cards,
-MG red accents (#E0424C, with a light #FF9A9E and a deep #3A1215 variant; they replaced the earlier muted gold and cyan). These app resources intentionally override the shared
+an accent the user picks from the MG4 paint colours (Dynamic Red #E0424C by default; the palette
+is theme attributes in `res/values/attrs_accent.xml` and `accents.xml` — use `?attr/evAccent…`,
+never a hard-coded accent hex). These app resources intentionally override the shared
 DESIGN.md palette, DayNight preference and flat-surface rules. Do not overwrite them
 with the shared token generator. Use static gradients rather than continuous effects;
 keep large touch targets, readable text and null telemetry shown as a dash.