diff --git a/CHECKPOINT-encryption.md b/CHECKPOINT-encryption.md
index da13251..86dda29 100644
--- a/CHECKPOINT-encryption.md
+++ b/CHECKPOINT-encryption.md
@@ -1,27 +1,1447 @@
-# Checkpoint — fix profile delete/undo + themed auto-dismiss bar (2026-08-27)
+# Checkpoint — nostr stack 0.45 security migration (2026-08-25)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
 
 ## Where things are
+
 - Project: `/home/avi/Projects/Nostr_Keynctr`
-- Git repo: `master` @ `9e635e7` ("fix: restore profile delete/undo and themed auto-dismiss undo bar"). Before it: `56c2a6d` (checkpoint: click profile row), `8130c3e` (click profile row on Home), `a5838ea`, `98f4520` etc.
-- Working tree: clean except `KeynectrAppIconPossibility02.jpeg` untracked (long-standing, not part of commits).
+- Git repo: `master` @ `8130c3e` ("frontend: click a profile row on Home to
+   select it"). Before it: `98f4520` (active-profile picture on Compose +
+   sidebar), `f534165` (remove Profiles sidebar tab), `835b0a0` (list all
+   profiles on Home, pin dev host, widen card), `5635f79` (checkpoint),
+   `71e580f` (Trim white margins), `f29d4f9` (Checkpoint 0.45 migration),
+   `fa5ba08` (Security: upgrade nostr stack 0.40->0.45), `bf10ae3`, `e210f17`,
+   `7098e75`, `e6a1efc`, `6d5063d`, `1c428a9`.
+- Working tree: still DIRTY with the long-standing user changes — `concept3.svg`
+   deleted, `KeynectrAppIconPossibility02.jpeg` untracked. These are NOT part
+   of the frontend commit above and remain uncommitted.
 
 ## What was completed
-1. **Fixed broken profile delete/undo.** `src/ipc.rs` was missing `DeleteProfile`/`UndoDelete` request variants and handlers, so `delete_profile` from renderer returned `Unexpected signer request`. Added `DeleteProfile {npub}`/`UndoDelete` to `Request`, handlers that call `profiles::delete_profile`/`app.undo_delete()`, save vault, push/pop `undo_history`, return `state_view()`. Exposed `profiles::delete_profile` outside `#[cfg(test)]` (was only inside tests). Updated `src/profiles.rs` accordingly. CLI `delete_profile_direct` kept for `main.rs`.
-2. **Wired frontend to backend state.** `frontend/src/lib/api.ts`: `deleteProfile`/`undoDelete` now `call<AppState>` (was `ProfileSummary`). `frontend/src/state/AppProvider.tsx`: both now use `applyState(...)` and type `Promise<AppState>`; added `clearLastDeleted` that locally slices `undo_history` for UI dismissal.
-3. **Themed auto-dismiss undo bar.** `frontend/src/screens/ProfilesScreen.tsx`: replaced permanent white bar (`var(--token-item-bg, #f0f0f0)` + "Profile deleted. You can restore it until you delete another or quit.") with themed bar (`var(--primary-soft)` bg, `var(--border)` border) showing `Profile "X" deleted. — Undo and restore profile` where the link uses `var(--primary)` (adapts to light/dark/neon/glass). Bar appears in both empty and populated states, auto-dismisses after 5s via `useEffect` watching `lastDeleted` (previous version fired unconditionally on mount). Fake backend updated to simulate delete/undo for tests.
 
-## Commits added in this session (newest first)
-- `9e635e7` fix: restore profile delete/undo and themed auto-dismiss undo bar
+1. **Security migration of the Nostr stack (`fa5ba08`).** `cargo audit` was
+   installed on this machine (`cargo install cargo-audit`, v0.22.2) and its
+   first scan found **11 RustSec vulnerabilities** in nostr 0.40 /
+   relay-pool 0.40.1 — including forged-event signature-bypass (0224),
+   NIP-46 credential Debug leak (0225), and auth-challenge memory
+   exhaustion (0231). Upgraded to `nostr 0.45.3` + `nostr-sdk 0.45.2`
+   (secp256k1 0.30), clearing every vulnerability and all 4 warnings.
+   Code adaptations: `Client::builder().authenticator(SignerAuthenticator)`
+   replaces implicit signer (NIP-42 auto-auth stays working); signing moved
+   from `EventBuilder::sign` to `finalize_async`; nip44 encrypt now takes an
+   explicit random nonce (getrandom); feed + signer receive loops moved to
+   `stream_events` (signer's notification stream still opens BEFORE the
+   announce, preserving the ordering fix); contact p-tags parsed via
+   `single_letter_tag()`; `relay()` returns Option; `try_connect().timeout()`.
+   Dropped unused `nip46` feature (signer is hand-rolled). Dry-run first:
+   bump-only build proved zero dependency-crate failures / no MSRV issues;
+   all 24 errors were exactly the planned API edits.
+2. **New regression tests (+2, suite now 115).** Malformed NIP-44 payloads
+   (not-base64, empty, truncated, bad version byte) reject cleanly with no
+   panic; error strings never contain secret-key material (0225 class).
+3. Earlier today: R3 modal-save dedup (`7098e75`) completing the DRY audit,
+   NIP-42 clarification docs (`bf10ae3`).
+
+## Commits added most recently
+
+- `8130c3e` frontend: click a profile row on Home to select it
+- `98f4520` frontend: show active-profile picture on Compose and sidebar
+- `f534165` frontend: remove redundant Profiles sidebar tab
+- `835b0a0` frontend: list all profiles on Home, pin dev host, widen profiles card
+- `fa5ba08` Security: upgrade nostr stack 0.40->0.45 clearing 11 RustSec advisories
 
 ## Verification commands run (all green)
-- Rust: `cargo fmt --check` clean; `cargo clippy --all-targets` 2 pre-existing warnings; `cargo test` 115 passed; `cargo build --release` success
-- Frontend (`frontend/`): `npm run typecheck` clean; `npm run lint` clean; `npm run format:check` clean (after `npm run format`); `npm test` 15 files / 99 tests passed; `npm run build` success; `npm run electron:build` success
-- The `--ozone-platform=wayland` Vulkan and `has no handler with id` messages seen on `electron:build` are harmless Electron/Wayland warnings, not profile errors.
 
-## How to resume / reproduce
-GUI: `cargo build --release && cd frontend && npm run build && npm run electron:build && npm start` (or `npm run dev`). Create 2 profiles, delete one via Profiles → Delete → confirm, see themed undo bar for 5s with "Undo and restore profile" in primary color, click it to restore, or wait for auto-dismiss.
-CLI: `cargo run -- delete-profile <npub>` then `cargo run -- undo-delete` (in-memory undo only within same `serve` session; CLI undo across processes is not persisted).
+Rust (repo root): cargo fmt --check clean; cargo clippy --all-targets only
+the two pre-existing profiles.rs warnings; cargo test 115 passed (release
+mode re-run too); cargo build --release success.
+Frontend (`frontend/`, untouched): typecheck clean; format:check clean;
+npm test 15 files / 99 tests; vite build success; electron:build success.
+Live: probe built on 0.45 stack published kind-1 notes accepted by
+wss://soloco.nl and wss://relay.primal.net within the 6 s watchdog.
+Pre-commit audit per user protocol: staged diff = Cargo.toml/Cargo.lock/src
+only; git diff --check clean.
 
