Loomworks list-loading — CR-2 build checkpoint — v0.1

Status: PAUSED at a clean checkpoint after Step 2 — Steps 3–6 not started. No push. Date: 2026-06-27 By: Claude Code (CC) on DUNIN7-M4 Builds: loomworks-list-loading-cr-1-engine-cursor-contract (merged eeae9c2/0096) → CR-2 …-cr-2-frontend-load-more-v0_2

> Read-only-safe checkpoint: both repos sit on feature branches at committed, suite-green states; main/feat-companion-surface untouched; nothing pushed.

Done (committed, suites green)

Part 1 — record commit (PUSHED). loomworks-record HEAD 9b72ca5 — CR-2 v0.2 + CR-2 Step-0 report (+ the earlier CR-1 v0.3 / standing note / impl-note backlog in 0011837).

Step 1 — engine lists.page_size setting. Engine branch list-loading-cr-2-page-size @ e5bbf05 (off main eeae9c2; main untouched; not pushed). Nullable bounded-numeric setting [10,100] on the three-place pattern (KNOWN_SETTINGS + _LABEL_TO_KEY + plain-words). Made the shared numeric tune path None-safe for the nullable default (zero regression for the two existing settings); orientation catalog grew 3→4. 9 new tests; full engine suite 3041/0/63.

Step 2 — reusable load-more spine. OL branch list-loading-cr-2-frontend-load-more @ 5973ff8 (off feat-companion-surface 17263c9; not pushed). The shared, generic pagination core, extracted to the general list shape (D-3):

• src/lib/pagination.ts — PagedResult<T> + FetchPage<T> + toPagedResult() (the per-endpoint item-key is absorbed by each adapter).
• src/hooks/usePagedList.ts — first page on mount/resetKey/reload; loadMore accumulates; append + prepend modes; optional dedupKey; caller-resolved pageSize (lists.page_size ?? surface default).
• src/components/lists/LoadMoreControl.tsx — explicit (not infinite scroll); button only when has_more; count always ("Showing N of TOTAL").
• 12 isolation tests; full OL suite 390/76 green. (4 pre-existing tsc errors in unrelated tags/provider test files — not introduced here.)

Not started — Steps 3–6 (why paused here)

The spine is built and tested; Steps 3–6 are its application to real components. I paused at this clean boundary rather than half-wire components, for two reasons the CR itself anticipates:

1. Blast radius (the >30-test halt signal). Each surface is embedded in multiple parents whose tests mock the fetch adapters. Rewiring one fetch contract forces mock updates across that surface's component test and every embedder (e.g. renders touches RenderingRoom.test, lib/renders.test, plus WorkspacePane/MobileSurface/InEngagementSurface mocks). Across Memory (two lists: held + committed), Rendering, the home engagement list, the home lenses, and CenterPane, Steps 3–6 collectively touch well over 30 existing tests. The CR grants per-surface commits precisely for this.
2. Clean, durable checkpoint — both repos green and committed; no partial component surgery left behind.

Remaining, now well-scoped against the spine:

• Step 3 — apply to the three wholesale surfaces (each currently limit=200):
• renders / RenderingRoom — single list. D-4 outcome (confirmed): the engine renders endpoint sorts created_at ASC and pages forward (oldest→newer via next_cursor); a forward-only keyset cannot land on the newest page, so the land-on-oldest fallback applies (page 1 = oldest, load-more = newer) — which matches what RenderingRoom displays today (no reversal), so it's not even a display change. Report this, don't fight it.
• assertions / MemoryRoom — two paged lists (held + committed) in one room.
• engagements / home "Your engagements" list.
• Wire-boundary note: the renders.ts / memory.ts / projects.ts adapters still declare stale envelope types (offset, no has_more/next_cursor) — add the CR-1 keyset fields when paging.
• Step 4 — home lenses re-wire (/me/dashboard/needs_you + /recent already keyset-conformant; stop discarding next_cursor) + the third settings place (applySettingChange branch in useConversation.ts:71).
• Step 5 — per-surface page-size defaults (Memory/Rendering ~15, home engagement list ~40, needs_you ~15).
• Step 6 — CenterPane before→cursor migration (two call sites: useConversation.ts + ChatView.tsx); CenterPane adopts the Step-2 control in prepend mode (dedupKey kept as belt-and-braces); surface the now-available total_count.

State summary

| Repo | Branch | HEAD | Pushed? | |---|---|---|---| | loomworks-record | main | 9b72ca5 | yes | | loomworks-engine | list-loading-cr-2-page-size | e5bbf05 | no (main eeae9c2 untouched) | | loomworks (OL) | list-loading-cr-2-frontend-load-more | 5973ff8 | no (off feat-companion-surface) |

HALT. Awaiting a go-ahead to continue Steps 3–6 (each a bounded surface-wiring against the built spine), or to split them across sessions. No push.

DUNIN7 — Done In Seven LLC — Miami, Florida · list-loading CR-2 build checkpoint v0.1 · 2026-06-27