4grayandClaude Opus 5.5 302c3b0eb9 fix(dashboard): gate rail skeletons per rail, never above visible rails ...

Addresses the Codex and Greptile reviews on #1738. The component-wide grace
timer started when the dashboard was created, so a rail that begins loading
later (Xtream recently added, TMDB) showed its skeleton at once and could
still flash and collapse; and after the grace period a slow rail's skeleton
could appear above rails that already showed cards, pushing them down and,
if it resolved empty, back up.

createRailSkeletonGates now keeps one gate per rail, in template order: the
grace period counts from that rail's own loading start, a skeleton is never
inserted above a rail that already has cards (the real rail inserts at most
once instead), and a shown skeleton stays until its own rail finishes so the
first arriving rail does not collapse the others in a cascade. Nine specs
cover the fast path, per-rail start, the no-content-below rule, latching,
reloading, destroy and a zero grace period. The seeded-profile timeline is
unchanged at 0.0004 across three renderer reloads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-27 21:51:59 +02:00

..

architecture

fix(dashboard): gate rail skeletons per rail, never above visible rails

2026-09-27 21:51:59 +02:00

development

test(performance): count startup phases and SQL statements for the J1 launch journey (#1715)

2026-09-27 21:01:26 +02:00

maintenance

ci(test): type-check Jest spec programs and gate it in CI (#1705)

2026-09-27 20:54:27 +02:00

superpowers

feat(epg): rebuild the programme guide for M3U playlists (#1560)

2026-09-06 18:47:25 +02:00