feat(wasm-sdk): chained document queries with js-evo-sdk facade and suite coverage

[QuantumExplorer]

Issue being fixed or feature implemented

Final PR of the chained-document-queries stack (base: #4552). The JS surface for the provable semi-join — "posts I liked" in one verified round trip from the browser.

What was done?

wasm-sdk (src/queries/chained_document.rs, module precedent: document_ranked.rs):

• Typed ChainedDocumentsQuery / ChainedDocumentsResult TypeScript declarations.
• getChainedDocuments / getChainedDocumentsWithProofInfo on WasmSdk. The inner half reuses the documents query builder (where/orderBy in the familiar clause shape, innerLimit required); results are { innerDocuments, outerDocuments } arrays in inner-proof order. Always proof-verified — two grovedb proofs bound to one quorum-signed root, with the outer query re-derived from the proven inner values, so the node cannot steer the join.

js-evo-sdk:

• sdk.documents.chained(...) / chainedWithProof(...) facade methods.
• README section next to the refersTo docs it builds on, including the pagination recipe (inner keyset cursor on the join property).

platform-test-suite:

• Chained-query case in IndexOnlyDocument.spec.js, against the yappr contract the spec already registers: liked posts come back as full post bodies through the shared EvoSDK (createPlatformProofVerifier.getEvoSdkForNetwork, now exported), asserting both halves, inner order, and the identifier surface.

How Has This Been Tested?

• cargo check -p wasm-sdk --target wasm32-unknown-unknown clean; full yarn workspace @dashevo/wasm-sdk build (wasm-pack + bundle) succeeds and the generated .d.ts carries the new methods.
• yarn workspace @dashevo/evo-sdk build compiles against the regenerated types.
• Functional coverage runs with the suite against a local network (yarn test:suite on the IndexOnlyDocument spec); the underlying proof composition is unit/e2e-tested in the base PRs (rs-drive 7/7, drive-abci 4/4, dash-platform-queries 5/5).

Breaking Changes

None.

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

For repository code-owners and collaborators only

• 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: 7eb930a3-e493-4f52-8dc5-8b3e031f335d

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 — 34 ahead in queue (commit 72809ab)
Queue position: 35/36 · 2 reviews active
ETA: start ~16:37 UTC · complete ~17:41 UTC (median 1h 4m across 30 recent reviews; 2 slots)
Queued 4m ago · Last checked: 2026-08-31 22:20 UTC