Offline sync service (queue, retry, conflict)

[AojdevStudio]

Parent

#1 (Platform Spine Epic)

Plain English

Let work done offline be queued and later sent to the cloud reliably, retrying failures, avoiding duplicates, and resolving conflicts by a defined policy.

What to build

An offline sync queue in the desktop with retry, conflict detection, and reconciliation policy; tests for queue, retry, duplicate-replay, and conflict handling.

Acceptance criteria

• Offline changes are queued
• Failed sends retry per policy
• Duplicate replays do not double-apply
• Conflicts resolve per the defined policy (tested)

Blocked by

• Walking skeleton: workspace, capability crates, Tauri shell, API health #20
• Local data service (SQLite migrations, repo, persistence test) #33