Local store
Changes are kept in the local SQLite/offline queue first.
Changes are kept in the local SQLite/offline queue first.
The FastAPI backend reads the queue and marks items as synced, pending, conflict or local only.
Production PostgreSQL/cloud sync is still a deployment task; this screen validates the local workflow.
There are no pending offline changes. Add a sample change to test the flow.
Setup edits are stored locally and added to the offline queue.
Pending changes are pushed when cloud access is available.
If remote data changed first, the item stays in conflict until resolved.