mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
One table holds an entry per write route, and every User column the backup classifies as a setting appears in exactly one entry; a new setting column fails the inventory case until it has one. For each entry the file sets a non-default value through its write route, reads it back through its read route and through /api/auth/me where that publishes it, and checks the stored column moved off what a fresh account holds. The backup leg runs through the routes too: the portable full backup a person downloads, the operator's upload, and the restore into an account recreated under the same id. Every setting must read back identically on the restored account, through the same routes and the account payload, and every stored column must come back with its value.