feat(platform-wallet): watch-only rehydration from persistor (seedless load)

[Claudius-Maginificent]

Update — incremental v3.1-dev merge (2026-06-09)

Pushed 855471e6e8..2d22cf3e82. v3.1-dev advanced again (6fa4686..da9d3fe, now v4.0.0-beta.4); merged it up to keep the branch current. The prior merge already folded in 6fa4686, so the merge-base is exactly that commit — this was a small incremental merge of three disjoint shielded-pool PRs:

• feat: shielded scan-based spend detection and OVK outgoing-note history #3819 — shielded scan-based spend detection + OVK outgoing-note history
• feat: add IdentityCreateFromShieldedPool state transition (shielded-pool-funded identity creation) #3816 — IdentityCreateFromShieldedPool state transition
• chore(release): update changelog and bump version to 4.0.0-beta.4 #3822 — release bump → 4.0.0-beta.4

All three wallet overlap files (manager/mod.rs, error.rs, ffi/persistence.rs) auto-merged with zero conflicts, including preservation of the event_manager ungating against upstream's new shielded-sync edits (re-verified by a non-shielded cargo check -p platform-wallet canary). The only manual resolution was Cargo.lock (took upstream's beta.4 base, reconciled our secrets/rehydration deps without disturbing upstream pins). Wallet-scope gates all green: fmt, check, clippy ×2, cargo test -p platform-wallet-storage, plus platform-wallet default + shielded and platform-wallet-ffi. Behavioral risk ~10% — disjoint feature work, no signature breaks.

---

Update — comment compaction + v3.1-dev merge (2026-06-09)

