Repository navigation
Conversations: synchronize read progress and pins through their source #2181
Description
Parent
Spec: #2178. Project: Open Cloud Groups. Milestone: v2.0.
What to build
Conversations: synchronize read progress and pins through their source. Follow the agreed tracer-bullet sequence; preserve real source ownership and existing grants. One issue per bounded implementation PR.
Acceptance criteria
- Mobile and another connected client synchronize reads and pins for the same cloud account and Channel; unrelated source/accounts remain unchanged.
- Existing Host read/roster authority remains; no aggregate duplicate preference authority.
- Cloud progress is monotonic and authorized, and distinct from history access floors and Bot delivery progress.
- Pins-first/recent-message sorting reflects saved source state after restart.
- Reuse TOB public API/CLI; if service changes are needed, create a separate TOB issue/PR with an independently runnable API/CLI acceptance path before the client PR. One PR per implementation issue.
- Source and real UAT multi-client evidence accompany the client PR.
Boundaries
UAT only; do not touch Prod or merge. Do not claim native/runtime success from source tests. Preserve other tasks and shared device queue.
Activity