test(platform-wallet): CR-001 — SPV mn-list sync readiness

[Claudius-Maginificent]

Issue being fixed or feature implemented

Implements CR-001 — SPV mn-list sync readiness per tests/e2e/TEST_SPEC.md (Status: PASS-pending-validation). Foundation for every other Core (CR) test — pins the SPV-readiness contract before any Core operation runs.

What was done?

• Added packages/rs-platform-wallet/tests/e2e/cases/cr_001_spv_mn_list_sync_readiness.rs.
• Registered cr_001 in cases/mod.rs alphabetically (before cr_003_*).
• Test waits ≤ 180 s for spv::wait_for_mn_list_synced, reads mn-list height, asserts > 0, asserts the SPV runtime reports started.
• Skips with informative log when PLATFORM_WALLET_E2E_DISABLE_SPV=1 (operator escape hatch).
• #[ignore]-tagged per repo convention; runs only with --ignored.

Spec divergence note

The spec entry mentions SpvHealth::status() -> Enum with a Ready variant. That accessor does not exist in the current codebase — the test uses SpvRuntime::is_started() == true as the available proxy, with an inline comment. Follow-up: either add SpvHealth::status() (small public API addition) or update the spec line to match is_started().

How Has This Been Tested?

• cargo build --tests --no-default-features — clean
• cargo build --tests — clean
• cargo clippy --tests --all-features -- -D warnings — clean
• cargo fmt --all -- --check — clean
• cargo test --test e2e cr_001 -- --list shows the test discoverable
• NOT run against testnet (testnet validation held while rust-dashcore docs: make more copy-pastable, and use proper markdown blocks #470 DKG cycle clears)

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 added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed (TEST_SPEC entry already exists at PASS-pending-validation; flipping to PASS happens after testnet green)

Related

• test(platform-wallet): e2e framework + full test suite — triage pins, Found-*/PA-* guards, fail-closed persist, Stage-2 merge #3549 — chain top, e2e framework
• test(platform-wallet): QA-V6→V26 fixes + parallelism contract #3609 — QA fixes V6→V20 cohort
• test(platform-wallet): CR-004 — legacy BIP32 UTXO update after spend (FAILING-by-design) #3613 — CR-004 FAILING-by-design test

_{🤖 Co-authored by Claudius the Magnificent AI Agent}

[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: defaults

Review profile: CHILL

Plan: Pro

Run ID: f854a35f-52af-48b9-95fc-78e870b87f7b

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/cr-001-spv-mn-list-readiness

---

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 and usage tips.}