feat(sdk): chained document queries — ChainedDocuments fetch with composed proof verification

[QuantumExplorer]

Issue being fixed or feature implemented

Third PR of the chained-document-queries stack (base: #4549). The Rust SDK surface for the provable semi-join: ChainedDocuments::fetch(&sdk, query) returns the liked posts (and the inner projections carrying the pagination cursor) with the single merged proof fully verified.

What was done?

• dash-platform-queries: ChainedDocumentQuery — a rich, transport-free query (inner DocumentQuery + join_property + outer type name). Encodes through the standard versioned GetDocumentsRequest encoder — typed V1 clauses, no CBOR anywhere on the surface — and attaches the ChainedJoin spec (a network still on the V0 wire is refused rather than silently sent a plain documents query); requires a non-zero inner limit; refuses inner features the chained surface doesn't support; always proves. Converts to DriveChainedDocumentQuery, and carries the concrete FromProof<ChainedDocumentQuery> impl: it decodes the response's proven_join_values (32-byte identifiers, fail-closed) as the untrusted bootstrap hint and runs the single-pass merged verification.
• rs-drive-proof-verifier: ChainedDocuments result type + verify_chained_documents_proof — the tenderdash-composition wrapper: merged-query reconstruction from the hint, single-pass verification, and exact set equality against the proven join values live in rs-drive; this wrapper binds the proof's root to the quorum-signed app hash and exists so the composition can never be skipped. Deliberately no unproven decoder with verification semantics.
• rs-sdk: Query wire-encoding impl + explicit identity Query<Self> impl, Fetch binding, MockResponse (per-document CBOR halves, list order preserved), mock expectation loading, platform::{ChainedDocumentQuery, ChainedDocuments} re-exports.
• The Fetch binding's Request is GetDocumentsRequest; no dedicated rpc exists anymore.

How Has This Been Tested?

Offline tests against the yappr-likes fixture (dash-platform-queries): wire-shape encoding pinning the typed V1 clauses and the riding join spec, required-limit and unsupported-inner-feature rejections, rich→drive conversion + shared shape validation (5/5). Proof verification is exercised end-to-end in rs-drive's chained_query_e2e_tests (including the hint-tamper matrix) and rs-drive-abci's handler tests. Devnet test vectors can be generated with generate_test_vectors.sh once a local network is up — follow-up.

cargo check --workspace --all-targets, cargo fmt, grpc-coverage gate.

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: e759e38e-b495-449b-bebf-102706c695e6

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 — 32 ahead in queue (commit 9400531)
Queue position: 33/34 · 2 reviews active
ETA: start ~17:23 UTC · complete ~18:27 UTC (median 1h 4m across 30 recent reviews; 2 slots)
Queued 1m ago · Last checked: 2026-09-01 00:10 UTC

[codecov]

Codecov Report

❌ Patch coverage is 0% with 68 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.97%. Comparing base (ff0a7b9) to head (9400531).
⚠️ Report is 1 commits behind head on v4.2-dev.

Files with missing lines	Patch %	Lines
...rm-queries/src/documents/chained_document_query.rs	0.00%	44 Missing ⚠️
...drive-proof-verifier/src/proof/chained_document.rs	0.00%	24 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (50.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##           v4.2-dev    #4552      +/-   ##
============================================
- Coverage     87.29%   86.97%   -0.33%     
============================================
  Files          2753     2786      +33     
  Lines        358390   362680    +4290     
============================================
+ Hits         312855   315434    +2579     
- Misses        45535    47246    +1711     

Components	Coverage Δ
dpp	88.62% <ø> (+0.24%)	⬆️
drive	85.71% <62.50%> (-0.07%)	⬇️
drive-abci	89.73% <91.93%> (-0.08%)	⬇️
sdk	∅ <ø> (∅)
dapi-client	∅ <ø> (∅)
platform-version	∅ <ø> (∅)
platform-value	92.92% <ø> (ø)
platform-wallet	∅ <ø> (∅)
drive-proof-verifier	40.82% <0.00%> (-7.82%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.