feat(masternodes): add Masternodes tab, retargeted onto platform-wallet rewrite

CHANGELOG.md

@@ -14,8 +14,38 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
   before. Each suggestion now shows a small label for its wallet and its
   type, and the field shows a hint listing the tags you can use when it's
   empty.
+
+- **Masternodes tab**: a new "Masternodes" entry in the left nav (visible when
+  Expert mode is on) for loading and managing masternode and evonode (HP
+  masternode) identities by ProTxHash. Loaded nodes appear as a card list
+  showing type, voter-key readiness, key status, and DPNS-voting status;
+  opening a card shows a detail view with inline DPNS contested-name voting,
+  Withdraw / Top up / Transfer actions, key management, and — for evonodes
+  only — a link to claim token rewards. The load form accepts an optional
+  password to encrypt the entered voting/owner/payout keys immediately
+  instead of only after a separate step; leaving it blank keeps today's
+  behavior, and protection can always be added later from the key screen.
+  This replaces loading a masternode or evonode from *Identities → Load
+  Existing Identity → Show Advanced Options*, which no longer offers those
+  identity types.
+
+- **Wallet/identity indicator on more screens (rollout in progress)**: the
+  wallet and identity picker previously shown only at the top of the Identity
+  Hub now also appears at the top of the Identities, DashPay, DPNS, and
+  Wallets screens. On the Identity Hub and the new Masternodes tab it's fully
+  interactive — you can change which wallet or identity you're acting as
+  right there. On the other four it's currently a read-only preview of your
+  active wallet/identity, with a tooltip on where to change it; making it
+  interactive there, and adding it to the remaining screens, is tracked as a
+  follow-up.
+
 ### Changed
 
+- **Masternode and evonode identities no longer appear in the Identity Hub or
+  Identities picker**: they now live exclusively on the new Masternodes tab,
+  so you're never offered actions (like registering a username) that don't
+  apply to a node's collateral/voting identity.
+
 - **Wallet balance breakdown is single-sourced**: the per-account tabs and the
   wallet header now derive every balance from one place. The Core header total
   and the Core per-account breakdown are read from the same generation of synced
@@ -108,6 +138,25 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ### Fixed
 
+- **Expert mode now reveals the Masternodes tab without a restart**: turning on
+  Expert mode in Settings immediately shows the "Masternodes" entry in the left
+  nav. Previously the Expert-mode flag was stored separately per network, so the
+  nav entry could stay hidden (reading a stale value on whichever network context
+  the app was showing) until the app was restarted. Expert mode is now a single
+  app-wide flag shared across all networks.
+
+- **Clearer error when loading a masternode by an unknown ProTxHash**: entering a
+  valid-looking but unregistered ProTxHash in the masternode load form now says no
+  masternode or evonode was found for that ProTxHash, instead of the misleading
+  generic "Identity not found — check the ID or name" message.
+
+- **Withdrawal key selection**: the Withdraw screen now pre-selects only a key
+  whose private key you actually hold (a payout/Transfer key preferred, Owner as
+  fallback). Previously it could pick a key that exists on the identity but whose
+  private key isn't loaded locally — common on loaded masternode/evonode
+  identities where only the Owner key was supplied — which made the withdrawal
+  fail at signing with an unhelpful technical error. When no usable key is
+  loaded, the screen guides you to add one instead of failing mid-withdrawal.
 - `WalletBackend` is now initialised eagerly at `AppState` start, eliminating a
   retry-loop spam on the SDK connection during cold boot.
 - Wallet store is rehydrated on cold start, resolving a regression where wallets

CLAUDE.md

@@ -77,7 +77,7 @@ Code lives by responsibility, not convenience:
 - **`backend_task/`** — async business logic, one submodule per domain; the authoritative enforcement layer. `TaskError` and its typed variants live in `backend_task/error.rs`.
 - **`database/`** — SQLite persistence, one module per domain.
 - **`context/`** — `AppContext` submodules (`*_db.rs`, lifecycle, settings, status).
-- **`wallet_backend/`** — the wallet orchestration seam: adapters, views, backend-side live caches, signers, the secret chokepoint, the event bridge. All wallet secret bytes (HD seed, imported single key, identity private key) enter/leave the vault through ONE chokepoint, `wallet_backend/secret_seam.rs` (raw `SecretBytes`, no DET-side serialization). Per-secret at-rest encryption is implemented via `put_secret_protected`/`get_secret_protected` (Argon2id + XChaCha20-Poly1305, per-secret object-password envelope, AAD bound to `wallet_id ‖ label`); unprotected secrets use `put_secret`/`get_secret` (raw, keyless vault). The keyless-vault residual (identity keys and no-password secrets) is the deferred tier. Design + migration: `docs/ai-design/2026-06-19-secret-storage-seam/`.
+- **`wallet_backend/`** — the wallet orchestration seam: adapters, views, backend-side live caches, signers, the secret chokepoint, the event bridge. All wallet secret bytes (HD seed, imported single key, identity private key) enter/leave the vault through ONE chokepoint, `wallet_backend/secret_seam.rs` (raw `SecretBytes`, no DET-side serialization). Per-secret at-rest encryption is implemented via `put_secret_protected`/`get_secret_protected` (Argon2id + XChaCha20-Poly1305, per-secret object-password envelope, AAD bound to `wallet_id ‖ label`); unprotected secrets use `put_secret`/`get_secret` (raw, keyless vault). Identity keys (imported/loaded, including masternode voting/owner/payout) enter unprotected (Tier-1 keyless) at load/creation time — the load flow has no password field — but can be sealed to Tier-2 per-identity afterward via `IdentityTask::ProtectIdentityKeys` (Key Info screen → "Add password protection…"; gated by vault-key scheme, not identity type). The keyless-vault residual is only no-password secrets and keys the user has not opted to protect. Design + migration: `docs/ai-design/2026-06-19-secret-storage-seam/`.
 - **`ui/<domain>/`** — screens (`ScreenLike`). UI may *call* `model/` validators for instant feedback but never implements its own validation.
 - **`ui/components/`** — reusable **Component-pattern widgets ONLY**: a `show()` plus a `ComponentResponse`, a display-only render widget, or component infrastructure. If it does not render egui, it is not a component.
 - **`ui/state/`** — non-widget UI state: per-screen view-models and async fetch-state caches (e.g. `TrackedAssetLockCache`). Owned by screens, may return `BackendTask`, render nothing.

Cargo.toml

@@ -132,6 +132,11 @@ name = "backend-e2e"
 path = "tests/backend-e2e/main.rs"
 required-features = ["testing"]
 
+[[test]]
+name = "mcp_http_auth"
+path = "tests/mcp_http_auth.rs"
+required-features = ["mcp"]
+
 [[bench]]
 name = "wallet_hydration"
 harness = false