v0.4.2-beta.6

[Unreleased]

Fixed

• Clock text and icon colour didn't follow the theme. The stock Clock
  view picks its font/icon colour via a button-card JS template
  (var_font_color/var_font_color_night) that hardcodes a literal
  return "white" - a colour hidden inside JS, not a plain YAML
  - color: white line, so the existing colour patterns never saw it. Its
  own red/transparent night-mode indicators are deliberate and left
  alone; only the literal white return value is replaced. The same
  js_hardcoded_white() pass applies to every view, not just Clock, and
  was added to both dashboard_converter.py and
  examples/view-assist/convert.py.

Reverted

• The previous beta's Weather-view layout fix (height: 100vdh /
  padding: -10% correction) made the clipped-icon problem worse rather
  than better - blind CSS layout guesses without a way to see the actual
  render aren't a good trade against a pre-existing, out-of-scope View
  Assist bug. Reverted to leaving those two declarations exactly as
  upstream ships them.

• A leftover chromhasettings.yaml example view cloned in as a second,
  broken "Theme" tab. Before the automatic dashboard existed,
  examples/view-assist/README.md told people to copy
  chromhaclock/chromhacontrols/chromhasettings into
  /config/view_assist/views/ by hand. Anyone who did still has them there,
  and the dashboard clone had no way to know they were obsolete - so
  chromhasettings.yaml's hardcoded example profile (chromha_ryan) cloned
  in as a tab confusingly also titled "Theme", pointing the ChromHA card at
  an accent entity that only exists if your profile happens to be named
  "ryan". These three legacy views are now skipped during cloning (with a
  warning naming the file to delete), and the README no longer recommends
  installing them.

Changed

• The ChromHA View Assist dashboard is now a clone of your actual View
  Assist dashboard, not a hand-built substitute. 0.4.0/0.4.1 generated
  original Home/Weather/Controls views from scratch, gated behind a Push
  to View Assist target per profile - a mismatch with what people actually
  wanted, which was their real View Assist dashboard with ChromHA's colours.

  It now reads every view file under /config/view_assist/views/ plus the
  dashboard's shared button_card_templates, and colour-patches both with
  the same substitutions examples/view-assist/convert.py already applies
  to a user's own copy - just automatic, and into a separate dashboard
  instead of View Assist's own. A Theme view (colour wheel + Solid/Glass
  per profile) is appended. The dashboard is now rewritten on every rebuild
  (previously created once and left alone) so it tracks your real View
  Assist setup as it changes - the same "generated, don't hand-edit"
  contract the theme file already has. New module: dashboard_converter.py.

Fixed

• The colour picker didn't always stick. chromha-card.js fired an
  unserialised text.set_value call on every colour change. Two picks made
  in quick succession (a very ordinary way to use a colour wheel) raced:
  nothing guaranteed the first call's write couldn't land after the
  second's, silently reverting to an earlier colour depending on timing.
  Commits are now serialised - never more than one write in flight, always
  sending only the latest value - which makes that reordering impossible
  rather than just unlikely.

• A stale, wrapped View Assist view file produced an invalid card. If a
  file under /config/view_assist/views/ was copied in the wrapped
  views:/cards: shape instead of a bare button-card - as ChromHA's own
  example views did before 0.4.0 - the dashboard clone wrapped it a second
  time, producing a card with no type (a broken card in the UI). Detected
  and unwrapped automatically now, with a warning logged pointing at which
  file is still in the wrong shape on disk.

• Dynamic view titles rendered as literal garbage. A Lovelace view's own
  title: is never template-evaluated - only a button-card's own config is

  • so a view whose title was a [[[ ... ]]] expression (View Assist's
    stock locate and music views both do this) showed that literal text in
    the tab bar instead of anything useful. The generated dashboard now
    rejects a templated title and falls back to a plain name derived from the
    view's own filename - a ChromHA-dashboard-only substitution; the source
    view file is untouched.

• Weather's background was still blue after conversion. Not a simple
  background-color: line - View Assist's stock Weather view sets it via
  card_mod CSS text (ha-card { background: #059bf9 }), which the colour
  patcher's structural patterns never looked inside. That exact colour is
  the Alert view's own deliberate blue, reused here seemingly by copy-paste;
  now patched to the theme background everywhere except the Alert view
  itself, in both dashboard_converter.py and examples/view-assist/convert.py.