OT-14 stale driver-status contrast
The actual composed Hosts controls fixture reproduced9of9 sampled stale text pairs below4.5:1 (minimum2.0945). Before measurement includes the three opacity groups: header status, per-node health body and per-target resilience row. Approved semantic inks became pale after their parent’s50% opacity blended them with the white panel.
Removed only these three opacity styles and updated one explanatory comment. Explicit health/resilience stale chips remain, as do the existing30-second local-receive health and15-second published resilience age boundaries. No health/resilience mapping, event subscription, command, authorization, timer, helper or public parameter changed. source-boundaries.json confirms the entire @code section is identical except that comment.
The actual after measurement passes9of9 pairs, minimum5.554998. contrast.py measures computed text/background colors and composes observed ancestor opacity groups over their opaque underlay; before.json/after.json retain every pair and group. Both screenshots use the actual Chromium surface through CDP (fromSurface=true,captureBeyondViewport=false), avoiding the known Playwright real-zoom framing artifact. This bounded measurement concerns this actual supported light composition, not every possible host/theme.
Both fixture Release builds have zero warnings/errors. Existing focused state/store/operation/diagnostic/Hosts parent suites pass58/58 with0skips (tests.log and ot14-stale-panel.trx). No new CSS-string test was introduced. The earlier full parent keyboard/phone/real200 matrix remains in ../../ot13-host-controls; this narrow style-only batch does not claim to rerun that entire matrix.
The checked-in Hosts synthetic fixture now seeds an additional old resilience sample, so breaker/failure/in-flight/stale combinations are observable. Its local health receive clock naturally passes30seconds before measurements; no production clock or source age boundary was altered. Commands are synthetic and this run uses Reader. Test execution used the owned private SQL environment runner; the browser fixture uses local in-memory services and no real device, broker or SQL.
Owned loopback18142 was stopped after both runs; cleanup.json confirms no listener. VoiceOver tests are excluded by user instruction.