Fresh read variants that await a server round-trip (closes #75)

Adds Library.fresh(): forces a refresh, awaits its completion and persist, then returns the albums/photos/timeline read namespaces now reflecting a completed server round trip — the caller awaits and is guaranteed current at resolve. Default reads and the background loop are unchanged (immediate-from-cache). Concurrent fresh reads coalesce to one in-flight refresh; a fresh read whose refresh fails rejects rather than answering stale. The CLI adopts fresh reads separately (#52). Model: opus-4-8
2026-09-22 23:29:15 +02:00
parent 2e00139d3c
commit aeccb489b5
3 changed files with 358 additions and 12 deletions
@@ -193,6 +193,15 @@ export interface TimelineAPI {
    groups(args: { groupBy: GroupBy; filter?: PhotoFilter }): TimelineGroup[];
 }

+// The surface `Library.fresh()` resolves to (issue #75). It is the same three
+// read namespaces as the default `albums`/`photos`/`timeline`, handed back only
+// after a forced refresh has brought the local copy current.
+export interface FreshReads {
+    albums: AlbumsAPI;
+    photos: PhotosAPI;
+    timeline: TimelineAPI;
+}
+
 export const makeAlbumsAPI = (
    derive: () => DerivedRecords,
    content?: PhotoContent,