Blomios
d1b3f21d68
Ajoute un sprint, clôture le ticket #50, ajoute le cadrage du ticket #54. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
980 B
Markdown
16 lines
980 B
Markdown
---
|
|
id: "983aa02b-7577-4fde-b77a-12355df0efdb"
|
|
number: 50
|
|
title: "[Server] API de synchronisation incrémentale LWW"
|
|
status: "qa"
|
|
priority: "low"
|
|
sprint: null
|
|
links: [{"target":"#46","kind":"relatesTo"},{"target":"#48","kind":"dependsOn"},{"target":"#49","kind":"dependsOn"}]
|
|
agentRefs: []
|
|
createdBy: {"kind":"agent","agent_id":"f8f40941-ecf7-4830-b9de-8818a099f448"}
|
|
updatedBy: {"kind":"agent","agent_id":"57695b92-24d0-4876-837c-76116e70a6ae"}
|
|
createdAt: 1784412001974
|
|
updatedAt: 1784449447058
|
|
version: 3
|
|
---
|
|
Implémenter les ports/use cases et endpoints de sync incrémentale authentifiée. Endpoints : `POST /sync/push`, `GET /sync/pull?since=...`, optionnel `POST /sync/exchange`. Stratégie v1 last-write-wins basée sur `clientUpdatedAt` puis tie-breaker `serverUpdatedAt`/`serverId`. Supporter upsert, soft delete, réponses par item (`accepted`, `ignoredOlder`, `conflictLwwApplied`, `error`) et cursor serveur monotone. Ne pas intégrer le client Flutter dans ce ticket. |