Merge wave B — the connect step reads liveness, not a latched field

A provider with no sync history reports "unknown" instead of "connected",
so a fresh account is no longer told a device it never linked is already
delivering; the connect step resolves the sync verdict into four honest
tiles, records the flow's result only for a connection that is actually
serving, points an unconfigured provider at its credentials, and steps
over a source the account already has.
This commit is contained in:
Marc-André Bombeck committed 2026-09-11 10:24:54 +02:00
commit 4d7b326fda
25 files changed
+1440 -73

No files matched your search

+2 -1
View File
@@ -326,9 +326,10 @@ const integrationLedgerState = z
"error_reauth",
"disconnected",
"parked",
"unknown",
])
.describe(
"Last recorded ledger state for this provider. `connected` is also the value a user who has never synced sees — the ledger row is created on the first attempt, and its absence reads as `connected`, not as an error.",
"Last recorded ledger state for this provider. `unknown` (added v1.38.19) is what a user who has never synced sees: the ledger row is created on the first attempt, and its absence is no claim about the connection in either direction — it used to read as `connected`, which is why a client must never treat this field as liveness. Read `syncHealth.verdict` for that, and treat `unknown` as `disconnected` anywhere a ledger state is painted.",
);
const nightscoutConnectRequest = nightscoutConnectSchema.meta({