Signage

Moved from a group that was playing to one with nothing to show, a
display adopted the new assignment but kept the old group's last image
on screen indefinitely. With nothing renderable, the controller keeps
whatever frame is up, which is right for a gap in the same assignment
and wrong for a frame from an assignment the display no longer has. The
same early return also skipped persisting, so an outage or a restart
resumed the old group's content from local state.

The controller now records which assignment the frame on screen came
from. When the server says the current assignment has nothing, a frame
from another assignment is taken down (a new stage clear(), which also
abandons any transition still preparing) and the slate shows; and the
new assignment's state is persisted if the stored one belongs to a
different assignment. A gap within the same assignment still keeps its
last good frame, and every path with content is unchanged.

Regression tests: populated-group to empty-group reassignment drops the
old image and shows the slate; and a restart with no server after that
move does not resume the old group's content.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-13 20:38:42 -05:00

support

fix(ui): keep Signage state consistent across tabs, and confirm destructive actions

2026-10-12 21:32:04 -05:00

backoff.test.ts

fix(display): retry every failed request with backoff, and never give up

2026-10-05 21:31:55 -05:00

contributed-renderer.test.tsx

fix(display): define the display-server messages once, in src/shared

2026-10-05 21:25:21 -05:00

display-contract.test.ts

fix(display): keep blackout across reloads and follow the display's current assignment