feat(wasm-sdk): composite document queries on the JS surface

[QuantumExplorer]

Issue being fixed or feature implemented

Last platform PR of the composite document query series (Yappr feed: one merged proof per feed page instead of 15 to 19 round trips). Stack:

1. feat: merge a limited path query below a key another branch already owns grovedb#850 (recursive graft for colliding limited branches)
2. chore: bump grovedb to 2d95c567 (#850 merged: limited branches graft below a shared key) #4597 (grovedb pin)
3. feat(drive): composite document queries: a page plus derived sub-queries under one merged proof #4598 (rs-drive core: shapes, execution, merged proof, verifier)
4. feat(dapi): composite document queries on the getDocuments V1 wire #4599 (wire: proto sub_queries, drive-abci dispatch)
5. feat(sdk): composite document queries, the client stack #4600 (client stack: dash-platform-queries, proof verifier, rs-sdk)
6. this PR (wasm-sdk + js-evo-sdk surface, e2e spec)

What was done?

• wasm-sdk: getCompositeDocuments(query) and getCompositeDocumentsWithProofInfo(query), mirroring the chained surface. The query object is the page (dataContractId, documentType, where, orderBy, a required limit) plus subQueries, each with an optional dataContractId (defaults to the page's), documentType, kind: 'documents' | 'counts', fixed where / orderBy, an optional per-value limit, and an optional bind: { source?: 'page' | index, sourceProperty, field }. Sub-query contracts are fetched through the same contract cache as the page's. The result is { pageDocuments, subResults }, each sub-result a discriminated union: { kind: 'documents', documents } or { kind: 'counts', counts: Map<base58 id, bigint> }. TypeScript declarations ride the usual custom section. parse_order_clause becomes crate-visible next to parse_where_clause.
• js-evo-sdk: sdk.documents.composite(query) and sdk.documents.compositeWithProof(query), plus a README section with the feed-page example and the four sub-query shapes.
• platform-test-suite: a composite case in the IndexOnlyDocument spec, right after the chained one: the dash posts page, one like count per post from the countable [hashtag, postId] index, and the viewer's own likes through the byLiker terminal (value-bounded, no limit).

Usage:

const page = await sdk.documents.composite({
  dataContractId: YAPPR,
  documentType: 'post',
  where: [['hashtag', '==', 'dash']],
  limit: 20,
  subQueries: [
    { documentType: 'like', kind: 'counts', where: [['hashtag', '==', 'dash']], bind: { sourceProperty: '$id', field: 'postId' } },
    { documentType: 'post', bind: { sourceProperty: 'quotedPostId', field: '$id' } },
    { dataContractId: DASHPAY, documentType: 'profile', bind: { sourceProperty: '$ownerId', field: '$ownerId' } },
  ],
});

How Has This Been Tested?

• cargo test -p wasm-sdk (native): 103 tests green; cargo clippy -p wasm-sdk --tests clean apart from the pre-existing rs-drive DocumentPropertyType unused import under verify-only features.
• ESLint on the facade and the spec (the spec's import-x/no-unresolved on dash is the usual uninstalled-workspace noise, not a finding).
• The e2e case runs in the platform test suite against a network carrying feat(dapi): composite document queries on the getDocuments V1 wire #4599 and feat(sdk): composite document queries, the client stack #4600; it was not run locally (no local network in this environment).

Breaking Changes

None. New methods only.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 704f01ad-f90a-4487-9639-baa922475973

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[thepastaclaw]

🕓 Ready for review — 57 ahead in queue (commit 9636331)
Queue position: 58/59 · 2 reviews active
ETA: start ~2026-09-06 11:08 UTC · complete ~2026-09-06 12:03 UTC (median 54m across 30 recent reviews; 2 slots)
Queued 5m ago · Last checked: 2026-09-05 09:30 UTC

[QuantumExplorer]

Closed by GitHub when a mistaken force-push briefly collapsed the stack's branches onto one commit. Replacement with the same branch and content: #4605.