design: the code-set state colours now agree with the standard

Last inconsistency from the sweep: several VM-side state colours are still literals, and after
the palette moved they disagreed with everything around them — the top bar's LIVE state would
have painted the retired pink-red while the tile beside it used the standard red.

Values aligned (tokenisation of these sites is its own unit — they are strings bound to
Background/Foreground, so the fix is a VM->Brush refactor, not a find/replace):
- live / on-air / recorder dot: #e94560 -> #ff5451 (the standard red)
- error banner: #8f1f1f -> #93000a (error-container)
- audio meter bands follow the doc's stated thresholds: nominal cyan #38bdf8, caution amber
  #ffb95f, peak #ff5451 — they were green/yellow/red, which contradicted DESIGN.md's own table

GameMeterHonestyTests pinned the old band colours; its intent (the meter scales by volume) is
unchanged, so the two colour expectations now name the new bands.
This commit is contained in:
2026-10-30 08:30:33 -07:00
parent 8502c1d194
commit c885bbd782
4 changed files with 14 additions and 14 deletions
+2 -2
View File
@@ -48,14 +48,14 @@ public sealed class GameMeterHonestyTests
vm.GameAudioVolume = 1.0;
vm.GameAudioLevel = 1.0;
Assert.True(vm.GameMeterFillWidth > 230, "unity volume must keep the meter hot");
Assert.Equal("#ef4444", vm.GameMeterBrush);
Assert.Equal("#ff5451", vm.GameMeterBrush); // DESIGN.md: peak band
// Drop the knob to 20% — the captured level does NOT change (the OS
// tap is pre-endpoint-volume); the meter must scale it anyway.
vm.GameAudioVolume = 0.2;
vm.GameAudioLevel = 1.0;
Assert.InRange(vm.GameMeterFillWidth, 40, 80);
Assert.Equal("#22c55e", vm.GameMeterBrush);
Assert.Equal("#38bdf8", vm.GameMeterBrush); // DESIGN.md: nominal band
// And the push really reached the (faked) endpoint — one knob, honest.
Assert.Contains(0.2, pushed);