feat(feed): load For You pages through one composite document query

[QuantumExplorer]

What

Loads a For You feed page through ONE composite getDocuments request instead of about ten: the page, its like/repost/reply/quote counts, the posts it quotes, the authors' profiles and DPNS names, and (logged in) the viewer's own likes, reposts and bookmarks on the page, all under a single merged proof. The SDK derives every sub-query from the proven page, so the responding node cannot substitute, omit or inject any of it.

Cold anonymous /feed goes from 15 to 19 DAPI calls to about 4 (bootstrap 2, composite page 1, trending 1); a logged-in load drops by a similar amount.

Blocked on

• An @dashevo/evo-sdk release carrying documents.composite (feat(wasm-sdk): composite document queries on the JS surface dashpay/platform#4605, on top of #4596 to #4604 and feat: merge a limited path query below a key another branch already owns dashpay/grovedb#850).
• Devnet nodes serving sub_queries on the V1 documents wire (feat(dapi): composite document queries on the getDocuments V1 wire dashpay/platform#4603).

Until then the change is inert: loadCompositeFeedPage checks for documents.composite at runtime and the v6 (refersTo-enforced) topology, and returns null so the legacy loaders run exactly as today. It also backs off for a minute after any composite failure. Bumping the evo-sdk dependency lights it up; no other switch is needed.

How

• lib/feed/composite-feed-page.ts: builds the query from the contract topology helpers (likeIndexFor, repostIndexFor, bookmarkIndexFor, quoteFieldFor, replyCountFieldFor), decodes the result into the raw page plus a PreloadedEnrichment, seeds the DPNS and profile caches with the proven documents (including proven absences), attaches quoted posts, and stamps counts and the viewer's marks onto the posts. Anonymous pages also chain the quoted posts' authors' profiles off the join so embedded cards need no straggler hop; logged-in pages spend those request slots on the viewer's marks instead (the platform caps a request at 10 sub-queries).
• lib/feed/load-for-you-feed.ts: tries the composite page first, for the first batch and the background top-ups. The feed paginates by document id while the composite surface paginates with a range clause on $createdAt, so the loader remembers the $createdAt of every cursor it handed out and translates; an unknown cursor takes the legacy path.
• hooks/use-progressive-enrichment.ts: enrichProgressively(posts, preloaded?) merges the preloaded slices at once and only queries what they did not cover (per author for names/profiles/avatars, per post for stats/interactions). Same state shape, so PostCard and every per-card fallback are untouched. hooks/use-feed-data.ts passes the preload through and the viewer id down.
• dpnsService.seedUsernames and unifiedProfileService.seedProfileDocuments: let proven lookups warm the batch resolvers; DPNS gains a five-minute negative cache so proven "no name" identities stop re-querying.

Repost attribution ("X reposted") stays on its own query: the repost count and a repost documents lookup would both read repost.byPost, which the composite rules forbid on one request, and the count is the better use of the slot. Quoted replies and blog quotes keep resolving through attachQuotedPosts, which now only runs for posts the composite did not already resolve.

Testing

• npx tsc --noEmit clean; next lint on the touched files reports only the pre-existing warnings.
• Not run against a network: no devnet with the composite surface exists yet. Once the evo-sdk bump lands, the query inspector should show one getDocuments for the page where it showed the page query, four grouped counts, the profile and DPNS batches and the quoted-post fetch.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}