enricobuehlerandClaude Opus 5 f66de3eba4 fix(web): close the last two high-severity items from the closeout audit ...

**The streamed-screen pin could still be clobbered by three other write paths.**
Deferring it to the server's value on Save fixed the reported sequence but not
the general case: the draft is only re-seeded while it is CLEAN, so once there is
an unsaved edit its `capture_monitor` is frozen at whatever it was before the
operator used the picker — and `applyAxis` (which spreads the last saved policy),
the built-in preset switch and the custom-preset apply all put that stale value
back. Every write path reads `serverCaptureMonitor()` now; no path spreads the
draft's copy.

**The session⇄game grace input had no accessible name.** That card has its own
`Field` and only DisplayCard's was fixed, so the number input was still announced
as an unnamed spin button. Same treatment: `htmlFor`/`id` for the single control,
`fieldset`/`legend` for the two button groups. Verified in a browser — zero
inputs without an accessible name across the Displays page.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-01 00:20:10 +02:00

..

DisplayCard.tsx

fix(web): close the last two high-severity items from the closeout audit

2026-08-01 00:20:10 +02:00

index.tsx

feat: the streamed screen is a persisted setting, pickable from the console

2026-07-27 23:51:41 +02:00

MonitorCard.tsx

fix(web): the logs come back after a host restart, and eight more that quietly lied

2026-08-01 00:20:10 +02:00

SessionGameCard.tsx

fix(web): close the last two high-severity items from the closeout audit

2026-08-01 00:20:10 +02:00