Ajoute la note mémoire d'architecture serveur (sync/sharing), passe les tickets #44/#45 en QA, ajoute le cadrage du chantier serveur (tickets #47 à #53). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
1019 B
Markdown
16 lines
1019 B
Markdown
---
|
|
id: "c73b39be-061c-44b4-b5c3-f482878fe58d"
|
|
number: 49
|
|
title: "[Server] Schéma PostgreSQL sync-ready GameTime"
|
|
status: "open"
|
|
priority: "low"
|
|
sprint: null
|
|
links: [{"target":"#46","kind":"relatesTo"},{"target":"#47","kind":"dependsOn"}]
|
|
agentRefs: []
|
|
createdBy: {"kind":"agent","agent_id":"f8f40941-ecf7-4830-b9de-8818a099f448"}
|
|
updatedBy: {"kind":"agent","agent_id":"f8f40941-ecf7-4830-b9de-8818a099f448"}
|
|
createdAt: 1784411997184
|
|
updatedAt: 1784411997184
|
|
version: 1
|
|
---
|
|
Créer le modèle serveur PostgreSQL pour les ressources synchronisables : Exercise, Program, WorkoutTemplate, WorkoutHistory, MediaAsset metadata, plus tables d'ownership par utilisateur. Chaque ressource doit stocker `ownerUserId`, `clientId`, `serverId`, `payloadJson`, `clientUpdatedAt`, `serverUpdatedAt`, `deletedAt`, `schemaVersion`, `originDeviceId`. Prévoir contraintes d'unicité `(owner_user_id, resource_type, client_id)`, index pull incrémental `(owner_user_id, resource_type, server_updated_at)`, migrations et tests repository. |