Add Vesting CLI/exercise support and bump crypto deps for chain branch

[illuzen]

Summary

• Add full CLI support for the new treasury-funded Vesting pallet (info, list, show, claim, create-schedule, end-schedule, retarget), including --call-data-only for routing admin calls through the treasury multisig.
• Add a vesting phase to quantus exercise that covers all four extrinsics (permissionless claim, BadOrigin on create, create→claim→reclaim via Alice/Bob/Charlie treasury multisig, retarget→end with pot balance checks).
• Regenerate SubXT metadata from a Vesting-enabled runtime (spec 142 / tx 3) and allow that version pair in COMPATIBLE_RUNTIMES.
• Align crypto deps with chain branch chore/bump-crypto-deps-2026-08: poseidon 3.1.0, rusty-crystals 4.1.0, zk-circuits/wormhole 4.2.0 (crates.io), plonky2 1.5.5; temporarily path-depend on the chain’s qp-dilithium-crypto until a 4.x-compatible release is published.

Notes / follow-ups

• Upgrade exercise: already implemented (--upgrade-wasm), but not in the default phase set. Committing a bumped-spec compact.compressed.wasm (~700 KB) and wiring CI is a good next step; the blob must have a higher spec_version than the node under test.
• Publishability: qp-dilithium-crypto is still a path dep (crates.io 0.5.0 requires rusty-crystals 3.x). Switch to crates.io once a 4.x-compatible dilithium-crypto is published.
• Old runtime pairs (134–136) are still listed; bindings now hash-validate against the 142 metadata, so consider pruning them when nothing important still runs those versions.

Test plan

• cargo test --release --lib (236 passed)
• quantus vesting info / list against local Vesting-enabled node
• quantus exercise --phases vesting against local --dev node (7/7 steps)
• Full exercise suite against local node (vesting green; wormhole needs QUANTUS_BINS_DIR=./generated-bins when run from repo root)
• CI exercise workflow against chain main (or the vesting / crypto-bump branch) once those land
• Optional: quantus exercise --upgrade-wasm <bumped-spec.wasm> on a fast-governance node

[n13]

Verdict: REQUEST CHANGES — the latest head still has a broken supported-runtime path, deterministic test failures, and unsafe failure handling in the new exercise/vesting code.

Findings (highest severity first):

1. [P1] Default ML-DSA-65 wallets cannot transact on runtimes this CLI still declares compatible (src/config/mod.rs:17-20, src/cli/wallet.rs:48-50, src/chain/client.rs:350-368). Specs 134-136 expose the legacy one-variant signature enum (variant 0, ML-DSA-87), while this PR defaults newly created/imported wallets to ML-DSA-65 and encodes that as variant 1. The runtime gate accepts those nodes, wallet creation succeeds, and then every signed transaction from the default wallet is rejected as an undecodable signature. Either remove the old runtime pairs, retain ML-DSA-87 as the default until they are removed, or explicitly prevent ML-DSA-65 submission to pre-142 runtimes; cover the selected compatibility contract in tests.

2. [P1] The required test matrix is red at this head (src/cli/wormhole.rs:4541, src/cli/wormhole.rs:4655). The 4-bps change makes the medium fee result 9996, but the test still requires 9990. The new source-inspection guard also rejects the legitimate TransactionStage::Finalized normalization branch inside the _until submitters. SKIP_CIRCUIT_BUILD=1 cargo test --locked --lib cli::wormhole::tests:: reproducibly reports 35 passed / 2 failed, and the Ubuntu build-and-test CI job is now failed. Update both assertions so the checked-in suite validates the intended behavior and passes.

3. [P2] The wormhole exercise can leave a funded, empty-password wallet behind while hiding cleanup failures (src/cli/exercise/scenarios/wormhole.rs:30-52). Both delete_wallet results are discarded, and the funding transfer uses ? before cleanup is installed. A funding/watch error therefore bypasses deletion entirely; a deletion error after the command is also silently ignored. This can leave the deterministic exercise wallet (potentially holding the 500-token funding) on disk and make a later run fail with AlreadyExists. Run cleanup on every post-creation exit and propagate or log any deletion failure.

4. [P2] Relative vesting moments overflow instead of failing input validation (src/cli/vesting.rs:315-320). A syntactically valid large +<seconds> value performs unchecked seconds * 1_000 and now_ms + offset; it panics with overflow checks and wraps in release builds, producing unrelated call data/timestamps. Use checked_mul and checked_add and return an actionable QuantusError.

Validation:

• git diff --check 4ddb4ace...459d655 — passed.
• SKIP_CIRCUIT_BUILD=1 cargo clippy --all-targets --locked -- -D warnings — passed.
• SKIP_CIRCUIT_BUILD=1 cargo test --locked --lib cli::wormhole::tests:: — failed: 35 passed, 2 failed at lines 4541 and 4655.
• GitHub CI at 459d655: format, analysis/doc, and security-audit jobs passed; Ubuntu build/test failed; macOS and examples were still running at review time.

[n13]

Verdict: APPROVE — all four previously reported blockers are resolved on 85fd3bd.

• ML-DSA-65 support is now explicit per compatible runtime, and both shared CLI transaction submission paths reject ML-DSA-65 signers on legacy runtimes with an actionable error while leaving ML-DSA-87 usable.
• The two deterministic wormhole test failures are corrected.
• The exercise wallet is cleaned up on every post-creation exit, with run and cleanup failures both preserved.
• Relative vesting timestamps now use checked multiplication and addition and reject overflow.

Validation:

• git diff --check 4ddb4ace...85fd3bd — passed.
• SKIP_CIRCUIT_BUILD=1 cargo test --locked --lib cli::wormhole::tests:: — 37 passed.
• SKIP_CIRCUIT_BUILD=1 cargo test --locked --lib config::tests:: — 9 passed.
• SKIP_CIRCUIT_BUILD=1 cargo test --locked --lib cli::vesting::tests:: — 2 passed.
• SKIP_CIRCUIT_BUILD=1 cargo clippy --all-targets --locked -- -D warnings — passed.
• GitHub CI is green across format, Ubuntu/macOS build and test, analysis/doc, audit, and examples.

No remaining blocking findings.