Video preview initialisation now uses a lifecycle token so stale async setup from a previously closed preview is discarded and cleaned up immediately. This prevents old preview instances from leaving behind active client walkers or stream sessions when users switch videos quickly.\n\nImage subtitle prefetching now also extends to the known video end as soon as duration metadata arrives, even before playback advances, so subtitle cache filling continues towards full coverage without relying on current playback position.
Subtitles no longer lose their lookahead buffer when cache-only fallback fetches are triggered repeatedly during playback. This improves subtitle continuity in longer viewing sessions and when moving between videos, where captions could otherwise appear to stall until playback moved far enough ahead again.\n\nThe shared subtitle player now preserves prefetch progress during fallback current-frame requests, and a regression test covers repeated fallback triggers to ensure prefetch requests are not reset by that path.
Image subtitle rendering now tolerates timestamp boundary drift when matching cached frames and can optionally perform a throttled current-time fallback fetch when cache-only mode misses. This improves subtitle reliability near the end of videos or while paused without introducing request bursts. Added regression coverage for paused near-end rendering and cache-miss fallback behavior.
The Debug dashboard now shows server-maintenance telemetry, including auth/share row counts and restart scheduler status. The Admin server section now includes a persistent scheduled-restart form with cadence/time options, and controls are disabled when the app is not running under systemd.
Admins can now persist a global scheduled restart policy with cadence and time. When enabled under systemd, the server waits for at least one hour of no logged-in clients before shutting down so systemd can restart it safely. The debug API now exposes maintenance row counts and cleanup/scheduler runtime snapshots for long-uptime monitoring.
Server maintenance now removes stale auth sessions and expired share links automatically during long runtimes. The app also prunes stale zip cache files in the background so disk usage and DB row growth stay under control over weeks of uptime.
Server-side image subtitle caches now evict frame and event data as soon as the slowest active viewer has passed each event (with a short grace), instead of keeping old event bytes until cache-cap pressure.\n\nThis reduces long-session memory growth and lowers crash risk when subtitle prefetch advances quickly through many events.
Image subtitle warmup now starts immediately when a subtitle track is selected, prefetching an initial timeline window before playback advances. This reduces missing caption frames at the beginning of playback for longer videos and avoids needing to pause or rewind to catch early lines.\n\nThe app and share player both use a 60-second startup warmup while keeping cache-only foreground subtitle rendering and background walker ownership of subtitle network requests.
Subtitle rendering now separates playback from stream fetching to reduce contention during long watch sessions. The foreground player reads subtitle frames from cache while the background prefetch walker owns subtitle frame network requests.\n\nThis improves stability after multiple consecutive videos by removing competing current-frame requests, and keeps share playback aligned with the same cache-first behaviour.
The technical reference now documents last-folder persistence and browser-history navigation behaviour.\nThe generated test index was refreshed to include the new route and page-load scenarios.
Folder navigation now tracks an in-app browse history that maps to browser back and forward buttons.\nWhen users navigate all the way back to browse index 0, the app prompts whether to return to the previous webpage.\nThe client now also uses the server-provided last folder when no local restore folder is available.