Pushed b4a3aa9989..855471e6e8. Two changes since the last update; base retargeted to v3.1-dev (the old base feat/platform-wallet-sqlite-persistor / #3625 was squash-merged upstream and its branch deleted).

Comment compaction (coding-best-practices)

Swept the crate for the verbose prose that accumulated during the audit + remediation campaign: −1,319 net comment lines across 50 source + 19 test files. Proven comments-only (every changed file is code-byte-identical after stripping comments — zero behavioral change) and verified green (fmt, check, clippy ×2, tests incl. doc-tests). Kept: teaching public rustdoc, SAFETY: / INTENTIONAL: blocks, security "why" notes, external-quirk citations. Removed: tombstone/history narration, finding-ID changelogs, and multi-paragraph design essays (they live in git history / SCHEMA.md / SECRETS.md).

Merge origin/v3.1-dev

#3625 is now in v3.1-dev (squash-merged), so this brings the upstreamed base + the rest of the v3.1-dev payload (grovedb 4.0.0, dashcore, drive shielded-fees, dpp, getDocuments v1) into the branch. Resolution:

• rs-platform-wallet-storage/** — forced to our HEAD (the evolved superset; verified byte-identical). The pre-rename wallet_meta.rs stray was removed.
• rs-platform-wallet / -ffi — kept both additive sides (our serde_adapters + upstream shielded_*; rehydration FFI + birth-height exports; upstream fix(platform-wallet): zeroize private keys when freeing preview rows #3797 zeroize-on-preview-free).
• One semantic conflict fixed: upstream gated PlatformWalletManager.event_manager behind #[cfg(feature = "shielded")], but rehydration reads it unconditionally — ungated the field (genuinely-shielded fields stay gated); validated by building both feature configs.

Wallet-scope build gates pass (platform-wallet-storage no-default + all-features, rs-platform-wallet default + shielded, rs-platform-wallet-ffi). Full-workspace CI dispatched against the merged head to validate the disjoint upstream dep bumps.

---

Update — security audit + whole-crate review remediation (2026-06-09)

Pushed 9e1248cb0a..b4a3aa9989 (31 commits): a full security audit of the secrets/** subsystem plus a whole-crate review and remediation of platform-wallet-storage. All work is verified green; the on-disk SQLite format is unshipped so V001 was edited in place (no V002).

Secrets subsystem hardening (audit → fixes)

No CRITICAL/HIGH; the crypto core verified sound (fresh per-seal XChaCha20-Poly1305 nonces, tag-before-plaintext AEAD, Argon2id bounds-gated before allocation, zeroize+mlock wrappers). Fixes landed:

• Enabled argon2's zeroize feature (the multi-MiB KDF matrix + key-correlated intermediates were left un-wiped).
• Added a write-side per-secret size cap — the read path capped at 128 MiB but the write path did not, so an oversized secret could brick the whole shared vault on next open.
• Parent-directory permission check; folded the KDF header into the passphrase verify-token AAD; sealed PersistableBlob (no-key-material-in-DB enforced at the type level); converted production expect() → typed errors; added parser-fuzz + on-disk tamper tests; narrowed #![allow(unsafe_code)] to per-block with // SAFETY: notes; pinned fd-lock; acknowledged the bincode advisory.

Whole-crate review remediation — one CRITICAL fixed

• delete_wallet data loss (CRITICAL): a pre-flush BEGIN EXCLUSIVE cross-process lock race silently dropped the buffered changeset (one error path failed to restore the slot before returning). Fixed, and the regression test was adversarially mutation-verified (revert the fix → test goes red).
• MEDIUM: refuse a second in-process open() on the same path (AlreadyOpen); wallet-scope the identity tombstone (was cross-wallet); application_id / NotAWalletDb restore validation (foreign DB rejected, destination untouched); refinery-panic on malformed schema-history → typed SchemaHistoryMalformed; journal-mode read-back (silent WAL fallback); durability docs corrected (WAL+NORMAL is app-crash, not power-loss, durable); README / SCHEMA.md / SECRETS.md drift corrected to match shipped code; network-FS vault-lock caveat.
• LOW: fail-hard out-of-range sync watermark; deterministic UTXO account bucketing; centralized i64→u32 safe-casts; kv/blob size-limit unified; backup retention floor; CLI SQLITE_OPEN_URI removed; bincode RUSTSEC-2025-0141 acknowledged.

QA (all green): cargo fmt --all --check; cargo check + clippy under both --no-default-features --features sqlite,cli and --all-features (-D warnings); cargo test -p platform-wallet-storage → 380 passed / 0 failed. The CRITICAL fix and the new negative tests were adversarially mutation-verified.

---

Update — downstream-build hotfix: un-gate schema readers used by production load() (2026-06-08)

9e1248cb0a fixes a cfg-gating defect that broke this crate for downstream consumers building without __test-helpers. The production seedless Persister::load() path calls schema readers — schema::wallets::{fetch,parse_network}, identities::{load_state,managed_identity_from_entry}, the asset_locks reader cluster (decode_row, AssetLocksByAccount, imports), blob::decode_outpoint, identity_keys::{decode_entry, IdentityKeyWire::into_entry} — that the test-reconciliation merge (8ba49c37) left gated behind #[cfg(any(test, feature = "__test-helpers"))]. CI passed because --all-features / cargo test enable __test-helpers; a plain dependency build with --features sqlite,cli,secrets,kv (no __test-helpers) failed with 17 "function not found" errors.

Fix: un-gate exactly the readers reached from production load() — they live in the already-sqlite-gated schema module, so they compile precisely when load() does (no kv symbol pulled into a sqlite-only path, no DDL/V001 touched). One genuinely-dead asset_locks::list_active (zero callers, new at this rev) was gated instead, which keeps both clippy unions clean simultaneously. The in-memory changeset field cs.wallet_metadata is a different concept and is untouched.

QA (all green): cargo fmt --all --check; cargo check -p platform-wallet-storage --no-default-features --features sqlite,cli,secrets,kv (the downstream repro — 0 errors); clippy -p platform-wallet-storage under both --all-features and --no-default-features --features sqlite,cli (-D warnings); cargo test -p platform-wallet-storage → 339 passed / 0 failed.

---

Update — #3625 (storage crate + wallet_metadata→wallets rename) propagated in (2026-06-08)

Propagated the current #3625 tip (c9d1c81) into this branch via merge f69746d5 plus test-reconciliation 8ba49c37. Standard bottom-up parent-into-child propagation — #3625 is under review and is not modified; the new storage-crate work rides into the stack here.

What's new in this propagation:

• SQLite root table renamed wallet_metadata → wallets — disambiguates the root wallets table from the meta_* metadata family. Internal to platform-wallet-storage (SQL identifiers + the schema::wallets module, FK targets, both cascade triggers). The in-memory changeset domain field cs.wallet_metadata / WalletMetadataEntry / FFI on_persist_wallet_metadata_fn is a different concept and is deliberately untouched.
• Storage hardening (from a data-model/schema audit): dropped redundant idx_identity_keys_identity (left-prefix of the PK); renamed identities.wallet_index → identity_index (matches its source field); fixed the platform-address load count to count only reconstructed rows (+ regression test); corrected the migration-drift-fingerprint doc (it is intentionally content-blind to allow in-place V001 edits pre-release) and the CHECK-column counts in SCHEMA.md.
• Conflicts resolved: the two recurring stack conflicts KEEP-BOTH (rs-platform-wallet/src/changeset/mod.rs serde + shielded modules; rs-platform-wallet-ffi/src/manager.rs rehydration FFI + birth-height exports), plus 7 storage-crate conflicts and 2 semantic overlaps (an orphaned schema::wallet_meta→wallets reference in the new load() loop; behavioral test reconciliation against feat(platform-wallet)!: add platform-wallet-storage crate (sqlite persister) #3625's stricter schema).

QA (all green): cargo fmt --all --check; clippy -p platform-wallet-storage under both --all-features and --no-default-features --features sqlite,cli (-D warnings); clippy -p platform-wallet -p platform-wallet-ffi (-D warnings); cargo test -p platform-wallet-storage --all-features → 339 passed / 0 failed / 3 ignored; cargo test -p platform-wallet -p platform-wallet-ffi → 295 passed / 0 failed / 5 ignored.

Stack note (supersedes the older "review against #3672" note below): #3672 (secrets) is now merged. This PR's base is feat/platform-wallet-sqlite-persistor (#3625) — review the diff against #3625.

---

Update — latest #3625 propagated (2026-06-03)

Propagated the current #3625 tip (04662411cf, a chore: update Cargo.lock) into this branch via merge 3f2e7d2561 (parents 2f351903cd + 04662411cf). Fast-forward-clean; the delta is Cargo.lock only. The recurring stack-conflict files remain intact — rs-platform-wallet/src/changeset/mod.rs keeps all three feature-gated modules (serde_adapters + shielded_changeset + shielded_sync_start_state) and rs-platform-wallet-ffi/src/manager.rs keeps both the rehydration FFI and the birth-height exports.

---

Update — #3625 (carrying a v3.1-dev merge) propagated in (latest, 2026-06-03)

Merged the latest parent #3625 (feat/platform-wallet-sqlite-persistor, tip 31660906c2) into this branch (merge 2f351903cd). #3625 had just had v3.1-dev merged into it, so this is the bottom-up, parent-into-child propagation that keeps the stack reconciled:

• Incoming payload is pure v3.1-dev, disjoint from the wallet crates — 4.0.0-beta.2 version bumps, rs-platform-version v8/v12 method versions, rs-drive-abci shielded-pool gating, and the dashmate ZeroSSL-renewal fix. It reaches the wallet crates only transitively via dpp/drive. The merge was conflict-free, deleted zero files, and the wallet-storage schema/readers (migrations/V001__initial.rs, sqlite/schema/contacts.rs, sqlite/schema/identity_keys.rs, sqlite/schema/mod.rs) are byte-identical pre/post merge — so the silent-merge-defect class (a reader SELECTing a column an auto-merge dropped) cannot have fired.
• QA (Marvin) PASS: cargo fmt --check; cargo clippy -p platform-wallet-storage --all-targets --all-features -- -D warnings; cargo check -p platform-wallet-ffi (full dep graph recompiled against the bumped transitive crates — no API breakage from the version bumps); cargo test -p platform-wallet-storage → 334 passed / 0 failed / 3 ignored, incl. the item-G rehydration roundtrips (g_rt1/2/3, rt4), the unified-contacts lifecycle suite (tc_p4_004*), the schema guards (allowlist_accepts_every_known_table, contact_state_labels_match_enum), and sqlite_hardening_3625.

---

Update — #3625 contact-table unification merged in, reader reworked (latest, 2026-06-02)

Merged the latest #3625 (932b923b2b, CMT-003) into this branch (merge 052db80f12):

• Unified contacts table (one lifecycle-state row replacing contacts_sent / contacts_recv / contacts_established) now backs rehydration. The item-G contacts reader was reworked for the unified shape: load_state un-gated to production (no longer #[cfg(feature = "__test-helpers")]), with the load_changeset wrapper retained so the seedless load() still consumes a ContactChangeSet.
• No silent-merge defect. Independent QA (Marvin) re-checked the exact failure class that previously broke wallet-restore (a reader SELECTing a column the auto-merged schema had dropped): every contacts / identity_keys column the readers touch exists in V001, identity_keys keeps both wallet_id + derivation_blob, the meta_contact trigger fires on the unified contacts table, and all six meta_* tables + PER_WALLET_TABLES are reconciled. All feat(platform-wallet)!: add platform-wallet-storage crate (sqlite persister) #3625 hardening (CMT-001/002/004/005/006) is intact.
• All gates green: cargo fmt --check, clippy under --all-features and --no-default-features --features sqlite,cli (-D warnings), cargo check -p platform-wallet-ffi; 513 tests pass incl. item-G g_rt1/g_rt2/g_rt3 and the tc_p4_004* unified-contacts lifecycle suite.

---

Update — reconciled with #3625/v3.1-dev, #3735 removed, item-G verified (latest)

This branch was brought current with the base stack and cleaned up; #3693 (contacts + identity-key rehydration, item G) was folded in.

• Merged feat/platform-wallet-sqlite-persistor (feat(platform-wallet)!: add platform-wallet-storage crate (sqlite persister) #3625) + v3.1-dev. Brings the per-object metadata facility (meta_* tables + soft-cascade triggers), bincode outpoint encoding, the secrets review fixes, and v3.1-dev (Orchard genesis, dpp/drive updates). All feat(platform-wallet)!: add platform-wallet-storage crate (sqlite persister) #3625 fixes verified intact; no merge regression in either direction.
• Dead fix(platform-wallet): wallet_id gate on resolver-fed sign entrypoints #3735 wrong-seed-gate scaffolding removed. fix(platform-wallet): wallet_id gate on resolver-fed sign entrypoints #3735 (the FFI sign-time gate) was closed out-of-scope, so this drops the never-constructed PlatformWalletError::WrongSeedForDatabase, the never-imported subtle dep, and the false docs claiming a first-sign gate / seed-unavailable skip exist. The seedless watch-only load() performs no wrong-seed check by design; any sign-time gate is deferred FFI work, not this PR.
• Item-G (contacts + identity-key rehydration) is wired into load(). LOAD_UNIMPLEMENTED is reduced to core::last_applied_chain_lock; load() now calls the contacts + identity-key readers, so restored wallets recover their contacts/keys. A reconciliation-merge defect was caught and fixed — the identity_keys table had lost its wallet_id column relative to the reader (auto-merge artifact), breaking all rehydration; the table/writer/PER_WALLET_TABLES scope were reconciled and a dual-FK-cascade regression test (tc049_delete_wallet_cascades_identity_keys) added.
• iOS-style seedless model verified (grumpy-review): zero-seed load_from_persistor, watch-only wallet build (Wallet::new_watch_only), no SeedProvider/3-arg-resolver-at-load; signing stays on-demand via the MnemonicResolver vtable (private key never crosses FFI).

All gates green: cargo clippy under --all-features and --no-default-features --features sqlite,cli (-D warnings), plus the platform-wallet-storage + platform-wallet test suites (incl. the 6 item-G tests).

---

---

STACKED PR — review diff against feat/platform-wallet-storage-secrets (PR #3672), not v3.1-dev.

Merge order: #3625 (feat/platform-wallet-sqlite-persistor) → #3672 (feat/platform-wallet-storage-secrets) → this PR.

The wallet_id sign-gate that this PR's earlier iterations bundled has been extracted to PR #3735 (security patch targeting v3.1-dev directly). Land #3735 first; the standard merge-up cycle will pull the gate into this PR's lineage naturally.

---

Issue being fixed or feature implemented

After the SQLite persister landed (#3625), restarting the wallet app required a full re-scan from birth height — the DB held all the data but nothing reconstituted live wallets from it. This PR closes that gap.

The user story matches how the real iOS host works. The app launches with the Keychain locked. There is no seed in memory. The wallet UI needs to come back instantly with all balances, UTXOs, identities, and asset-lock state — without prompting the user to unlock — so they can see their funds, scroll their history, and decide whether to act. Only when they do act (sign a transaction, register an identity key) does the Keychain unlock and the seed arrive, gated to that one operation. This was validated against dashwallet-ios (swift-sdk-integration branch): loadFromPersistor() is zero-arg, called at app launch with locked Keychain; signing flows take the MnemonicResolverHandle vtable on demand.

The implementation reflects that: load is seedless and watch-only. Every persisted wallet comes back as Wallet::new_watch_only(...) — no key material derived, no signing capability, no seed touched. Wrong-seed detection moves to the sign path — covered by the companion security PR #3735 against v3.1-dev.

What was done?

Seedless watch-only load (rs-platform-wallet)

PlatformWalletManager::load_from_persistor() reconstructs each persisted wallet from the keyless ClientWalletStartState:

pub async fn load_from_persistor(&self) -> Result<LoadOutcome, PlatformWalletError>

For each wallet in the persisted wallets map, the manager:

• Builds an AccountCollection from the account_manifest: one Account::from_xpub(parent_wallet_id, account_type, account_xpub, network) per AccountRegistrationEntry.
• Constructs Wallet::new_watch_only(network, wallet_id, accounts) — key_wallet::WalletType::WatchOnly variant, no Mnemonic/Seed variant, no key bytes anywhere.
• Routes the keyless CoreChangeSet (UTXOs, tx records, IS-locks, sync watermarks) into the wallet via the existing apply_persisted_core_state(...) path, which correctly handles non-BIP44 topologies (CoinJoin-only / DashPay) via all_funding_accounts_mut() — the F2 silent-zero balance fix carries through.

A wallet whose persisted rows fail to decode is skipped, not silently mis-loaded. LoadOutcome.skipped carries (WalletId, SkipReason::CorruptPersistedRow { kind: CorruptKind }) where CorruptKind is MissingManifest | MalformedXpub | DecodeError(String). A PlatformEvent::WalletSkippedOnLoad { wallet_id, reason } fires per skip. One corrupt row never aborts the rest. The caller receives Ok(LoadOutcome) (non-empty skipped is success, not an error).

New schema readers

Item	Reader	Notes
A1	schema::accounts::load_state	Reads account_registrations + pools; decodes AccountRegistrationEntry; no Wallet built
B	schema::core_state::load_state	Bulk reconstructs ManagedWalletInfo — UTXOs, tx records, IS-locks, derived-address flags, sync watermarks, last_applied_chain_lock; routes UTXOs to the first funds-bearing account of any topology (no BIP44 assumption); no silent zero balance
A2	schema::asset_locks::load_unconsumed	Status-predicate reader excluding terminal Consumed rows at SQL level (WHERE status NOT IN ('consumed'))

FFI

// before — earlier iteration of this PR (now removed)
int32_t platform_wallet_manager_load_from_persistor(
    const PlatformWalletManagerHandle* manager,
    const PlatformWalletPersisterHandle* persister,
    const ResolverSeedProvider* resolver,
    LoadOutcomeFFI* out_outcome);

// after
int32_t platform_wallet_manager_load_from_persistor(
    const PlatformWalletManagerHandle* manager,
    const PlatformWalletPersisterHandle* persister,
    LoadOutcomeFFI* out_outcome);

The resolver arg is gone — load is purely watch-only. LoadOutcomeFFI surfaces loaded_count / skipped_count / skipped[] so the host can retry skipped wallets after a corruption-fix flow.

Swift wrapper

PlatformWalletManager.swift::loadFromPersistor() aligns to the new 2-arg + outparam C signature (passes nil for the outcome ptr — the iOS host doesn't surface skip reasons to the UI today).

No V002 migration

Every column required for this phase is in V001. No SQL migration is added.

Not in this PR

• Contacts and identity-keys rehydration — ClientWalletStartState has no contacts slot; wiring requires a changeset-shape change. Deferred to PR-3 (feat(platform-wallet): add contacts and identity-key rehydration (item G) #3693).
• Wrong-seed gate at sign-time — extracted to security PR fix(platform-wallet): wallet_id gate on resolver-fed sign entrypoints #3735 (targets v3.1-dev directly). Once merged + merge-up, the gate ships with this PR's lineage too.

How Has This Been Tested?

cargo fmt --all --check
cargo clippy -p platform-wallet -p platform-wallet-storage -p platform-wallet-ffi --all-targets -- -D warnings
cargo check --workspace
cargo test -p platform-wallet -p platform-wallet-storage -p platform-wallet-ffi
cargo test --doc -p platform-wallet -p platform-wallet-storage

Result: 410 tests passed, 0 failed, 8 ignored. Doctests: 3 passed, 0 failed, 1 ignored.

Targeted suite (packages/rs-platform-wallet/tests/rehydration_load.rs):

• RT-WO — persist N wallets, drop, reopen, load_from_persistor(); assert every wallet comes back as Wallet::WatchOnly with correct wallet_id, accounts, balances. No seed ever touched.
• RT-Corrupt — feed a corrupt manifest blob for one wallet; assert that wallet appears in LoadOutcome.skipped with CorruptPersistedRow, the other wallets load cleanly, exactly one PlatformEvent::WalletSkippedOnLoad fires.
• RT-Z — assert LoadOutcome, SkipReason, WalletSkippedOnLoad payloads carry no key material in Display or Debug.

Persister-side readers:

cargo test -p platform-wallet-storage --test sqlite_accounts_reader \
                                       --test sqlite_core_state_reader \
                                       --test sqlite_asset_locks_filter \
                                       --test sqlite_load_wiring \
                                       --test sqlite_load_reconstruction

13/13 tc_p4_* passes including corruption-is-hard-error variants.

Breaking Changes

This PR rewrites a load path that was added in earlier commits of this same PR (and has never shipped). There are no breaking changes against v3.1-dev. For reviewers tracking the in-PR evolution:

• PlatformWalletManager::load_from_persistor() no longer takes a &dyn SeedProvider (the trait itself was deleted — MnemonicResolverHandle is the on-demand contract).
• ClientWalletStartState no longer carries a Wallet field (assembled in the manager via Wallet::new_watch_only).
• FFI dropped the 3rd resolver arg from platform_wallet_manager_load_from_persistor.

No ! in the title because this is additive capability on an unreleased API — v3.1-dev carries none of the previous PR-internal shapes.

AR-7 hygiene

Load path eliminates AR-7 entirely — the manager never constructs WalletType::Mnemonic|Seed, only WalletType::WatchOnly (no key material). AR-7's residual Debug concern was about derived Wallet values on the load path; that path no longer derives.

Sign path keeps AR-7 discipline (Zeroizing + non_secure_erase()); the sign-time wallet_id gate that enforces it ships in PR #3735.

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

Note on the checklist item above: no ! in the title because no public API on v3.1-dev changes. The FFI signature change is internal to this PR branch (never released).

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

---

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

---

Rebuild note (2026-05-25): History rewritten to remove the sign-gate code that was extracted to PR #3735. The 5-commit minimal rework on top of the original PR-1 rehydration work yields a focused diff: watch-only load via Wallet::new_watch_only, FFI resolver-arg drop, Swift wrapper align. The sign-time wallet_id gate ships via #3735 against v3.1-dev.

[codecov]

Codecov Report

❌ Patch coverage is 87.02703% with 96 lines in your changes missing coverage. Please review.
✅ Project coverage is 87.18%. Comparing base (6fa4686) to head (855471e).
⚠️ Report is 3 commits behind head on v3.1-dev.

Files with missing lines	Patch %	Lines
...rs-platform-wallet-storage/src/secrets/file/mod.rs	82.31%	26 Missing ⚠️
...rm-wallet-storage/src/sqlite/schema/asset_locks.rs	48.83%	22 Missing ⚠️
...-wallet-storage/src/sqlite/schema/identity_keys.rs	64.28%	15 Missing ⚠️
...orm-wallet-storage/src/sqlite/schema/core_state.rs	85.22%	13 Missing ⚠️
...rs-platform-wallet-storage/src/sqlite/persister.rs	85.88%	12 Missing ⚠️
...es/rs-platform-wallet-storage/src/sqlite/backup.rs	93.54%	2 Missing ⚠️
...tform-wallet-storage/src/sqlite/schema/accounts.rs	90.00%	2 Missing ⚠️
...platform-wallet-storage/src/secrets/file/format.rs	99.23%	1 Missing ⚠️
...s/rs-platform-wallet-storage/src/secrets/secret.rs	95.45%	1 Missing ⚠️
...s-platform-wallet-storage/src/sqlite/migrations.rs	96.15%	1 Missing ⚠️
... and 1 more

Additional details and impacted files

@@              Coverage Diff              @@
##           v3.1-dev    #3692       +/-   ##
=============================================
+ Coverage     69.91%   87.18%   +17.27%     
=============================================
  Files            19     2661     +2642     
  Lines          2712   328679   +325967     
=============================================
+ Hits           1896   286569   +284673     
- Misses          816    42110    +41294     

Components	Coverage Δ
dpp	87.67% <ø> (∅)
drive	86.05% <ø> (∅)
drive-abci	89.50% <ø> (∅)
sdk	∅ <ø> (∅)
dapi-client	∅ <ø> (∅)
platform-version	∅ <ø> (∅)
platform-value	92.20% <ø> (∅)
platform-wallet	∅ <ø> (∅)
drive-proof-verifier	47.85% <ø> (∅)

🚀 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.