Signage

Zayin/Signage

Fork 0

Files

T

History

ekklesiaandClaude Opus 5.5 855b5f9f54

CI / lint (pull_request) Successful in 14s

Details

CI / typecheck (pull_request) Successful in 15s

Details

CI / test (pull_request) Successful in 21s

Details

CI / build (pull_request) Successful in 19s

Details

CI / integration (pull_request) Successful in 6m0s

Details

chore: release signage 0.1.2

0.1.2 fixes what the first production Signage deployment found:
- #4: the display and server share one message schema; every heartbeat
  from an image slide used to be refused with a 400;
- #5: every display request retries with backoff and never gives up, so
  a display that failed one request no longer stays offline until
  reloaded;
- #6: one object URL per cached slide, released when done; the leak
  exhausted the browser within minutes;
- CI (#7, #8): every change runs inside a pinned Ekklesia, end to end
  in a real browser, and cleans up even when killed.

compatibility.platform stays ^0.1.0: every fix is module-side, and CI
tested it against platform v0.1.1 plus test-only scripts. The README no
longer says Signage is unreleased or undeployed.

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

2026-10-05 22:08:31 -05:00

support

chore: release signage 0.1.2

2026-10-05 22:08:31 -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

test(display): run the real display controller against the real viewer routes