4grayandClaude Opus 5.5 9bbeff32a3 fix(settings): retry a failed revert of a refused lock removal and fail closed meanwhile ...

When writing the previous store back after a relock-refused removal
fails, the lock store now keeps a pending rewrite, is not readable (the
locked session withholds everything) and rewrites the persisted store
from memory on the next access, so a restart cannot load the removal.
A failed "Remove all playlists" clear shares the same retry.

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

2026-09-27 13:53:09 +02:00

..

epg/data-access

perf(ci): run Tier A coverage concurrently with isolatedModules ts-jest (#1701)

2026-09-26 23:05:26 +02:00

m3u-state

perf(ci): run Tier A coverage concurrently with isolatedModules ts-jest (#1701)

2026-09-26 23:05:26 +02:00

playback/util

perf(ci): run Tier A coverage concurrently with isolatedModules ts-jest (#1701)

2026-09-26 23:05:26 +02:00

playlist

perf(ci): run Tier A coverage concurrently with isolatedModules ts-jest (#1701)

2026-09-26 23:05:26 +02:00

portal

fix(settings): refuse lock removals that commit after a relock and keep the index stale until the store write lands

2026-09-27 13:08:59 +02:00

services

fix(settings): retry a failed revert of a refused lock removal and fail closed meanwhile

2026-09-27 13:53:09 +02:00

shared

fix(settings): re-ask the PIN before a relocked backup merge and keep the PIN cooldown across prompts

2026-09-27 12:56:37 +02:00

ui

fix(settings): re-ask the PIN before a relocked backup merge and keep the PIN cooldown across prompts

2026-09-27 12:56:37 +02:00

workspace

fix(settings): restore backup locks after the Xtream merge and snapshot the Stalker lock dialog's categories

2026-09-27 12:04:45 +02:00

vercel.json

ci: add vercel configuration file to manage deployment settings

2026-04-06 15:05:06 +02:00