fix(relay): accept whitespace-prefixed stored JSON (#161)

Select the stored format from a whitespace-trimmed view while decoding the original JSON value, and align the
changelog with Relay device-ID and provisioning terminology.

What could go wrong and why this is safe: valid JSON with leading whitespace could otherwise be mistaken for a
legacy identifier and block Relay work. The change affects format selection only; every decoded member still passes
canonical validation, malformed reads remain fail-closed, and no rewrite, delete, or provisioning path is added.

Author: psimaker

CHANGELOG.md

@@ -12,7 +12,7 @@ All notable changes to VaultSync are documented here.
 
 ### Fixed
 
-- **Cloud Relay no longer continues from invalid saved server identities** ([#161](https://github.com/psimaker/vaultsync/issues/161)) — if secure storage contains a malformed server identifier, VaultSync reports that registration did not complete and sends no registration request, without rewriting or deleting the stored value. Valid existing JSON and legacy records remain unchanged.
+- **Cloud Relay no longer continues from malformed saved Relay device IDs** ([#161](https://github.com/psimaker/vaultsync/issues/161)) — VaultSync reports that Cloud Relay provisioning did not complete and sends no provisioning request, without rewriting or deleting the stored value. Valid existing JSON and legacy records remain unchanged.
 - **Push and Cloud Relay registration details now survive failed secure-storage updates** ([#148](https://github.com/psimaker/vaultsync/issues/148)) — VaultSync keeps the last valid value when a replacement cannot be saved and reports the failure instead of continuing as if registration succeeded.
 - **Folder access now stays intact when reconnecting or syncing in the background** ([#147](https://github.com/psimaker/vaultsync/issues/147)) — reselecting the same Obsidian folder no longer accumulates access claims. Switching folders takes effect only after the new location is readable, scanned, and its permission is saved; any failure keeps the previous folder connected. Background runs release only their own access on completion, restart, or cancellation.
 - **Background sync no longer reports unfinished work as completed** ([#146](https://github.com/psimaker/vaultsync/issues/146)) — continued processing now reports success only after every expected vault is confirmed fully idle. If the sync engine stops, vault status cannot be read, a vault reports an error, the run expires or is cancelled, or the app returns to the foreground, the background run reports failure instead; conflict checks happen only after idle is proven.

ios/VaultSync/Services/SubscriptionManager.swift

@@ -118,7 +118,7 @@ enum RelayDeviceIDStorage {
 
     static func decodeStoredValue(_ stored: String) -> LoadResult {
         let ids: [String]
-        if stored.hasPrefix("[") {
+        if stored.trimmingCharacters(in: .whitespacesAndNewlines).hasPrefix("[") {
             guard let data = stored.data(using: .utf8),
                   let decoded = try? JSONDecoder().decode([String].self, from: data) else {
                 return .failed

ios/VaultSyncTests/KeychainServiceTests.swift

@@ -402,6 +402,19 @@ struct RelayDeviceIDStorageTests {
         ]))
     }
 
+    @Test("Valid JSON with leading whitespace loads unchanged (#161)")
+    func issue161WhitespacePrefixedJSONStorageLoads() throws {
+        let stored = " \n\t" + (try Self.json([
+            Self.firstValidDeviceID,
+            Self.secondValidDeviceID,
+        ]))
+
+        #expect(RelayDeviceIDStorage.decodeStoredValue(stored) == .loaded([
+            Self.firstValidDeviceID,
+            Self.secondValidDeviceID,
+        ]))
+    }
+
     @Test("A JSON array containing only an invalid device ID fails closed (#161)")
     func issue161InvalidJSONMemberFailsClosed() throws {
         let stored = try Self.json([Self.invalidDeviceID])