Falcon Rundown 1.2.3 Changelog

Version 1.2.3 strengthens collaborative editing with more reliable story locks in Safari, safer recovery after tab and background transitions, and consistent lock enforcement across Rundown, REST and Schedule operations.

Story Lock Reliability

• Safari-safe lifecycle: Story locks now release and reacquire safely through editor navigation, background suspension and back/forward cache restores.
• Exact tab ownership: Locks are tied to the precise editor tab and generation, so a delayed request from an older tab cannot release or write through a newer lock.
• Safer resume and takeover: Editors remain read-only until ownership has been revalidated or reacquired, and interrupted acquire or takeover responses recover without leaving orphan locks.
• Draft protection: Unsaved story content is preserved when a lock is lost, an editor unmounts or another user takes over, and can be restored after a fresh lock is obtained.

Security and Consistency

• Story saves, file uploads and REST writes now verify current permissions, project filters, archive state and the exact active editor lock.
• Story, rundown, folder, layout and workspace operations that could invalidate active editing now refuse to continue while affected stories are locked.
• Permission and filter changes are revalidated atomically during mutations, preventing stale browser sessions from retaining write access.
• Legacy lock calls and retired application endpoints now fail closed.

Schedule Safety

• Worker safety contract v2: Schedule executions validate current actor permissions, project and filter scope, active story locks and canonical transaction ordering before changing data.
• Fail-closed automation: Live Schedule actions require a compatible worker heartbeat. Migrated rules are disabled for explicit review before they are enabled again.