chore: bump miden-client to 0.16.0-rc.3 and web SDK to 0.16.0-rc.5

[zeljkoX]

Why

Devnet is running miden-node 0.16.0-rc.3. Node rc.2 changed the RPC AccountResponse storage-map proof format to a batched PartialSmt (miden-node #2439), and miden-client 0.16.0-rc.3 is the release that speaks it (rust-sdk #2360). Our pinned miden-client 0.16.0-rc.2 is therefore mismatched against devnet. The web SDK 0.16.0-rc.5 release bundles that same client rc.3.

The protocol line did not move: miden-protocol / miden-standards / miden-tx stay at =0.16.0-rc.6, and web SDK rc.5's WASM embeds miden-protocol-0.16.0-rc.6 / miden-client-0.16.0-rc.3 / miden-crypto-0.29.4. No MASM, procedure-root, or tx-summary changes.

What

• Cargo.toml: miden-client, miden-client-sqlite-store, miden-node-proto-build to =0.16.0-rc.3.
• Cargo.lock: VM/crypto stack (miden-crypto, -core, -assembly, -processor, -prover, -verifier) 0.29.1 to 0.29.4, matching the web SDK WASM. Also picks up the single-threaded WASM prove hang fix (miden-vm #3722).
• @miden-sdk/miden-sdk to 0.16.0-rc.5 in packages/miden-multisig-client and the four browser examples; workspace and example lockfiles regenerated.
• Docs: MIDEN_COMPATIBILITY.md support matrix, MULTISIG_SDK.md and miden-multisig-client/README.md install snippets.

Guardian uses none of the Rust types that changed shape in client rc.3 (StorageMapEntries, SyncedNote, NoteObserver); our own miden-rpc-client::get_account_details has no callers. Web SDK rc.3 to rc.5 has no breaking TS API changes; the newLocalProver() Poseidon2 change does not affect us (we only use newRemoteProver / deserialize).

Verification

• cargo build --workspace --all-targets clean.
• cargo test -p miden-multisig-client -p miden-rpc-client -p guardian-client all pass, including procedure_roots_are_valid and procedure_roots_match_upstream_component.
• npm test -w miden-multisig-client: 42 files, 490/490 pass, including procedure-roots.test.ts and the Rust-built-account round-trip.
• Not yet run: a smoke-web pass against devnet, which is what exercises the node rc.3 RPC pairing this fixes.

Follow-up

Release bump to 0.17.0-rc.2 is intentionally left for a separate chore(release) PR, matching #426 / #392. That PR should add an rc.2 row to the compat matrix and restore the rc.1 row to miden-client =0.16.0-rc.2 / web SDK 0.16.0-rc.3, which is what rc.1 actually shipped with.

Summary by CodeRabbit

• Documentation

  • Updated compatibility guidance and multisignature quick-start instructions to reference the latest SDK release candidates.
  • Refreshed installation examples and package documentation with current version information.

• Chores

  • Updated SDK versions used by browser, web, and multisignature examples.
  • Aligned project components with the latest compatible release candidates for improved consistency.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c81276ae-c7aa-4c66-8bc1-6c468d78325f

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

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cfdd0e57-8f4e-424a-949b-f9c4d8c57b0c

📥 Commits

Reviewing files that changed from the base of the PR and between 6888e19 and eba054e.

⛔ Files ignored due to path filters (6)

• Cargo.lock is excluded by !**/*.lock
• examples/_shared/multisig-browser/package-lock.json is excluded by !**/package-lock.json
• examples/operator-smoke-web/package-lock.json is excluded by !**/package-lock.json
• examples/smoke-web/package-lock.json is excluded by !**/package-lock.json
• examples/web/package-lock.json is excluded by !**/package-lock.json
• packages/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (9)

• Cargo.toml
• docs/MIDEN_COMPATIBILITY.md
• docs/MULTISIG_SDK.md
• examples/_shared/multisig-browser/package.json
• examples/operator-smoke-web/package.json
• examples/smoke-web/package.json
• examples/web/package.json
• packages/miden-multisig-client/README.md
• packages/miden-multisig-client/package.json

Included review availability: 3 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

Walkthrough

The pull request updates Miden Rust and npm dependency pins. It also updates compatibility documentation, multisig SDK instructions, example packages, and multisig client metadata to reference the corresponding release candidates.

Changes

Miden dependency version alignment

Layer / File(s)	Summary
Dependency and documentation pins Cargo.toml, docs/..., examples/..., packages/miden-multisig-client/...	Rust dependencies now use the specified rc.3 versions. npm packages, compatibility data, examples, and multisig documentation now use 0.16.0-rc.5.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to eba05

This PR aligns the Rust and web SDK versions with the stated devnet protocol pairing, and the listed build and test checks pass. No actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: haseebrabbani

Poem

A rabbit checks each version pin,
Rust and npm now match within.
The docs hop forward, examples too,
Multisig paths wear releases new.
“All aligned!” the rabbit sings.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary changes: the Rust Miden client dependencies and web SDK are bumped to the versions reflected in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (9 skipped: 9 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/miden-client-rc3-web-sdk-rc5

---

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