Update snarkVM to v4.9.1

[iamalwaysuncomfortable]

Summary

Updates all ten snarkvm-* dependencies from 4.9.0 to 4.9.1 (crates.io) and bumps the package versions to 0.11.7, following the same shape as #1387.

What v4.9.1 brings

snarkVM v4.9.1 introduces ConsensusVersion::V19 (per-transaction deployment limits, keeping the block-wide synthesis limit on the first V19 block) and bumps lru to 0.18.2 — the only non-snarkvm lockfile churn here (lru 0.16.3 → 0.18.2, pulling in hashbrown 0.17.1).

Consensus-version count

NUM_CONSENSUS_VERSIONS goes 18 → 19, so every copy of the consensus-heights CSV is extended by one value (the same set of sites #1387 converged on):

• sdk/tests/wasm.test.ts and the test_set_genesis_block_non_zero_fails input in wasm/src/utilities/mod.rs
• the getOrInitConsensusVersionTestHeights doc example in wasm/src/utilities/mod.rs
• the JSDoc examples in sdk/src/program-manager.ts and their docs/api_reference mirror
• create-leo-app/template-devnode-js/index.js

No wasm source changes are needed: the manager code only compares consensus versions relationally (< V9, < V14) and already delegates Varuna selection to snarkVM's varuna_version_from_consensus.

Testing

• yarn build:all succeeds on both networks
• yarn test:wasm: 204 passed, 0 failed
• yarn test:sdk: 1083 passing, 49 pending; the 6 failures are RecordScanner encrypted-registration tests that hit the live api.provable.com/scanner endpoint and fail Unauthorized without API credentials — unrelated to this change
• RUN_SKIPPED=true mocha tmp/**/wasm.test.js --grep Consensus: the 19-height list is accepted end-to-end on both testnet and mainnet builds

---

Note

Medium Risk
Touches core proving and verification in WASM (Varuna selection); behavior matches mainnet/testnet today but changes devnets below consensus V4. Dependency bump across the whole monorepo adds release-wide regression surface.

Overview
Bumps @provablehq/sdk / @provablehq/wasm and create-leo-app to 0.11.7, pins all snarkvm-* crates to 4.9.1 (including lru 0.18.2 via the lockfile), and aligns workspace templates, e2e packages, docs, and yarn lock with the new SDK.

For snarkVM v4.9.1’s 19th consensus version, every devnode getOrInitConsensusVersionTestHeights example and test CSV gains one more height (…,18), including wasm utilities tests and sdk JSDoc mirrors.

WASM proving/verification no longer hardcodes VarunaVersion::V2 where a block height is available: execute_inner, offline prove paths, join/split/transfer, execute_fee!, and verifyFunctionExecution now use varuna_version_from_consensus after resolving CONSENSUS_VERSION. Standalone snarkVerify / batch verify stay on V2 because no chain height is in scope.

^{Reviewed by Cursor Bugbot for commit dde578e. Bugbot is set up for automated code reviews on this repo. Configure here.}

Derive the Varuna version wherever a height is known (065fc6e)

Comparing the manager against snarkVM's synthesizer/process and synthesizer/src/vm surfaced that only execute_authorization_inner derived its Varuna version via varuna_version_from_consensus — every other proving/verification site hardcoded VarunaVersion::V2 despite having the block height in hand. This PR now derives it in execute_inner, join, split, transfer, the execute_fee! macro, and verifyFunctionExecution. Equivalent on mainnet/testnet today (consensus ≥ V4 → Varuna V2); matters on devnets pinned below consensus V4 and future-proofs against a VarunaVersion::V3 upstream. Intentional hardcodes remain in executeFunctionOffline (no height in scope) and snarkVerify/snarkVerifyBatch (raw proofs, no chain height).

Re-ran yarn build:all and yarn test:wasm after the change: 204 passed, 0 failed.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 065fc6e. Configure here.}