github-stars-backfill-rules

To handle Dexie schema changes safely, evaluate whether config normalization, a schema bump, lazy hydration, or a one-shot backfill is needed to ensure compatibility with legacy rows and missing fields.

The best way to backfill missing fields is applying a capability-keyed backfill design that regression-safely handles legacy rows across IndexedDB and chrome.storage.local without triggering unnecessary full syncs.

You need a full sync backfill when persisted data requires comprehensive normalization across sync workflows, whereas lazy hydration applies when adding a new persisted repo field without immediate full data reprocessing.

Adding a new persisted repo field does not always require a Dexie schema migration; you can normalize config, implement lazy hydration, or run a feature backfill task depending on the specific storage change requirements.

A storage upgrade triggers a full sync backfill unexpectedly when compatibility reviews detect missing fields or unnormalized config across auth, upgrades, and sync workflows that fail versioned persistence rules for legacy rows.

You can use chrome.storage.local alongside IndexedDB by applying compatibility rules that regression-safely handle schema evolution, backfill state, and missing fields across both storage mechanisms during upgrades.