[Devbook drift] .devbook/arc42/05-building-block-view.md#cloud-service #885

Scheduled Devbook verify run, 2026-09-30 (devbook:verify-change, kind building-block).

Evidence: The documented parts hold. The Sync.Api → Sync/Cosmos/BlobStorage edges exist. ITaskReplica and IAttachmentStore are in Modules.Sync/Ports with in-memory Adapters. Only Cosmos and BlobStorage reference their SDKs. SyncAttachmentOptions.SectionName = "Modules:Sync:Attachments". There is no webhook, FCM or WoL code, which matches "not built yet". The code also carries what the section omits: the ISessionReplica and IAnnotationReplica ports, the sessions and annotations Cosmos containers (AppHost lines 265-266, CosmosOptions), and the /sessions, /annotations, /inbox and /inbox/{id}/ack routes (SyncRoutes).

Detail

• src/Modules/Sync/Backlog.Modules.Sync/Ports/ISessionReplica.cs and IAnnotationReplica.cs (with Adapters/InMemorySessionReplica.cs and InMemoryAnnotationReplica.cs) are replication ports the section does not name. It describes only ITaskReplica, IAttachmentStore, the device registry and pairing codes.
• The AppHost declares five Cosmos containers: tasks, sessions, annotations, devices, pairingCodes. Infrastructure.Cosmos/CosmosOptions.cs has SessionsContainerName and AnnotationsContainerName. The section names only three.
• The Sync API serves routes the section does not list: SessionSyncEndpoints (/api/sync/sessions), AnnotationSyncEndpoints (/api/sync/annotations) and InboxEndpoints (/api/sync/inbox, /inbox/{id}/ack), all under PairedDevice authorization.
• The section says the cloud stores "never domain data", but session and annotation replicas are now held in the cloud. Local ADR 0011 records annotations as a third replica container.

Action: run devbook:capture-specs (kind building-block) over .devbook/arc42/05-building-block-view.md#cloud-service and carry the plan in through flow-spec.

Read-only: nothing was run or written. The chapter carries no draft or proposed status, and no open pull request or change names it.