Krzysztof Rudnicki cfc4c295e4 crdt_sync: add the one-shot GitHub -> Firebase data migration ... Reads through the GitHub API, not a local clone: the checkout on this machine was five days stale while devices kept syncing, so seeding from it would have silently rolled back everything written in between. Blobs are fetched by sha rather than by path, so a concurrent push cannot swap the content out from under the tree listing. Writes through the real FirebaseSyncClient so the migration exercises the same key escaping the apps will, then reads every blob back and compares bytes before reporting success -- a migration that claimed success without checking would be indistinguishable from one that dropped a file. Retries connection resets and 5xx: GitHub drops keep-alive connections routinely, and a half-completed migration is worse than one that never started. Three things are deliberately left behind, and stay in the GitHub repo (archived, not deleted): - todo-sync/changesets/ pre-migration sqlite_crdt format, unread since 2026-07-17 - diet-guard-sync/devices/desktop/ a replica that stopped syncing on 2026-07-22; verified to hold 0 records, 0 tombstones and 0 fields newer than both `pc` and `phone`. Carrying it over would cost a full re-download every tick forever, since a device that publishes no revision can never be skipped - READMEs and .gitkeep, which are not sync data Run against the live database: 16 files, 956,272 bytes, all verified byte-for-byte, and independently re-checked by listing the namespaces and parsing records back out.		2026-08-03 18:31:18 +02:00
..
__init__.py	crdt_sync: add the one-shot GitHub -> Firebase data migration	2026-08-03 18:31:18 +02:00
migrate_github_to_firebase.py	crdt_sync: add the one-shot GitHub -> Firebase data migration	2026-08-03 18:31:18 +02:00