Read config tree from json config file and return

Return all data found inside a registry section

Saved-server list persistence. Pure registry operations on the saved_servers key — config.bs's domain, alongside getSavedUsers — called from both SetServerScreen (render thread, delete) and the loginRouter coordinator (main thread, save).

Recursivly search the config tree for entry with settingname equal to key

Pure: match the saved_servers JSON against a server GUID, case-insensitively (via serverIdsMatch). Split out from the registry read (findSavedServerByGuid in replayRoute.bs) so the match logic is unit-testable without touching the registry (getSetting reads the real "JellyRock" section, which tests must not write). Lives here alongside the saved_servers shape.

Helper to get the global registry section name Returns "test-global" during tests, "JellyRock" in production

Return an array of all the registry section keys

Returns an array of saved users from the registry that belong to the active server

"JellyRock" registry accessors for the default global settings

Filter registry keys to find those that should be deleted during a settings reset Preserves session/identity keys, deletes everything else

User registry accessors for the currently active user

Helper to determine if a setting is global (applies to all users)

Generic registry accessors

True when two Jellyfin server ids refer to the same server. Jellyfin GUIDs are canonical lower-case hex, but fold both sides so a mis-cased id (e.g. from an external deep-link/cast sender) still matches. The single source of truth for "same server?" across the saved-server list and the saved-user filter — keeps every id comparison consistent.

Convert dynamic value to string for registry storage