7 Commits

Include renames

Author	SHA1	Message	Date
ekklesiaandClaude Opus 5.5	7c17282616	fix(ui): keep Signage state consistent across tabs, and confirm destructive actions ... Activating a timeline from Playback left Timelines showing it as inactive, because each tab read its own stale copy of the channel groups; operators read that as activation not sticking. Tabs also mounted every panel afresh, so each switch flashed a spinner and collapsed the page before regrowing. Panels now share one stale-while-revalidate resource cache, and Playback follows the management realtime channel so Now showing tracks the wall. Deleting an image, a timeline, a slot, a source, or an audience happened on a single click; each is now a two-step in-place confirmation (DESIGN 21.3). The audience key was presented as a field to fill in. Audiences are now named in plain words, explained (images look the same for every audience), and the content key is derived from the name with an Advanced override. The roster labels signed-in browsers and lets an offline entry be removed after confirmation, so test tabs and retired screens no longer accumulate. The preview keeps nothing in the Dashboard origin's storage, and the narrow-screen notice no longer names the platform. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-12 21:32:04 -05:00
ekklesia	a8c35db201	chore: release signage 0.1.4	2026-10-10 23:02:55 -05:00
ekklesiaandClaude Opus 5.5	dd656eb18a	chore: release signage 0.1.3 ... 0.1.3 ships the external package integration validated in #13 (Pass 2): the canonical linux-x64-glibc Module Package installed and exercised end to end by CI, with bounded external runtime image processing. Only the version moves: the manifest, package.json, the server runtime, both browser artifacts, the settings payload's moduleVersion, the test fixtures, and the README status line. compatibility stays platform ^0.2.0 and moduleSdk ^0.2.0; Core 0.2.4 already satisfies it, so the range is not tightened. pnpm-lock.yaml carries no root version and is unchanged. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-10 12:20:06 -05:00
ekklesiaandClaude Opus 5.5	855b5f9f54	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
ekklesia	1bf89a3942	feat: align Signage with platform display and design	2026-09-30 18:21:42 -05:00
ekklesia	af0f0adadc	test: align signage release expectations	2026-09-29 20:50:02 -05:00
ekklesia	92bef4c7aa	feat: initial Signage 0.1.0	2026-08-28 16:41:54 -05:00