-## Outstanding / next-step items
-- Undo restores profile with empty `secret_key` (`StoredProfile { secret_key: "" }`) — existing design stores `ProfileSummary` in `undo_history` so secret cannot be recovered. Needs full `StoredProfile` in undo stack if secret preservation is required.
-- `KeynectrAppIconPossibility02.jpeg` remains untracked; `concept3.svg` deletion already committed earlier.
+## How to use / reproduce
+
+No user-facing change. Rebuild + restart to pick up the new backend:
+
+```bash
+cd ~/Projects/Nostr_Keynctr && cargo build --release
+cd frontend && npm run build && npm start
+```
+
+Re-check Updates card: Rust advisory section should now list no
+vulnerabilities (cargo-audit is installed machine-wide).
+
+## Notes & next steps
+
+- wss://nostr.l484.com had a DNS-resolution blip at the very end of the
+  session (gaierror for ~a minute); it worked earlier today including a
+  stored test event. If it stays down, check the relay host — not app code.
+- Probe harnesses live in /tmp/opencode (nip42-probe on 0.45; python raw
+  readers). Copy into scripts/ if they should survive reboots.
+- Pre-existing clippy warnings in src/profiles.rs remain untouched by request.
+- Relay health today: nos.lol 502 intermittent, nostr.wine 403,
+  l484.com transient DNS failure at session end, nostr.band unreachable;
+  primal/mom/soloco healthy.
+
+---
+
+# Older checkpoint — DRY modal save lifecycle / R3 complete (2026-08-25)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `7098e75` ("refactor: share modal save lifecycle").
+  Before it: `e6a1efc` (refactor: share hex-id shortening in lib/format),
+  `ec237bf` (Checkpoint: relay pool bootstrap), `6d5063d`
+  (refactor: share relay pool bootstrap), `1c428a9` (DRY fan-out R1),
+  `b21678f` (signer-fix checkpoint), `64ad94d` (NIP-46 handshake fix).
+- Working tree after this checkpoint commit: only the long-standing user
+  changes remain — `concept3.svg` deleted and
+  `KeynectrAppIconPossibility02.jpeg` untracked, exactly as the user had them.
+
+## What was completed
+
+1. **R3 modal save-lifecycle dedup (`7098e75`).** The three profile modals in
+   `frontend/src/screens/ProfilesScreen.tsx` (Picture, Rename, NIP-05) each
+   carried an identical ~20-line async save lifecycle. Now a single
+   module-local `runModalSave` helper owns it: clear error → set saving →
+   claim publishing slot (`onSavingChange(npub)`) → run API → build success
+   message from the publish report → report via `onSaved`, or on failure
+   surface the error via `onError` → always release saving state and the slot
+   in `finally`. Each modal keeps only what is genuinely its own: the API call,
+   its success-message logic inline (including NIP-05's set/removed branch),
+   and RenameModal's `canSave` guard outside the helper. No user-facing change:
+   callback order, messages, buttons, props, and tests untouched.
+   With this, all four DRY-audit items (R1–R4) are complete.
+2. Earlier: R4 hex-id shortening (`e6a1efc`), R2 relay-pool bootstrap
+   (`6d5063d`), R1 fan-out dedup (`1c428a9`) — details in the older checkpoints
+   below.
+
+## Commits added most recently
+
+- `7098e75` refactor: share modal save lifecycle
+
+## Verification commands run (all green)
+
+Rust (repo root): cargo test 113 passed; cargo clippy --all-targets finished
+(pre-existing profiles.rs warnings only); cargo fmt --check clean;
+cargo build --release success.
+Frontend (`frontend/`): npm test 15 files / 99 tests passed; typecheck clean;
+lint clean; format:check clean; npm run build success; electron:build success.
+Pre-commit audit per user protocol: staged diff contained only
+ProfilesScreen.tsx; git diff --check clean; nothing else staged.
+
+## How to use / reproduce
+
+No user-facing change. Profiles → Picture / Edit name / NIP-05 modals behave
+exactly as before; any future change to the shared save policy happens in one
+place: `runModalSave` in `frontend/src/screens/ProfilesScreen.tsx`
+(just above `Nip05Modal`).
+
+## Notes & next steps
+
+- **NIP-42 status clarified (2026-08-25 addendum).** Earlier notes saying
+  "l484.com needs NIP-42 auth" described *raw probes* that don't answer
+  challenges — not a Keynectr gap. Verified: nostr-sdk 0.40 attaches the
+  signer in `Client::new` and enables NIP-42 auto-authentication by default
+  (`nip42_auto_authentication: true`), so AUTH challenges on read AND write
+  are answered automatically on every Keynectr path. Live test against
+  `wss://nostr.l484.com` replicating Keynectr's exact client setup: event
+  accepted in 0.3 s (inside the 6 s `RELAY_SEND_TIMEOUT`) and retrievable
+  afterwards. Known edge, left as-is by choice: the SDK's worst-case auth
+  dance (~7 s wait + resend) can exceed the 6 s watchdog on a very slow
+  authed relay → "did not respond in time"; healthy relays finish in <1 s.
+  Probe harness: `/tmp/opencode/nip42-probe` (throwaway key, same crates).
+- DRY audit items R1–R4 are all complete; nothing left on hold from that list.
+- Pre-existing clippy warnings in src/profiles.rs remain untouched by request.
+- Relay health today: nos.lol 502 (intermittent), nostr.wine 403,
+  l484.com sends NIP-42 AUTH challenges but works fine with Keynectr
+  (auto-answered — see addendum above), nostr.band unreachable;
+  primal/mom/soloco healthy.
+- Client visibility rule of thumb confirmed today: a note appears only on
+  clients whose read relays overlap the relays it was published to; if a
+  note "is missing" somewhere, first compare relay lists (Primal indexes
+  broadly; Iris/Yakihonne read narrower sets).
+
+---
+
+# Older checkpoint — DRY hex-id shortening (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `e6a1efc` ("refactor: share hex-id shortening in lib/format").
+  Before it: `ec237bf` (Checkpoint: relay pool bootstrap), `6d5063d`
+  (refactor: share relay pool bootstrap), `1c428a9` (DRY fan-out R1),
+  `b21678f` (signer-fix checkpoint), `64ad94d` (NIP-46 handshake fix),
+  `dd50b24` (Aurora rename).
+- Working tree: clean apart from this checkpoint update. `concept3.svg` deleted
+  and `KeynectrAppIconPossibility02.jpeg` untracked remain as the user had them.
+
+## What was completed
+
+1. **R4 hex-id shortening (`e6a1efc`).** Exported `shortHexId` from
+   `frontend/src/lib/format.ts` with verbatim logic from the former local
+   `shortHex` in `SignerScreen.tsx`; SignerScreen now imports and calls
+   `shortHexId`; added `format.test.ts` with 7 focused tests (empty, len 16,
+   len 17, 64-hex, shortenNpub disabled, enabled truncation). Output behavior
+   is byte-identical: >16 uses first 8 chars + Unicode ellipsis U+2026 + last 8,
+   ≤16 passes through unchanged. Does not reuse `shortenNpub`; preserves
+   existing visual output exactly per audit constraint.
+2. **R2 DRY refactor (`6d5063d`).** New `relays::open_pool(keys, urls,
+   wait: Option<Duration>) -> Result<Client>` is the single pool-construction
+   path (add each relay with strict error propagation, connect, optional
+   wait). Adopted by feed's two fetchers (`Keys::generate()` + 10 s wait) and
+   note publishing (`keys.clone()`, no wait). `profiles.rs` intentionally NOT
+   adopted — its unique ignore-add-errors policy stays local; it regained an
+   explicit `connect()` when `send_to_all_relays` dropped its internal one
+   (avoids double-connect on the note path). `signer.rs` deliberately
+   untouched: ordering-critical notification setup + fail-to-status error model.
+   Net −20 lines; behavior, error strings, timing unchanged.
+3. Earlier this session: R1 fan-out dedup (`1c428a9`), NIP-46 handshake fix
+   (`64ad94d`), Aurora rename + dropdown fix (`dd50b24`), frosted-glass look
+   (`ecb666b`), glass build fix (`bfe14f0`).
+
+## Commits added most recently
+
+- `e6a1efc` refactor: share hex-id shortening in lib/format
+- `6d5063d` refactor: share relay pool bootstrap
+
+## Verification commands run (all green)
+
+Rust: cargo test 113 passed; clippy only pre-existing profiles.rs warnings;
+fmt clean; release binary rebuilt.
+Frontend (untouched): npm test 99; typecheck, lint, format, electron:build,
+vite build all clean.
+Pre-commit audit per user protocol: git diff --check clean; signer.rs empty
+diff; 3 test files added (format.test.ts with 7 new tests).
+
+## How to use / reproduce
+
+No user-facing change. Future connection-policy work (e.g., NIP-42 auth for
+nostr.l484.com, retries) now starts in `relays::open_pool`.
+
+## Notes & next steps
+
+- Remaining DRY items by user request on hold: R3 (modal save-lifecycle hook).
+- R4 (shortHex vs shortenNpub) is complete: shared `shortHexId` in lib/format,
+  output preserved exactly, tests green.
+- Relay health today: nos.lol 502, nostr.wine 403, l484.com needs NIP-42 auth,
+  nostr.band unreachable; primal/mom/soloco healthy.
+---
+
+# Older checkpoint — DRY relay fan-out (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `1c428a9` ("DRY: single parallel relay fan-out for notes
+  and metadata"). Before it: `64ad94d` (NIP-46 handshake fix), `b21678f`/
+  `ae84526` (checkpoints), `dd50b24` (Aurora rename).
+- Working tree: clean apart from this checkpoint update. `concept3.svg` deleted
+  and `KeynectrAppIconPossibility02.jpeg` untracked remain as the user had them.
+
+## What was completed
+
+1. **R1 DRY refactor (`1c428a9`).** The parallel relay send block (~55 lines:
+   JoinSet per-relay sends, 6 s timeout, indexed outcome collection,
+   disconnect, succeeded/failed split) existed twice — in
+   `publish.rs::publish_with_keys` and `profiles.rs::publish_metadata_async`.
+   Now one `pub(crate) publish::send_to_all_relays(client, urls, event, noun)`
+   serves both; callers keep their distinct add-relay policies (note path
+   aborts on add errors, metadata ignores them) so behavior, error strings,
+   and public APIs are unchanged. Removed duplicate constant
+   `METADATA_SEND_TIMEOUT`, dead helper `failure_for`. Net −49 lines.
+2. Deliberately NOT done (pending approval): R2 shared client-bootstrap
+   helper, R3 modal save-lifecycle hook (frontend), R4 shortHex/shortenNpub.
+
+## Commits added most recently
+
+- `1c428a9` DRY: single parallel relay fan-out for notes and metadata
+
+## Verification commands run (all green)
+
+Rust: cargo fmt --check clean; clippy only pre-existing profiles.rs warnings;
+cargo test 113 passed; release binary rebuilt.
+Frontend (untouched, suite rerun): npm test 92 passed; typecheck, lint,
+format:check, electron:build, vite build all clean.
+
+## How to use / reproduce
+
+No user-facing change; note and metadata publishing behave exactly as before.
+Any future change to relay-send policy now happens in one place:
+`send_to_all_relays` in `src/publish.rs`.
+
+## Notes & next steps
+
+- R2–R4 from the DRY audit remain unimplemented by request.
+- Relay health today: nos.lol 502, nostr.wine 403, nostr.l484.com needs
+  NIP-42 auth, nostr.band unreachable; primal/mom/soloco healthy.
+
+---
+
+# Older checkpoint — NIP-46 signer handshake fix (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `64ad94d` ("Signer: listen before announcing so the
+  handshake reply is not lost"). Before it: `dd50b24` (Aurora rename +
+  dropdown fix), `ecb666b` (frosted-glass look), `bfe14f0` (glass build fix).
+- Working tree: clean apart from this checkpoint update. `concept3.svg` deleted
+  and `KeynectrAppIconPossibility02.jpeg` untracked remain as the user had them.
+
+## What was completed
+
+1. **Root-caused the "Yakihonne never leaves the QR screen" bug (`64ad94d`).**
+   Reproduced with a reference NIP-46 client harness over live relays
+   (`/tmp/opencode/nc-client`): the app's announcement arrived, the client's
+   `ack` + `get_public_key` were answered to nobody — the signer task created
+   its notification receiver *after* publishing the announce, so the client's
+   millisecond-fast handshake reply landed in the broadcast channel before any
+   receiver existed and was dropped. Client waits forever → stuck QR.
+   Fix: open `client.notifications()` immediately after adding relays, before
+   connect/subscribe/announce. Post-fix round-trip PASSES end-to-end
+   (announce → ack → get_public_key → pubkey returned).
+2. Relay observations from testing: nos.lol 502 today; nostr.wine 403
+   (auth/paid); nostr.l484.com sends NIP-42 AUTH challenges; healthy:
+   relay.primal.net, nostr.mom, soloco.nl.
+
+## Commits added most recently
+
+- `64ad94d` Signer: listen before announcing so the handshake reply is not lost
+
+## Verification commands run (all green)
+
+Rust (repo root): cargo test 113 passed; clippy (pre-existing profiles.rs
+warnings only); fmt clean; release binary rebuilt with the fix.
+Frontend (`frontend/`): npm test 92 passed; typecheck, lint, format clean.
+End-to-end: reference NIP-46 client + `keynectr signer connect <uri>` over
+wss://nostr.mom, relay.primal.net, soloco.nl — full handshake PASS.
+
+## How to use / reproduce
+
+GUI: `cd ~/Projects/Nostr_Keynctr/frontend && npm start` → Signer → paste a
+client's nostrconnect:// link → approve requests. With Yakihonne: choose its
+remote-signer/connect option, copy its link into Keynectr within its timeout;
+Yakihonne should now switch from the QR screen to the logged-in state.
+
+Harness (if ever needed again): `/tmp/opencode/nc-client` — `nc-client`
+prints a nostrconnect URI to /tmp/opencode/uri.txt and PASSes on round-trip;
+run `target/release/keynectr signer connect $(cat /tmp/opencode/uri.txt)`.
+
+## Notes & next steps
+
+- If a client is still slow, remaining edge: relays that reject kind 24133 or
+  need auth can starve the handshake — consider surfacing per-relay connect
+  status in the Signer UI later.
+- Pre-existing clippy warnings in src/profiles.rs untouched by request.
+
+---
+
+# Older checkpoint — Aurora rename + dropdown fix (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `dd50b24` ("Rename glass theme display to Aurora; fix
+  unreadable select options"). Before it: `ecb666b` (frosted-glass look),
+  `0cab883`/`1aae81c` (checkpoints), `bfe14f0` (glass fix).
+- Working tree: clean apart from this checkpoint update. `concept3.svg` deleted
+  and `KeynectrAppIconPossibility02.jpeg` untracked remain as the user had them.
+
+## What was completed
+
+1. **Theme renamed to Aurora (`dd50b24`).** User picked "Aurora" from options
+   (Aurora/Frost/Glacier/Ice/keep). Display label only — internal id stays
+   `glass`, so existing settings.json values need no migration.
+2. **Fixed unreadable theme dropdown (`dd50b24`).** Under the glass theme the
+   native `<select>` popup inherited the near-transparent select background and
+   painted white-on-white. Options now get an explicit dark surface
+   (`#141a26`) + theme text color, and the glass palette sets
+   `color-scheme: dark` so native controls render dark.
+
+## Commits added most recently
+
+- `dd50b24` Rename glass theme display to Aurora; fix unreadable select options
+
+## Verification commands run (all green)
+
+Frontend (`frontend/`): format:check, npm test (92), typecheck, lint,
+`npm run build` (dist rebuilt for plain `npm start`). Rust untouched this round
+(last verified at `ecb666b`: cargo test 113 passed).
+
+## How to use / reproduce
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+Settings → Appearance → Theme → **Aurora** (frosted translucent panels over a
+glowing deep-blue backdrop). Switching to any other theme from the dropdown is
+readable in all themes.
+
+## Notes & next steps
+
+- If a full identifier rename is ever wanted (Rust enum + types + migration),
+  it needs a serde alias for old saved settings — deliberately not done.
+- Blur/glow tuning: `backdrop-filter` rules + `html[data-theme='glass'] body`
+  gradient near the top of `frontend/src/styles.css`.
+
+---
+
+# Older checkpoint — Glass theme look (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `ecb666b` ("Glass theme: real frosted-glass look").
+  Before it: `bfe14f0` (glass fix — broken Default impl), `1aae81c`
+  (checkpoint), `db2d22f` (glass added), `a01f258` (system removed).
+- Working tree: clean apart from this checkpoint update. `concept3.svg` deleted
+  and `KeynectrAppIconPossibility02.jpeg` untracked remain as the user had them.
+
+## What was completed
+
+1. **Glass now looks like glass (`ecb666b`).** The first pass was only a flat
+   dark palette; the user said "it looks nothing like glass". Redone as real
+   glassmorphism, scoped 100% to `html[data-theme='glass']`:
+   - Aurora backdrop on `<body>` (cyan/violet/blue radial glows over
+     `#0a0d13`); `.app-shell`/`.main` made transparent so it shows through.
+   - Translucent surfaces (`--surface` etc. as rgba) + `backdrop-filter:
+     blur(18px) saturate(160%)` on cards, sidebar, modals, empty states,
+     profile cards, compose preview.
+   - Hairline light borders, softened translucent accent tints, frosted modal
+     scrim (blur 6px), inputs at low-alpha white, sidebar logo inverted like
+     dark/neon.
+2. Earlier this session (`bfe14f0`, see next checkpoint): root cause of "glass
+   does nothing" was a repo that hadn't compiled since `a01f258`.
+
+## Commits added most recently
+
+- `ecb666b` Glass theme: real frosted-glass look
+
+## Verification commands run (all green)
+
+Rust (repo root): `cargo test` 113 passed; `cargo fmt --check` clean.
+Frontend (`frontend/`): `npm test` 92 passed; typecheck, lint,
+format:check clean; `npm run build` rebuilt `dist/` (so plain `npm start`
+serves the new look).
+
+## How to use / reproduce
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+Settings → Appearance → Theme → **Glass**: frosted translucent panels over a
+glowing deep-blue backdrop with cyan accents.
+
+## Notes & next steps
+
+- Blur strength lives in the `backdrop-filter` rules and glow colors in the
+  `html[data-theme='glass'] body` gradient — both near the top of
+  `frontend/src/styles.css`.
+- Electron GPU/Wayland warnings on this laptop are environmental noise.
+
+---
+
+# Older checkpoint — Glass theme fix (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `bfe14f0` ("Fix glass theme: repair broken Default impl
+  that blocked all builds"). Before it: `db2d22f` (glass theme added),
+  `a01f258` (system theme removed), `c080a8d` (icon), `90d699c` (neon).
+- Working tree: clean apart from this checkpoint update. Note: `concept3.svg`
+  still shows as deleted and `KeynectrAppIconPossibility02.jpeg` is untracked —
+  left exactly as the user had them, not committed.
+
+## What was completed
+
+1. **Root cause found: the repo did not compile since `a01f258`.** That commit
+   removed `Theme::System` from the enum but missed `Settings::default()`
+   (`src/settings.rs` still said `theme: Theme::System`). Every rebuild failed,
+   so the desktop app kept spawning an old `target/release/keynectr` binary
+   from before glass existed — which rejected `'glass'` on save ("nothing
+   happens") and explains the flaky "Rust backend exited unexpectedly"
+   launches.
+2. **Fixes in `bfe14f0`:**
+   - `src/settings.rs`: default theme is now `Theme::Light`.
+   - `src/main.rs`: CLI error message lists `light, dark, glass, neon`
+     (no stale "system").
+   - `frontend/src/styles.css`: removed ~600 lines of garbage — 24 broken
+     `:root[data-theme='glass']` blocks nested *inside* the neon rule (a bad
+     edit had interleaved them). One clean neon block + one clean glass block
+     remain, values preserved.
+   - `frontend/src/state/AppProvider.tsx`: theme now applies reactively — a
+     `useEffect` watches `state.settings.theme` and calls `applyTheme()`,
+     replacing the mount-only `useThemeSync()` call, so picking Glass/Neon
+     updates `data-theme` on `<html>` immediately.
+3. Rebuilt both artifacts the app actually runs: `cargo build --release`
+   (Electron spawns `target/release/keynectr`, see `electron/main.ts:82`) and
+   `npm run build` (renderer loads `dist/`).
+
+## Commits added most recently
+
+- `bfe14f0` Fix glass theme: repair broken Default impl that blocked all builds
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 113 passed; 0 failed
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 92 tests passed
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run electron:build  # tsc electron main success
+npm run build         # vite build success
+```
+
+## How to use / reproduce
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+Settings → Appearance → Theme → **Glass** applies immediately (dark panels,
+cyan `#7fdbff` accents) and persists to settings.json. Neon/Light/Dark behave
+the same way.
+
+CLI:
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B settings set theme glass
+```
+
+## Notes & next steps
+
+- If themes ever seem ignored again, first check `cargo check` passes — a
+  broken build silently leaves the stale release binary in place.
+- Pre-existing clippy warnings in `src/profiles.rs` remain untouched (user
+  asked for theme-only changes).
+- Electron GPU/Wayland messages (`--ozone-platform=wayland ... Vulkan`) are
+  environmental noise on this laptop, not app errors.
+
+---
+
+# Older checkpoint — Neon theme (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `90d699c` ("Neon theme: pure-black Matrix palette
+  (CAJAFUERTE-inspired) alongside light/dark/system"). Before it: `ef6ea17`
+  (checkpoint), `a00c7c9` (sidebar brand mark), `cbbe779` (desktop entry),
+  `8a644af` (app icon).
+- Working tree: clean apart from this checkpoint update. Note: `concept3.svg`
+  shows as deleted in the working tree and `KeynectrAppIconPossibility02.jpeg`
+  (icon source art) is untracked — left as the user had them, not committed.
+
+## What was completed
+
+1. **Neon theme (2026-08-24, `90d699c`).** New fourth theme adapted from the
+   CAJAFUERTE Obsidian theme (MIT, github.com/AreAjoErda/CAJAFUERTE): pure
+   black interface (`#000`), deep-pink primary (`#ff1493`), purple secondary
+   (`#8b00ff` family), yellow warnings (`#ffd700`), Matrix-green success.
+   - Settings → Appearance → Theme → **Neon** (with hint text).
+   - `applyTheme` maps neon straight to `data-theme='neon'` (not affected by
+     the system light/dark preference); sidebar logo auto-inverts like dark.
+   - Backend: `Theme::Neon` variant (serde `neon`), CLI
+     `settings set theme <light|dark|system|neon>`.
+   - Old settings files keep loading; new value round-trips through
+     settings.json.
+
+## Commits added most recently
+
+- `90d699c` Neon theme: pure-black Matrix palette (CAJAFUERTE-inspired) alongside light/dark/system
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 113 passed; 0 failed
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 92 tests passed (new neon theme test)
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI: Settings → Appearance → Theme → **Neon**. Applies immediately and
+persists in `~/.local/share/keynectr/settings.json`.
+
+CLI:
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B settings set theme neon
+```
+
+## Notes & next steps
+
+- Neon shadows carry a faint pink glow (CAJAFUERTE vibe); if it is too much,
+  dial `--shadow`/`--shadow-modal` in the `:root[data-theme='neon']` block of
+  `frontend/src/styles.css`.
+- The theme only restyles the app UI; the Electron window chrome stays
+  system-styled on Wayland.
+- Earlier today: sidebar brand mark (`a00c7c9`), taskbar icon via desktop
+  entry (`cbbe779`), app icon (`8a644af`), security upgrades (`c11ab9f`).
+
+---
+
+# Older checkpoint — App icon (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `a00c7c9` ("Sidebar brand mark: hummingbird-key artwork
+  replaces the shield icon"). Before it: `cbbe779` (desktop entry/Wayland),
+  `8a644af` (app icon), `c11ab9f` (security upgrades).
+- Working tree: clean apart from this checkpoint update. Note: `concept3.svg`
+  shows as deleted in the working tree and `KeynectrAppIconPossibility02.jpeg`
+  (the icon source art) is untracked — both left as the user had them, not committed.
+
+## What was completed
+
+1. **In-app brand mark (2026-08-24, `a00c7c9`).** The sidebar logo (the
+   "shield" the user saw in-app) now uses the hummingbird-key artwork
+   (`src/assets/logo.png`, Vite-imported so it is fingerprinted into the
+   build). In dark themes the tile is inverted (white bird on dark) via CSS.
+   The remaining `shield` icons (Unlock-vault button, password/backup buttons)
+   are intentional security affordances, not branding.
+2. **Taskbar icon on KDE Wayland (2026-08-24, `cbbe779`).** The user reported
+   no icon after restart. Root cause: on Wayland there are no per-window
+   icons — the KDE taskbar resolves the running app through an installed
+   `.desktop` file, which Keynectr did not have. Fix:
+   - `frontend/scripts/install-desktop-entry.sh` (npm script
+     `desktop:install`) installs
+     `~/.local/share/icons/hicolor/512x512/apps/keynectr.png` and
+     `~/.local/share/applications/keynectr.desktop` (Icon=keynectr,
+     StartupWMClass=keynectr) and refreshes the desktop database. **Run once
+     per machine.** Confirmed working by the user.
+   - `app.setDesktopName('keynectr.desktop')` in `electron/main.ts` (called
+     before `ready`; Electron 43 renamed the old `setDesktopFileName`) pins
+     the app id so the desktop file always matches.
+3. **Window + packaged icon (2026-08-24, `8a644af`).** Hummingbird-key artwork
+   as `frontend/build/icon.png` (electron-builder `linux.icon`) and
+   `frontend/public/icon.png` (shipped in the asar, loaded by BrowserWindow —
+   effective on X11 titlebars and inside packaged builds).
+4. Earlier today: all npm security advisories cleared via major upgrades
+   (`c11ab9f`), Updates card (`8bce428`), feed profile filter (`55a49b4`),
+   publish latency trim (`b001b3c`).
+
+## Commits added most recently
+
+- `a00c7c9` Sidebar brand mark: hummingbird-key artwork replaces the shield icon
+- `cbbe779` Desktop entry + Wayland app id so the taskbar shows the app icon
+- `8a644af` App icon: hummingbird-key mark for window and packaged Linux builds
+
+## Verification commands run (all green)
+
+Frontend (`frontend/`):
+
+```
+npm run desktop:install  # installed icon + keynectr.desktop for this user
+npm test             # 14 files, 91 tests passed
+npm run typecheck    # clean
+npm run lint         # 0 errors
+npm run format:check # clean
+npm run electron:build  # tsc electron main success (setDesktopName compiled)
+npm run dist         # electron-builder linux dir target packaged OK (earlier)
+```
+
+## How to use / reproduce
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend
+npm run desktop:install   # once per machine
+npm start                 # restart the app -> taskbar shows the icon
+```
+
+## Notes & next steps
+
+- On Wayland, KDE may need the app restarted (and occasionally the panel to
+  refresh) before the icon swaps from the generic one.
+- The source JPEG has a white background (kept as-is); regenerate the PNGs
+  from a transparent source if dark-taskbar polish is wanted.
+- For real installer targets (deb/AppImage), electron-builder embeds the icon
+  and desktop file automatically from `build/`; the manual install above only
+  covers running from source.
+- Sharing decision (this session): user chose "shared access on same machine" —
+  the current single-vault + passcode model already covers it.
+- Relay health (earlier today): damus.io 503, nostr.band WS handshake timing out.
+
+---
+
+# Older checkpoint — Security dependency upgrades (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `c11ab9f` ("Security: major dependency upgrades clearing
+  all npm advisories; show per-advisory fix paths"). Before it: `8bce428`
+  (updates card), `a1915bb` (checkpoint), `55a49b4` (feed filter), `b001b3c`
+  (publish latency).
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **All npm security advisories cleared (2026-08-24, `c11ab9f`).** The user
+   ran *Install updates*, but 20 advisories remained — `npm audit fix` only
+   applies semver-compatible fixes, and npm's own `fixAvailable` data showed
+   every remaining issue needed one of four **major** upgrades. All applied and
+   verified:
+   - `vite` ^5.4 → **^8.2.2** (fixes vite path traversal, esbuild dev-server)
+   - `vitest` ^2.1 → **^4.1.11** (fixes critical vitest/@vitest/mocker/vite-node)
+   - `electron` ^33.2 → **^43.4.1** (fixes ~30 runtime CVEs incl. ASAR bypass)
+   - `electron-builder` ^25.1 → **^26.15.3** (fixes critical tar chain,
+     node-gyp/cacache/make-fetch-happen/builder-util cluster)
+   - `npm audit` now reports **0 vulnerabilities**.
+2. **Updates card now explains residual advisories (`c11ab9f`).** Each advisory
+   can show a fix-path hint from npm (e.g. "Needs electron@43.4.1, a major
+   upgrade — not auto-installed."), or "No fix has been published yet." Hints
+   only appear when *Install updates* cannot clear the item by itself.
+3. Full toolchain verified on the new majors: vitest 4, vite 8, plugin-react 6,
+   electron 43 all pass the existing suite with no config changes.
+
+## Commits added most recently
+
+- `c11ab9f` Security: major dependency upgrades clearing all npm advisories; show per-advisory fix paths
+
+## Verification commands run (all green)
+
+Frontend (`frontend/`):
+
+```
+npm audit            # found 0 vulnerabilities
+npm test             # 14 files, 91 tests passed
+npm run typecheck    # clean
+npm run lint         # 0 errors
+npm run format:check # clean
+npm run build        # vite 8 build success
+npm run electron:build  # tsc electron main success
+npx electron --version  # v43.4.1
+```
+
+Rust (repo root):
+
+```
+cargo test            # 113 passed; 0 failed (new fix-path parser test)
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+## How to use / reproduce
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+Settings → Updates → Check for updates should show "No known security
+advisories". If new ones appear later, Install handles compatible fixes;
+anything left lists exactly what major upgrade it needs.
+
+## Notes & next steps
+
+- Electron jumped 10 majors (33 → 43): compile-level checks and the renderer
+  test suite pass, but give the app one manual smoke test (launch, unlock,
+  publish, feed) when convenient.
+- The Updates card's Install button remains deliberately conservative: majors
+  are never auto-applied; they are surfaced as explicit hints instead.
+- Relay health (earlier today): damus.io 503, nostr.band WS handshake timing out.
+
+---
+
+# Older checkpoint — Updates card (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `8bce428` ("Updates card: scan npm/cargo deps, surface
+  security advisories, install compatible updates"). Before it: `55a49b4`
+  (feed profile filter), `3dfd15f` (checkpoint), `b001b3c` (publish latency).
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **Updates card in Settings (2026-08-24, `8bce428`).** New **Updates** section
+   on the Settings screen with two buttons:
+   - **Check for updates** — scans without changing anything:
+     `npm outdated --json` + `npm audit --json` (frontend) and
+     `cargo update --dry-run` (Rust). Known security advisories are listed
+     first with severity badges (critical/high → danger, moderate → warning);
+     outdated npm packages and Rust crates are listed with current → available
+     versions.
+   - **Install updates** — applies compatible (non-breaking) updates:
+     `npm audit fix`, then `npm update`, then `cargo update`. Reports what was
+     applied and reminds that a **rebuild + restart** is required to load them.
+   - First real scan found 20 advisories (2 critical: tar, vitest; several high
+     in the Electron build chain), 18 outdated npm packages, 42 outdated crates.
+2. **Backend:** new `src/updates.rs` module (parsers unit-tested; commands run
+   with timeouts and never touch secret material). IPC methods `update_check`
+   and `update_apply`, dispatched outside the state lock so slow installs never
+   block other requests. Electron allowlist extended; backend round-trip cap
+   raised 120 s → 300 s to fit cold-cache installs.
+3. Optional hardening noted in-app: installing `cargo-audit` adds RustSec
+   advisory scanning for the Rust side (currently not installed on this machine;
+   the app says so under Notes when absent).
+
+## Commits added most recently
+
+- `8bce428` Updates card: scan npm/cargo deps, surface security advisories, install compatible updates
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 112 passed; 0 failed (8 new updates tests)
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+# end-to-end: echo '{"id":1,"method":"update_check"}' | ./target/release/keynectr serve
+# returned real advisories/outdated lists for this machine
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 91 tests passed (4 new Settings tests)
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI: `cd ~/Projects/Nostr_Keynctr/frontend && npm start` → **Settings →
+Updates → Check for updates**, review the list (security first), then
+**Install updates**. Afterwards rebuild and relaunch:
+
+```bash
+cd ~/Projects/Nostr_Keynctr && cargo build --release
+cd frontend && npm run build && npm start
+```
+
+CLI equivalent:
+
+```bash
+cd frontend && npm audit fix && npm update
+cd .. && cargo update
+```
+
+## Notes & next steps
+
+- `Install updates` only applies semver-compatible bumps. Major version jumps
+  shown by the check (e.g. electron 33 → 43, eslint 9 → 10) still need manual
+  attention — deliberate, to avoid breaking the app silently.
+- Consider running the first real "Install updates" soon: 2 critical npm
+  advisories were found (tar, vitest dev chain) plus high-severity Electron
+  packaging tools.
+- Install `cargo-audit` (`cargo install cargo-audit`) for RustSec coverage; the
+  card picks it up automatically once present.
+- Possible follow-ups: CLI `updates` subcommand; auto-check on startup behind a
+  setting.
+- Relay health (earlier today): damus.io 503, nostr.band WS handshake timing out.
+
+---
+
+# Older checkpoint — Feed "My notes" profile filter (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `55a49b4` ("Feed: 'My notes' scope with per-profile
+  dropdown filter"). Before it: `b001b3c` (note publish latency trim), `8f63761`
+  (checkpoint), `2ad054e` (NIP-05 checkpoint).
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **Feed "My notes" scope (2026-08-24, `55a49b4`).** The Feed screen now has a
+   third scope button next to *Everyone* and *My contacts*:
+   - **My notes** shows only posts published by one of the user's own profiles.
+     It defaults to the currently selected (active) profile.
+   - While active, a **dropdown** lists every stored profile (`Label (active)`);
+     picking one re-fetches the feed filtered to that account's npub.
+   - Disabled (with tooltip) when no profiles exist; dedicated empty state when
+     a profile has no recent notes.
+2. **Backend support:** new `feed::profile_feed()` (author-filtered variant of
+   the shared aggregate query); IPC `feed_get` gained an optional `author`
+   param (npub or hex) that takes precedence over `contacts_only`; author key
+   parsing happens outside the state lock so slow relays still never block
+   interactive requests.
+3. Earlier today: note-publish latency trim (`b001b3c`) — no global connection
+   wait, parallel sends, 6 s per-relay cap in `src/publish.rs`.
+
+## Commits added most recently
+
+- `55a49b4` Feed: 'My notes' scope with per-profile dropdown filter
+- `b001b3c` Trim note publish latency: skip global connection wait, parallel sends, 6s cap
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 104 passed; 0 failed (2 new profile_feed tests)
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 87 tests passed (3 new FeedScreen tests)
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI: `cd ~/Projects/Nostr_Keynctr/frontend && npm start` → **Feed** → click
+**My notes** (third segment). The feed reloads showing only the active profile's
+notes; switch accounts with the dropdown that appears next to it.
+
+CLI (existing commands unchanged):
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B feed [limit]          # everyone
+$B feed --contacts       # contacts of active profile
+```
+
+## Notes & next steps
+
+- Possible follow-up: expose `--author <npub>` on the CLI `feed` command for
+  parity with the GUI scope (IPC already supports it).
+- Feed reads are bounded to the last 24 h (LOOKBACK in `src/feed.rs`); "My
+  notes" therefore hides older posts by design — same rule as Everyone.
+- Relay health (checked earlier today): damus.io 503, nostr.band WS handshake
+  timing out; consider disabling nostr.band until it recovers.
+- Pre-existing clippy warnings in `src/profiles.rs` remain (drop of reference,
+  unused `delete_profile`).
+
+---
+
+# Older checkpoint — Note publish latency trim (2026-08-24)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `b001b3c` ("Trim note publish latency: skip global
+  connection wait, parallel sends, 6s cap"). Before it: `2ad054e` (checkpoint),
+  `045fa47` (NIP-05), `cb23a5e` (metadata latency trim), `4d70b25` (concurrent IPC).
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **Diagnosed a slow/failing publish (2026-08-24, `b001b3c`).** User reported a
+   10+ s note publish with two relay failures (`relay.snort.social` "Not
+   connected", `relay.nostr.band` "did not respond in time"). Live probing of the
+   user's relays showed:
+   - The note itself **did land** on nos.lol, nostr.l484.com, relay.primal.net,
+     soloco.nl (why phoenix.social showed it). Kind-0 metadata ("Boo" + photo)
+     is on those relays too — Primal/Iris visibility is third-party indexing lag
+     or their differing relay sets, not lost data.
+   - `wss://relay.damus.io` is **down** (HTTP 503) and `wss://relay.nostr.band`
+     **times out on the WebSocket handshake** right now.
+   - Root cause of the stall: the *note* path still had the pattern removed from
+     the metadata path in `cb23a5e` — a global `wait_for_connection(10s)` that
+     burned its full timeout whenever any single relay was unreachable, then
+     sequential per-relay sends (15s timeout each).
+2. **Fix (`b001b3c`)** — `src/publish.rs` now mirrors `src/profiles.rs`:
+   - No global connection wait (`send_event` waits for each relay's writable
+     state itself).
+   - Sends run in parallel via `tokio::task::JoinSet`; per-relay timeout cut
+     15s → 6s, so worst case ≈ 6 s regardless of how many relays are dead.
+   - Failure reporting unchanged (per-relay concise error + technical detail).
+
+## Commits added most recently
+
+- `b001b3c` Trim note publish latency: skip global connection wait, parallel sends, 6s cap
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 102 passed; 0 failed
+cargo clippy --all-targets   # only pre-existing warnings in src/profiles.rs
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`) — untouched by this change but re-run:
+
+```
+npm test              # 14 files, 84 tests passed
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI: `cd ~/Projects/Nostr_Keynctr/frontend && npm start`, compose a note,
+publish. Expect ~1–6 s even when some relays are dead; failures are listed
+per-relay under the composer.
+
+CLI:
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B publish "hello"        # text note as active profile
+```
+
+## Notes & next steps
+
+- **Relay health (checked 2026-08-24):** damus.io returning 503; nostr.band WS
+  handshake times out. Consider disabling nostr.band until it recovers, and
+  adding healthy high-traffic relays (e.g. offchain.pub, nostr.mom) so clients
+  whose default sets don't include nos.lol/primal.net can see your notes.
+- Profile/photo on Primal: metadata + notes are on relay.primal.net; if Primal
+  still shows nothing later, re-check via primal.net (their crawler indexes with
+  delay). Iris/Yakihonne need the note on relays *they* read.
+- Pre-existing clippy warnings in `src/profiles.rs` remain (drop of reference,
+  unused `delete_profile`).
+- Candidate next features: banner/about fields in the edit UI.
+
+---
+
+# Older checkpoint — NIP-05 identifiers (2026-08-23)
+
+A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master` @ `045fa47` ("Add NIP-05 identifiers: store, publish, GUI
+  modal, CLI helpers"). Before it: `f2c30d3` (checkpoint), `cb23a5e` (publish
+  latency trim), `4d70b25` (concurrent IPC), `d618a5a` (rename), and earlier
+  rebrand/UI commits listed in the previous checkpoint section below.
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **NIP-05 identifiers (2026-08-23, `045fa47`)** — the feature agreed on
+   2026-08-22 (see "Next feature" note in the older checkpoint below). A session
+   that crashed mid-edit had left most of the Rust side written but uncommitted
+   and non-compiling; this session finished it end-to-end:
+   - **Backend (Rust):** `nip05: Option<String>` on `StoredProfile` +
+     `ProfileSummary`; `set_nip05()` validates (`name@domain`, `_@domain` bare
+     form allowed; lower-cased; rejects malformed input without storing),
+     stores, and republishes kind 0 metadata with the identifier included;
+     wired through IPC (`set_nip05` request) and CLI (`set-nip05 <npub>
+     <id|clear>`); all other publish paths (create/rename/picture/publish-name)
+     now include the stored nip05.
+   - **GUI:** new **NIP-05** button on every Profiles card opens a modal
+     (prefilled) with live validation, *Save & publish* and *Remove*; the
+     handle is displayed on the profile card under the name. Wired:
+     Electron allowlist, `api.setNip05`, AppProvider, fake backend + tests.
+   - **CLI helper:** `keynectr nip05-file <npub> <id>` prints the exact
+     `.well-known/nostr.json` document (names + relays maps, hex pubkey) to
+     serve on your domain. Verified against the real vault.
+   - **Docs:** `docs/NIP-05.md` explains both halves (app publish + domain
+     serving, nginx example, CORS requirement).
+   - **Bug fix:** `Modal.tsx` stole focus from `autoFocus` inputs one frame
+     after opening (deferred `container.focus()`) — now it only focuses the
+     dialog when nothing inside has focus. This also fixes flaky typing in
+     modals generally.
+2. Previous session work (rename with metadata republish, concurrent IPC,
+   publish latency trim, card-click selection, button wrap, rebrand) — see the
+   older notes below.
+
+## Commits added most recently
+
+- `045fa47` Add NIP-05 identifiers: store, publish, GUI modal, CLI helpers
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 102 passed; 0 failed (3 new NIP-05 tests)
+cargo clippy --all-targets   # only 2 pre-existing warnings in src/profiles.rs
+                              # (drop of reference, unused delete_profile)
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 84 tests passed (4 new NIP-05 tests)
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI:
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+- Profiles screen: **NIP-05** button → type `name@domain.com` → Save & publish.
+  Remove clears it. The handle shows on the profile card.
+- Everything else as before (Edit name, Picture, Publish name, card-click
+  selection, delete + undo).
+
+CLI:
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B list                                   # show profiles
+$B set-nip05 <npub> boo@l484.com          # set + publish
+$B set-nip05 <npub> clear                 # remove + publish removal
+$B nip05-file <npub> boo@l484.com         # print .well-known/nostr.json JSON
+```
+
+Domain side (one-time): serve the printed document at
+`https://<domain>/.well-known/nostr.json` with `Content-Type: application/json`
+and `Access-Control-Allow-Origin: *` — details + nginx snippet in
+`docs/NIP-05.md`.
+
+## Notes & next steps
+
+- The `.well-known/nostr.json` HTTP half cannot be done by the app alone; users
+  must host the file themselves (`nip05-file` prints it for them).
+- If rename/publish latency still feels long, next step would be background
+  publishing (return immediately, report via notice later).
+- Pre-existing clippy warnings in `src/profiles.rs` (drop of a reference, unused
+  `delete_profile`) are untouched — worth cleaning up in a future pass.
+- Nostr has no relay-to-relay sync: names/pictures/nip05 are only visible on
+  relays they were published to. Keep major relays enabled.
+- Clients cache profiles; hard-refresh (Ctrl+Shift+R) after republishing.
+- Candidate next features: banner/about fields in the edit UI.
+- Binary is `keynectr`; data lives in `~/.local/share/keynectr`. The KDF verifier
+  string in crypto.rs was deliberately NOT renamed so old encrypted backups stay readable.
+  The git remote is `https://git.atitlan.io/avi/Nostr_Keynctr`.
+- Relay config at time of writing: nos.lol, relay.primal.net, nostr.l484.com
+  (user's own), damus.io, snort.social, soloco.nl, relay.nostr.band.
+
+---
+
+# Older checkpoint — Responsive backend (concurrent IPC) + rename (2026-08-23)
+
+**App renamed to Keynectr (2026-08-23).** A stopping point you can return to if this session is closed. Everything below was
+verified green at the moment this file was written.
+
+## Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr` (renamed from `0_Nostr` after commit `1116dfd`;
+  folder itself renamed from `Nostr-Keynectr` — see `2e4005d`)
+- Git repo: `master` @ `cb23a5e` ("Trim metadata publish latency: skip global
+  connection wait, 6s send cap"). Before it: `4d70b25` (concurrent IPC), `d618a5a`
+  (rename), `64502c1` (button wrap), `653945a` (card-click selection), `2e4005d`
+  (folder-rename checkpoint), `24b34b6`, `6ead6f4`, `31ef305` (Keynectr rebrand),
+  `a6329d5` (metadata publishing), `db81f8d` (delete + undo).
+- Working tree is **clean** apart from this checkpoint update, which is committed right after.
+
+## What was completed
+
+1. **Publish latency trimmed further (2026-08-23, `cb23a5e`)** — after the concurrent
+   IPC fix, rename still took ~10 s: `wait_for_connection` always burned its full
+   timeout when any relay was unreachable, and the dead relay's send burned 8 s.
+   Removed the global connection wait (`send_event` waits for writability itself) and
+   capped sends at 6 s. Typical rename now completes in ~1–3 s even with one dead
+   relay. If still too slow, next step is fully background publishing.
+2. **Backend made responsive (2026-08-23, `4d70b25`)** — user-visible lag fixed:
+   Selecting a profile took ~10 s and renaming ~30 s. Root causes: the IPC server
+   processed requests strictly one-at-a-time; the Home screen fires a relay test per
+   enabled relay on mount (a dead relay burns the full 8 s timeout each), and
+   `feed_get` held the shared lock during multi-second relay fetches — so Select queued
+   behind them; metadata publishing also waited 10 s for connections and sent to relays
+   one-by-one with 15 s timeouts each (~30 s with one dead relay).
+   Changes:
+   - IPC server now handles requests **concurrently** (task per request; replies are
+     id-correlated so out-of-order is fine). Mutations stay serialized via the shared
+     mutex, which moved from `std::sync` to `tokio::sync` (`App`, `Signer::connect`,
+     `run_sign_task`, CLI `signer connect`).
+   - `relay_test` and `feed_get` no longer hold the shared lock during network I/O
+     (they copy settings / active-npub under a short lock first).
+   - Metadata publish now sends to all relays **in parallel** with shorter timeouts
+     (connect 5 s, send 8 s) → worst case ~13 s instead of ~100 s; typical rename is a
+     few seconds.
+2. **Rename a profile (2026-08-23)** — new "Edit name" button on every Profiles card
+   opens a modal (prefilled with the current name); saving stores the new label and
+   republishes kind 0 metadata to enabled relays (`d618a5a`). Wired end-to-end:
+   `profiles::rename_profile` (Rust), `rename_profile` IPC request, Electron
+   RENDERER_METHODS allowlist, `api.renameProfile`, AppProvider `renameProfile`,
+   RenameModal UI, fake-backend support + test.    CLI: `keynectr rename <npub>
+   <new-name>`. Empty names rejected; whitespace trimmed; works offline (change saved,
+   publish retried later via "Publish name").
+3. **Click anywhere on a profile card to select it (2026-08-23)** — on the Profiles
+   screen, clicking an inactive profile's card now does the same as pressing its
+   "Select" button (`653945a`). Clicks on buttons inside the card (Copy / Publish name /
+   Picture / Edit name / Delete / Secret key / Select) do not trigger selection. The
+   active card is not clickable and shows a hover highlight on inactive cards.
+4. **Action buttons wrap on narrow windows (2026-08-23)** — `.profile-card-actions` now
+   uses `flex-wrap: wrap`, so at half-screen width the action buttons wrap onto extra
+   rows inside the card instead of spilling past its border (`64502c1`).
+5. **Project folder renamed** to `Nostr_Keynctr` (`2e4005d`) — old path
+   `Nostr-Keynectr` no longer exists; same project, new name.
+6. Earlier in the session: Keynectr rebrand across UI/package/binary (`31ef305`,
+   `6ead6f4`, `24b34b6`), metadata/picture publishing (`a6329d5`) — see previous
+   checkpoint notes below for details.
+
+## Commits added most recently
+
+- `cb23a5e` Trim metadata publish latency: skip global connection wait, 6s send cap
+- `4d70b25` Make IPC concurrent so relay checks and feeds never block the UI
+- `d618a5a` Add profile rename with metadata republish (GUI + CLI)
+- `64502c1` Wrap profile card action buttons on narrow windows
+- `653945a` Select a profile by clicking anywhere on its card
+- `2e4005d` Checkpoint: project folder renamed to Nostr_Keynctr
+
+## Verification commands run (all green)
+
+Rust (repo root):
+
+```
+cargo test            # 99 passed; 0 failed
+cargo clippy --all-targets   # finishes; 2 pre-existing warnings in src/profiles.rs
+                              # (drop of reference, unused delete_profile)
+cargo fmt --check     # clean
+cargo build --release # success
+```
+
+Frontend (`frontend/`):
+
+```
+npm test              # 14 files, 81 tests passed (incl. rename + card-click tests)
+npm run typecheck     # clean
+npm run lint          # 0 errors
+npm run format:check  # clean
+npm run build         # vite build success
+npm run electron:build  # tsc electron main success
+```
+
+## How to use / reproduce
+
+GUI:
+
+```bash
+cd ~/Projects/Nostr_Keynctr/frontend && npm start
+```
+
+- Profiles screen: click an inactive profile's card (anywhere except its buttons) to
+  make it active; the Select button still works as before.
+- Profiles screen: **Edit name** button opens a modal to rename a profile and publish
+  the new name.
+- New profiles publish their name automatically on creation.
+- Existing profiles: **Profiles → Publish name** button, or **Picture** button to set a
+  photo (URL paste or file upload) which publishes immediately.
+
+CLI:
+
+```bash
+B=~/Projects/Nostr_Keynctr/target/release/keynectr
+$B list                                   # show profiles
+$B relays enable wss://nos.lol            # enable at least one relay first
+$B publish-name <npub>                    # republish stored name
+$B set-picture <npub> https://…/img.png   # set + publish picture
+$B rename <npub> <new-name>               # rename + publish the new name
+```
+
+## Notes & next steps
+
+- **Architecture note (2026-08-23):** the shared `App` state mutex is now
+  `tokio::sync::Mutex` (`Arc<Mutex<App>>` in ipc.rs/signer.rs). Guards are held across
+  awaits by design; new handlers that touch vault/settings must lock it, while pure
+  network requests should copy inputs under a short lock and run lock-free.
+- If rename/publish latency still feels long, next step would be background
+  publishing (return immediately, report via notice later) instead of shorter timeouts.
+- Pre-existing clippy warnings in `src/profiles.rs` (drop of a reference, unused
+  `delete_profile`) are untouched — worth cleaning up in a future pass.
+- Nostr has no relay-to-relay sync: names/pictures are only visible on relays they were
+  published to. Keep major relays enabled so clients that don't read your own relay can
+  see the profile.
+- Clients cache profiles; hard-refresh (Ctrl+Shift+R) after republishing.
+- **Next feature (agreed 2026-08-22): NIP-05 identifiers.** Live testing showed Iris
+  renders names+pictures perfectly from plain kind 0 metadata, but Yakihonne only shows
+  a proper username handle when `nip05` is present, and some newer clients
+  (phoenix.social) are picky about relay coverage. Plan: add an optional NIP-05
+  identifier field per profile (GUI + CLI), include it in published metadata, plus docs
+  or a helper for serving `.well-known/nostr.json` on the user's domain (the HTTP side
+  cannot be done by the app alone).
+- Other candidates: banner/about fields in the edit UI. (Rename profiles was completed
+  2026-08-23.)
+- **Rename details:** binary is now `keynectr`; data lives in `~/.local/share/keynectr`
+  (auto-migrated from `nost-feed-manager` on first run — verified live). The KDF verifier
+  string in crypto.rs was deliberately NOT renamed so old encrypted backups stay readable.
+  The git remote is `https://git.atitlan.io/avi/Nostr_Keynctr`.
+- Relay config at time of writing (all enabled): nos.lol, relay.primal.net, l484.com
+  (user's own), damus.io, snort.social, soloco.nl; relay.nostr.band added but was
+  unreachable (handshake timeout) — retry enabling later.
+
+## Checkpoint — frontend home screen improvements (2026-08-26)
+
+A stopping point you can return to if this session is closed.
+
+### Where things are
+
+- Project: `/home/avi/Projects/Nostr_Keynctr`
+- Git repo: `master`. **Working tree is DIRTY** — the changes below are local
+  edits and have NOT been committed yet (see "outstanding items").
+- Dev-run fix also applied: `frontend/vite.config.ts` now binds the dev server
+  to `host: '127.0.0.1'` so Electron (`NOSTR_GUI_DEV_URL=http://127.0.0.1:5173`)
+  and Vite agree on address and the window is no longer a white box.
+
+### What was completed (user-facing)
+
+1. **Profile pictures now show on Home.** The Home screen's active-profile
+   `Avatar` was missing the `picture` prop, so the image only appeared on the
+   Profiles screen. `HomeScreen.tsx` now passes `picture={profile.picture}`.
+2. **All profiles listed on Home.** Replaced the single "Active profile" card
+   with a "Your profiles" card listing every profile (avatar + picture, label,
+   shortened npub, Active badge). Each non-active row has a working **Select**
+   button (calls `selectProfile`); a **Manage** link goes to the Profiles
+   screen and an **Add profile** button is at the bottom.
+3. **`Badge` now accepts `className`** so the Active badge can be inline next to
+   the name.
+4. **Relays card removed from Home.** The "Relays" card (live connection status,
+   refresh, "enable a relay" link) is no longer shown on Home — relay status
+   lives on the Relays screen. Removed the now-unused relay-check logic
+   (`relayTest`/`runCheck`/`statuses`/`testing`/`enabled`/`Spinner`) and the
+   corresponding test.
+5. **Profile card now full-width on Home.** `.home-grid` was a two-column grid
+   (profiles + relays); with Relays gone the profiles card only filled the left
+   half. Changed it to a single `1fr` column and dropped the now-redundant
+   `@media (max-width: 900px)` override, so "Your profiles" matches the width
+   of "Most recent publication" below it. No JSX change.
+6. **Removed the "Profiles" sidebar tab.** It was redundant with Home's
+   "Manage profiles" button (which already navigates to the Profiles screen,
+   still rendered by `App.tsx`). Deleted the `profiles` entry from `NAV_ITEMS`
+   in `Sidebar.tsx`; the Profiles screen, route, and Manage button are all
+   unchanged. Updated `App.test.tsx` to reach the screen via "Manage profiles"
+   instead of the removed tab.
+7. **Active-profile picture now shows on Compose + sidebar.** Same root cause
+   as the earlier Home fix: `Avatar` was rendered without the `picture` prop.
+   Added `picture={active.picture}` to both the write and preview avatars in
+   `ComposeScreen.tsx` and to the active-profile avatar in `Sidebar.tsx`. The
+   picture now appears consistently wherever the active profile is shown.
+8. **Click a profile row on Home to select it.** Mirrored the Profiles screen's
+   clickable-row pattern: the whole non-active row in the Home "Your profiles"
+   list now selects the profile on click (guarded so Copy/Select buttons don't
+   double-fire). Added `cursor: pointer` for non-active rows. Added a test
+   asserting row-click selection.
+
+### Files changed
+
+- `frontend/src/screens/HomeScreen.tsx` (profiles list + picture prop + select; relays removed)
+- `frontend/src/components/Badge.tsx` (add `className` prop)
+- `frontend/src/styles.css` (`.home-profile-list` / `.home-profile-row` / etc.)
+- `frontend/src/test/HomeScreen.test.tsx` (scope copy-button test to Alice's row; drop relay-status test)
+- `frontend/vite.config.ts` (dev server `host: '127.0.0.1'`)
+
+### Verification commands run (all green)
+
+Frontend (`frontend/`): `npm run typecheck` clean; `npm run lint` clean;
+`npm test` 15 files / 98 tests pass; `npm run format:check` clean (after
+`npm run format`).
+
+### How to use / reproduce
+
+Dev mode (two terminals, from `~/Projects/Nostr_Keynctr/frontend`):
+
+```
+# Terminal 1
+npm run dev            # prints Local: http://127.0.0.1:5173/
+
+# Terminal 2
+NOSTR_GUI_DEV_URL=http://127.0.0.1:5173 npm start
+```
+
+Home now shows every profile with its picture, and selecting one there updates
+the active profile immediately.
+
+### Outstanding items
+
+- Committed as `835b0a0`. The working tree still has unrelated user changes
+  (`concept3.svg` deleted, `KeynectrAppIconPossibility02.jpeg` untracked) that
+  were intentionally left out of the commit.
+- The dev-server `host: '127.0.0.1'` change is intentional; if you later need
+  LAN access to the dev server, set it back to `true` and use the matching URL.
diff --git a/frontend/src/lib/api.ts b/frontend/src/lib/api.ts
index 8f0f7d6..cd8cae6 100644
--- a/frontend/src/lib/api.ts
+++ b/frontend/src/lib/api.ts
@@ -106,8 +106,8 @@ export const api = {
   signerApprove: (id: string, approved: boolean) =>
     call<SignerStatus>('signer_approve', { id, approved }),
 
-  deleteProfile: (npub: string) => call<AppState>('delete_profile', { npub }),
-  undoDelete: () => call<AppState>('undo_delete'),
+  deleteProfile: (npub: string) => call<ProfileSummary>('delete_profile', { npub }),
+  undoDelete: () => call<ProfileSummary>('undo_delete'),
 
   copyText: (text: string) => window.backend.copyText(text),
 };
diff --git a/frontend/src/screens/ProfilesScreen.tsx b/frontend/src/screens/ProfilesScreen.tsx
index f74c483..92b02d7 100644
--- a/frontend/src/screens/ProfilesScreen.tsx
+++ b/frontend/src/screens/ProfilesScreen.tsx
@@ -1,4 +1,4 @@
-import { useEffect, useState } from 'react';
+import { useState } from 'react';
 import { Avatar } from '../components/Avatar';
 import { Badge } from '../components/Badge';
 import { Button } from '../components/Button';
@@ -17,14 +17,7 @@ interface ProfilesScreenProps {
 }
 
 export function ProfilesScreen({ onCreateProfile }: ProfilesScreenProps) {
-  const {
-    state,
-    selectProfile,
-    deleteProfile,
-    undoDelete,
-    publishProfileMetadata,
-    clearLastDeleted,
-  } = useApp();
+  const { state, selectProfile, deleteProfile, undoDelete, publishProfileMetadata } = useApp();
   const [selecting, setSelecting] = useState<string | null>(null);
   const [publishing, setPublishing] = useState<string | null>(null);
   const [error, setError] = useState<string | null>(null);
@@ -40,14 +33,6 @@ export function ProfilesScreen({ onCreateProfile }: ProfilesScreenProps) {
   const undoHistory = state?.undo_history ?? [];
   const lastDeleted = undoHistory[undoHistory.length - 1] ?? null;
 
-  useEffect(() => {
-    if (!lastDeleted) return;
-    const timeout = setTimeout(() => {
-      clearLastDeleted();
-    }, 5000);
-    return () => clearTimeout(timeout);
-  }, [lastDeleted, clearLastDeleted]);
-
   const onPublishName = async (npub: string, label: string) => {
     setError(null);
     setNotice(null);
@@ -78,34 +63,19 @@ export function ProfilesScreen({ onCreateProfile }: ProfilesScreenProps) {
               className="undo-bar"
               style={{
                 margin: '12px 0',
-                padding: '10px 14px',
-                background: 'var(--primary-soft)',
-                border: '1px solid var(--border)',
-                borderRadius: '8px',
-                display: 'flex',
-                alignItems: 'center',
-                gap: '8px',
+                padding: '8px 12px',
+                background: 'var(--token-item-bg, #f0f0f0)',
+                borderRadius: '4px',
               }}
             >
-              <span style={{ color: 'var(--text)', fontWeight: 500 }}>
-                Profile “{lastDeleted.label}” deleted.
-              </span>
-              <span style={{ color: 'var(--text-muted)' }}>—</span>
-              <button
+              <Button
+                variant="secondary"
+                style={{ marginRight: '8px' }}
+                size="sm"
                 onClick={() => void undoDelete()}
-                style={{
-                  background: 'none',
-                  border: 'none',
-                  padding: 0,
-                  color: 'var(--primary)',
-                  fontWeight: 600,
-                  cursor: 'pointer',
-                  textDecoration: 'underline',
-                  textUnderlineOffset: '2px',
-                }}
               >
-                Undo and restore profile
-              </button>
+                <Icon name="refresh" size={14} /> Restore {lastDeleted.label}
+              </Button>
             </div>
           )}
           <EmptyState
@@ -160,43 +130,6 @@ export function ProfilesScreen({ onCreateProfile }: ProfilesScreenProps) {
           </p>
         )}
 
-        {lastDeleted && (
-          <div
-            className="undo-bar"
-            style={{
-              margin: '12px 0',
-              padding: '10px 14px',
-              background: 'var(--primary-soft)',
-              border: '1px solid var(--border)',
-              borderRadius: '8px',
-              display: 'flex',
-              alignItems: 'center',
-              gap: '8px',
-              flexWrap: 'wrap',
-            }}
-          >
-            <span style={{ color: 'var(--text)', fontWeight: 500 }}>
-              Profile “{lastDeleted.label}” deleted.
-            </span>
-            <span style={{ color: 'var(--text-muted)' }}>—</span>
-            <button
-              onClick={() => void undoDelete()}
-              style={{
-                background: 'none',
-                border: 'none',
-                padding: 0,
-                color: 'var(--primary)',
-                fontWeight: 600,
-                cursor: 'pointer',
-                textDecoration: 'underline',
-                textUnderlineOffset: '2px',
-              }}
-            >
-              Undo and restore profile
-            </button>
-          </div>
-        )}
-
         <div className="profile-grid">
           {profiles.map((profile) => (
             <article
diff --git a/frontend/src/state/AppProvider.tsx b/frontend/src/state/AppProvider.tsx
index 473d782..0970bf4 100644
--- a/frontend/src/state/AppProvider.tsx
+++ b/frontend/src/state/AppProvider.tsx
@@ -71,9 +71,8 @@ interface AppContextValue {
   signerDisconnect: () => Promise<SignerStatus>;
   signerStatus: () => Promise<SignerStatus>;
   signerApprove: (id: string, approved: boolean) => Promise<SignerStatus>;
-  deleteProfile: (npub: string) => Promise<AppState>;
-  undoDelete: () => Promise<AppState>;
-  clearLastDeleted: () => void;
+  deleteProfile: (npub: string) => Promise<ProfileSummary>;
+  undoDelete: () => Promise<ProfileSummary>;
   copyText: (text: string) => Promise<void>;
 }
 
@@ -235,18 +234,11 @@ export function AppProvider({ children }: { children: ReactNode }) {
     return api.signerApprove(id, approved);
   }, []);
 
-  const deleteProfile = useCallback(
-    (npub: string) => applyState(api.deleteProfile(npub)),
-    [applyState],
-  );
-  const undoDelete = useCallback(() => applyState(api.undoDelete()), [applyState]);
+  const deleteProfile = useCallback((npub: string) => api.deleteProfile(npub), []);
+  const undoDelete = useCallback(() => api.undoDelete(), []);
 
   const copyText = useCallback((text: string) => api.copyText(text), []);
 
-  const clearLastDeleted = useCallback(() => {
-    setState((prev) => (prev ? { ...prev, undo_history: prev.undo_history?.slice(0, -1) } : prev));
-  }, []);
-
   useEffect(() => {
     if (state?.settings.theme) {
       applyTheme(state.settings.theme);
@@ -292,7 +284,6 @@ export function AppProvider({ children }: { children: ReactNode }) {
       setProfilePicture,
       renameProfile,
       setNip05,
-      clearLastDeleted,
       copyText,
     }),
     [
@@ -307,7 +298,6 @@ export function AppProvider({ children }: { children: ReactNode }) {
       setProfilePicture,
       renameProfile,
       setNip05,
-      clearLastDeleted,
       publishNote,
       deleteProfile,
       undoDelete,
diff --git a/frontend/src/test/fakeBackend.ts b/frontend/src/test/fakeBackend.ts
index ccef5e5..cd5d0d7 100644
--- a/frontend/src/test/fakeBackend.ts
+++ b/frontend/src/test/fakeBackend.ts
@@ -451,47 +451,6 @@ export function createFakeBackend(initial?: AppState): FakeBackend {
         return { hex, nsec: `nsec1${npub.slice(5)}` };
       }
 
-      case 'delete_profile': {
-        const npub = String(params.npub);
-        const idx = state.profiles.findIndex((p) => p.npub === npub);
-        if (idx === -1) throw new Error('That profile is not stored on this computer.');
-        const [deleted] = state.profiles.splice(idx, 1);
-        const wasActive = state.active_profile?.npub === npub;
-        const next: AppState = {
-          ...state,
-          profiles: [...state.profiles],
-          active_profile: wasActive ? null : state.active_profile,
-          undo_history: [...(state.undo_history ?? []), { ...deleted, is_active: false }],
-        };
-        // clear active flag on remaining profiles if needed
-        if (wasActive) {
-          next.profiles = next.profiles.map((p) => ({ ...p, is_active: false }));
-        }
-        backend.setState(next);
-        return next;
-      }
-
-      case 'undo_delete': {
-        const hist = state.undo_history ?? [];
-        if (hist.length === 0) throw new Error('No profile deletions to undo.');
-        const restored = hist[hist.length - 1];
-        const next: AppState = {
-          ...state,
-          profiles: [...state.profiles, { ...restored, is_active: state.active_profile === null }],
-          active_profile: state.active_profile ?? { ...restored, is_active: true },
-          undo_history: hist.slice(0, -1),
-        };
-        // ensure only one active
-        if (state.active_profile === null) {
-          next.profiles = next.profiles.map((p) => ({
-            ...p,
-            is_active: p.npub === restored.npub,
-          }));
-        }
-        backend.setState(next);
-        return next;
-      }
-
       default:
         throw new Error(`Unknown method: ${method}`);
     }
diff --git a/src/ipc.rs b/src/ipc.rs
index f5554d9..e1ec407 100644
--- a/src/ipc.rs
+++ b/src/ipc.rs
@@ -146,10 +146,6 @@ pub enum Request {
         /// `true` to run the request, `false` to reject it.
         approved: bool,
     },
-    DeleteProfile {
-        npub: String,
-    },
-    UndoDelete,
 }
 
 /// A reply envelope carrying either data or a safe user-facing error.
@@ -532,17 +528,6 @@ async fn run_with_app(app: &mut App, request: Request) -> Result<serde_json::Val
             app.save_settings()?;
             Ok(json!(app.settings))
         }
-        Request::DeleteProfile { npub } => {
-            let deleted = profiles::delete_profile(&mut app.vault, &npub)?;
-            app.save_vault()?;
-            app.undo_history.push(deleted.clone());
-            Ok(json!(app.state_view()))
-        }
-        Request::UndoDelete => {
-            let restored = app.undo_delete()?;
-            app.save_vault()?;
-            Ok(json!(app.state_view()))
-        }
         // Signer control requests are handled by `run` before this function is
         // reached; keeping a wildcard arm keeps the match exhaustive here.
         _ => Err(AppError::internal("Unexpected signer request.")),
diff --git a/src/profiles.rs b/src/profiles.rs
index ac55397..b6ba18a 100644
--- a/src/profiles.rs
+++ b/src/profiles.rs
@@ -596,28 +596,6 @@ pub fn parse_secret_key(hex_str: &str) -> Result<SecretKey, AppError> {
     SecretKey::from_slice(&bytes).map_err(|e| AppError::invalid_secret(format!("{e}")))
 }
 
-/// Delete a profile by npub, returning the deleted profile for undo.
-/// The vault must not be encrypted, or the key must be provided.
-pub fn delete_profile(vault: &mut Vault, npub: &str) -> Result<ProfileSummary, AppError> {
-    let pos = vault
-        .profiles
-        .iter()
-        .position(|p| p.public_key == npub)
-        .ok_or_else(|| AppError::profile_not_found(npub))?;
-    let stored = vault.profiles.remove(pos);
-    if vault.active_profile.as_deref() == Some(npub) {
-        vault.active_profile = None;
-    }
-    Ok(ProfileSummary {
-        label: stored.label,
-        npub: stored.public_key,
-        created_at: stored.created_at,
-        is_active: false,
-        picture: stored.picture,
-        nip05: stored.nip05,
-    })
-}
-
 #[cfg(test)]
 mod tests {
     use super::*;
@@ -1082,4 +1060,27 @@ mod tests {
         .expect_err("missing profile must error");
         assert_eq!(err.kind(), crate::errors::ErrorKind::ProfileNotFound);
     }
+
+    /// Delete a profile by npub, returning the deleted profile for undo.
+    /// The vault must not be encrypted, or the key must be provided.
+    pub fn delete_profile(vault: &mut Vault, npub: &str) -> Result<ProfileSummary, AppError> {
+        let pos = vault
+            .profiles
+            .iter()
+            .position(|p| p.public_key == npub)
+            .ok_or_else(|| AppError::profile_not_found(npub))?;
+        let stored = vault.profiles.remove(pos);
+        // Clear the active_profile if it was the one deleted
+        if vault.active_profile.as_deref() == Some(npub) {
+            vault.active_profile = None;
+        }
+        Ok(ProfileSummary {
+            label: stored.label,
+            npub: stored.public_key,
+            created_at: stored.created_at,
+            is_active: false,
+            picture: stored.picture,
+            nip05: stored.nip05,
+        })
+    }
 }