feat(rendering): slice 14 — view bridge: ledger rows → legacy FeedRenderItems#443
Merged
Juliusolsson05 merged 1 commit intoJul 7, 2026
Conversation
…derItems ledgerToFeedItems maps RenderLedger rows to the FeedRenderItem shape Feed already renders, so the Stage 3 flag swap replaces ONE call site (the decision core) while LazyEntry, memo structure, autoscroll tail-signature and TextProse/StreamingProse survive untouched. SemanticStreamingTurn keeps rendering semantic items until the final cutover slice deletes it with ghost rule 3 (D6) — decoupling the decision-core swap from a row- component rewrite. Order contract: items emit in LEDGER order with order fields engineered so legacy sortFeedRenderItems is a no-op (matching phase partition, null timeMs, constant source, index sequence). Payload references are the runtime's own objects (Entry / SemanticLiveTurn) so downstream memos hold. Unresolvable candidates surface in `dropped`, never silently omitted. 83 pipeline tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last structural piece before the cutover slice:
view/ledgerFeedItems.tsmapsRenderLedgerrows to theFeedRenderItemshape Feed already renders, soAGENT_CODE_RENDER_PIPELINE=1will swap ONE call site — the decision core — while LazyEntry, the memo structure, autoscroll's tail-signature, and TextProse/StreamingProse survive untouched. SemanticStreamingTurn keeps rendering semantic items until the final cutover deletes it atomically with ghost rule 3 (plan D6).orderfields engineered so legacysortFeedRenderItemsis a no-op over them (matching phase partition, null timeMs, constant source, index-based sequence) — the D4 chronological merge stays authoritative even though the legacy sorter still runs.Entry/SemanticLiveTurnobject references, asserted in tests — anything else would re-render every memoized row per tick (the D11 churn class).droppedfor the caller to surface — a silently missing row is the Optimistic submitted user prompts are buried behind semantic/work rows #239 failure class this rewrite exists to kill.deriveFeedRenderModelon runtime scenarios (streaming, ghost fallback, optimistic, empty).83 pipeline tests; tsc gate (node + web) clean.
🤖 Generated with Claude Code