Claude a5086aed0b fix(rundown): narrow rundown invalidation ...

Two independent issues in the revision strategy.

The client guard only skipped a refetch when the revision matched exactly,
while its comment described skipping anything not newer. A message which
arrives after a refetch has already brought in a later revision forced a
needless refetch. Compare with <= so the guard does what it claims.

Renaming a rundown re-initialised it, which stops playback. Renaming the
loaded rundown during a show therefore stopped the show. A title has no
bearing on the schedule, so it now goes through an ordinary transaction:
the title is persisted, the revision bumped and clients notified, with no
runtime involvement. Renaming to the current title is a no-op.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011a5cbVjNC5XXF88b2PkUCa

2026-08-30 10:51:20 +00:00

..

cli

bump version to 4.13.0

2026-08-28 12:04:02 +02:00

client

fix(rundown): narrow rundown invalidation

2026-08-30 10:51:20 +00:00

electron

bump version to 4.13.0

2026-08-28 12:04:02 +02:00

resolver

bump version to 4.13.0

2026-08-28 12:04:02 +02:00

server

fix(rundown): narrow rundown invalidation

2026-08-30 10:51:20 +00:00

spec

Deps migration (#1988)

2026-03-08 16:22:12 +01:00