feat(timeline): progressive day hydration with exact layout manifest (spec 051) #1000
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/timeline-instant-placeholders"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
GET /api/timeline/daysaccepts optionallayoutDayCount(clamped [0,24]) andlayoutAround; a bounded window of days carrieslayoutItems(id, mediaType, captureTimestamp, createdAt, width, height — no URLs).NON_NULLkeeps the response byte-identical for callers that do not opt in. One layout query reuses the day-items FROM/JOIN/visibility/predicate structure with identical ordering and a per-day 500-entry cap.layoutItemsrender as exact, non-interactive, aria-hidden placeholder tiles through the same justified-row layout path as real items (identical geometry, no layout shift), each with a subtle centered spinner (animate-spin, neveranimate-pulse— spec-013 guard). Placeholders carry nodata-timeline-media-id, so selection and scroll anchoring only ever resolve real tiles. Days without a manifest keep the existing count-based placeholders.specs/051-progressive-timeline-day-hydration/(spec, plan, tasks; renumbered from 050 after main claimed 050 for semisupervised clustering).CI environment fixes (bundled — scoped tests were red on every branch)
build.gradle.kts: pin Testcontainers docker clientapi.version=1.44. Docker Engine >= 28 (Winterfell/CI) rejects docker-java default 1.32 — this was the real ISSUE-076 root cause (runner configs were identical to the working NUC ones).deploy/postgres/Dockerfile+ README: basepostgis/postgis:16-*is Debian 11-only and PGDG removedbullseye-pgdg(2026-08), so the image could not be rebuilt anywhere. Nowpostgres:16(Debian 13) +postgresql-16-postgis-3+postgresql-16-pgvector; PG major 16 and the data volume path unchanged. Note: merging this rebuilds and recreates thememories-postgrescontainer via the normal CI deploy path (volume preserved).Verification
:apps:api:test: 1418 tests, 0 failures on the CI daemon (Engine 29.7.2) with both fixesnpm run check(svelte-check): 0 errors (pre-existing warnings only)npm run test:unit(vitest): 60/60 after merging origin/mainb3dab737merged in; no file overlap): svelte-check 0 errors, vitest 60/60,:apps:api:compileJava+compileTestJavaOK; spec 051 validated via spec-queryDocker Engine >= 28 rejects docker-java's default client API 1.32 ('Minimum supported API version is 1.40'), so every Testcontainers suite failed at DockerClientProviderStrategy on hosts with new daemons (Winterfell / its CI runners) while the NUC's older engine accepted it. Verifiable locally: GET /v1.32/version returns 404-era 400, /v1.44 is 200. The value is overridable with -Dapi.version for other daemons.feat(timeline): progressive day hydration with exact layout manifest (spec 050)to feat(timeline): progressive day hydration with exact layout manifest (spec 051)