fix: run libsodium on WebAssembly under the extension CSP (closes #182)

libsodium ships a WASM build and a wasm2js translation in one file, tries
WASM first, and silently falls back if instantiation throws. Under a plain
script-src 'self' the fallback was taken on every popup load, announced by
nothing but an uncaught CompileError.

Measured on the vault's own Argon2id parameters (OPSLIMIT_INTERACTIVE,
MEMLIMIT_INTERACTIVE), node 22: WASM 141-198ms per derivation, wasm2js
3204-3660ms. The work factor is identical either way — it is set by the
ops and memory parameters, not by wall time — so the fallback bought no
security and cost about 3.5s on every operation that asks for the
password, which is every signature.

Both manifests now declare script-src 'self' 'wasm-unsafe-eval';
object-src 'self' for extension pages: an object under
content_security_policy.extension_pages for Chrome MV3, a bare string for
Firefox MV2. The keyword permits compiling WebAssembly and nothing else —
not eval() of strings, not inline script, not remote script — and reaching
it requires already executing script in an extension page. 'unsafe-eval'
is not granted.

The silence is what made this dangerous, so the fallback is now loud at
three levels: tests/manifest.test.js pins both policies to exactly that
token set, failing make check if the grant is dropped or if anything is
added beside it; tests/vaultBackend.test.js asserts the unit tests
exercise the WASM backend, with a self-validating check that libsodium
never swapped its fallback in; and the e2e suite compiles a WebAssembly
module inside the real popup under the real manifest, with the harness
allowlist entry that used to excuse the CompileError now deleted.

The runtime fallback itself is kept — a wallet that refuses to decrypt is
worse than a slow one — but vault.js now reports the backend and logs an
error when it is not WASM.

README.md

@@ -272,10 +272,10 @@ on a different table knows exactly tf I am talking about.
 
 Every interactive element must visually indicate that it is clickable. Buttons
 use a visible border, padding, and a hover state (invert to white-on-black).
-Text that triggers an action (e.g. "Add additional wallet...") uses an
+Text that triggers an action (e.g. "Import private key") uses an underline. No
-underline. No invisible hit targets, no bare text that happens to have a click
+invisible hit targets, no bare text that happens to have a click handler. If it
-handler. If it does something when you click it, it must look like it does
+does something when you click it, it must look like it does something when you
-something when you click it.
+click it.
 
 #### Display Consistency
 
@@ -335,18 +335,12 @@ attack.
 
 The core hierarchy is **Wallets → Addresses**:
 
-- A **wallet** is one of three types:
+- A **wallet** is either:
-    - An **HD wallet** (`type: "hd"`, recovery phrase): generates multiple
+    - An **HD wallet** (recovery phrase): generates multiple addresses from a
-      addresses from a single 12/24 word recovery phrase using BIP-39/BIP-44
+      single 12/24 word recovery phrase using BIP-39/BIP-44 derivation. The user
-      derivation. The user can add more addresses with a "+" button.
+      can add more addresses with a "+" button.
-    - A **key wallet** (`type: "key"`, private key): a single address imported
+    - A **key wallet** (private key): a single address imported directly from a
-      directly from a private key. No "+" button since there is only one
+      private key. No "+" button since there is only one address.
-      address.
-    - An **xprv wallet** (`type: "xprv"`, extended private key): the same
-      multi-address behavior as an HD wallet, including the "+" button and the
-      address scan on import, but imported from an extended private key rather
-      than a recovery phrase. It therefore has no recovery phrase to display or
-      back up.
 - An **address** holds ETH and any user-added ERC-20 tokens.
 - The user can have multiple wallets, each with multiple addresses (HD) or a
   single address (key).
@@ -361,140 +355,95 @@ menus.
 
 ### Screen Map
 
-Navigation uses a stack model (like iOS): each forward action pushes the current
+Navigation uses a stack model (like iOS): each action pushes a screen onto the
-screen onto `state.viewStack`, and "Back" pops it (`pushCurrentView()` and
+stack, and "Back" pops it. The root screen is either Welcome (no wallets) or
-`goBack()` in `src/popup/views/helpers.js`). The root screen is either Welcome
+Home (has wallets). Screens are listed below with their elements and
-(no wallets) or Home (has wallets). Each screen below gives its view id in
+transitions.
-parentheses; the registry of view ids is the `VIEWS` array in
-`src/popup/views/helpers.js`, and the markup for a screen is the element with id
-`view-` plus that view id in `src/popup/index.html`.
 
-Three elements sit outside the screens and are present on all of them: the title
+#### Welcome
-bar ("AutistMask by @sneak" plus the Settings gear), the flash message line
-under it, and the red banner at the very top that appears on a debug build, when
-runtime debug mode is on, or when the active network is a testnet. They are not
-repeated in the element lists below.
 
-Closing and reopening the popup returns to the screen the user was last on only
+- **When**: No wallets exist yet.
-for the views listed in `RESTORABLE_VIEWS` (`src/popup/index.js`). Every other
+- **Elements**: "AutistMask" heading, brief intro text, "Add wallet" button.
-screen, including ExportPrivKey, falls back to Home.
-
-#### Welcome (`welcome`)
-
-- **When**: No wallets exist yet (`state.hasWallet` is false). This is the root
-  screen in that case.
-- **Elements**:
-    - "Welcome! To get started, add a wallet." text
-    - "Add wallet" button
 - **Transitions**:
     - "Add wallet" → **AddWallet**
 
-#### Home (`main`)
+#### Home
 
 - **When**: At least one wallet exists. This is the root screen.
 - **Elements**:
-    - Active address ETH balance (large) + USD value in parentheses
+    - Header: "AutistMask", Settings gear button
-    - "Total:" USD value across ETH and all tracked tokens of the active address
+    - Active address ETH balance (large) + USD value (inline parentheses)
+    - Total USD value across all tokens (small text)
     - Active address (color dot, full address, etherscan link, tap to copy)
-    - Send / Receive quick-action buttons, both acting on the active address
+    - Send / Receive quick-action buttons
     - ETH/USD price display
-    - Wallet list: each wallet shows its name (tap to rename inline) and a "+"
+    - Wallet list: each wallet shows name (tap to rename), "+" button (HD only),
-      button for HD and xprv wallets, then one block per address with "Address
+      and its addresses with color dots, balances, and `[info]` buttons
-      N" (bold when active), the ENS name if resolved, the full address, an
+    - Recent transactions across all addresses (merged, deduplicated, filtered)
-      `[info]` button, the address USD total, and a balance line for ETH and for
-      each tracked token
-    - "Recent Transactions": up to 25 transactions merged across every address
-      of every wallet, deduplicated by hash and filtered
     - "Add additional wallet..." link at bottom
 - **Transitions**:
-    - Tap address row → sets the active address and broadcasts
+    - Tap address row → sets active address (no screen change)
-      `AUTISTMASK_ACTIVE_CHANGED` (no screen change)
-    - Tap wallet name → inline rename field (no screen change)
-    - "+" on wallet → derives the next address inline (no screen change)
     - `[info]` on address → **AddressDetail**
-    - "Send" → **Send** (refuses with a flash message on a zero balance)
+    - "Send" → **Send** (selects active address)
     - "Receive" → **Receive** (shows active address QR)
-    - Tap home tx row → **TransactionDetail**
+    - "+" on wallet → derives next address inline
     - "Add additional wallet..." → **AddWallet**
     - Settings gear → **Settings** (toggles; tap again to return)
+    - Tap home tx row → **AddressDetail** (for the address involved)
 
-#### AddWallet (`add-wallet`)
+#### AddWallet
 
-- **When**: User wants to add a new wallet (from Welcome, Home, or Settings).
+- **When**: User wants to add a new wallet (from Home, Welcome, or Settings).
-  This one screen covers all three import modes; there is no separate import
-  screen.
 - **Elements**:
-    - "Back" button, "Add Wallet" heading
+    - "Add Wallet" heading, "Back" button
-    - Three tabs — "From Phrase" (`tab-mnemonic`), "From Key" (`tab-privkey`),
+    - Instruction text
-      "From xprv" (`tab-xprv`) — each showing its own form section:
+    - Die button `[die]` (generates random recovery phrase)
-        - **From Phrase**: instruction text, a die button that generates a
+    - Recovery phrase textarea
-          random recovery phrase, a recovery phrase textarea, and a backup
+    - Backup warning box (shown after die is clicked)
-          warning box that becomes visible once the die button has been used
+    - Password + confirm password inputs
-        - **From Key**: instruction text and a masked private key input
+    - "Add" button
-        - **From xprv**: instruction text and a masked extended private key
+    - "Have a private key instead?" link
-          input
+- **Transitions**:
-    - Password + confirm password inputs, with a hint line whose wording depends
+    - "Add" (valid phrase + password) → **Home**
-      on the selected tab
+    - "Back" → previous screen (Home or Welcome)
+    - "Have a private key instead?" → **ImportKey**
+
+#### ImportKey
+
+- **When**: User wants to import a single private key.
+- **Elements**:
+    - "Import Private Key" heading, "Back" button
+    - Instruction text
+    - Private key input (password-masked)
+    - Password + confirm password inputs
     - "Import" button
 - **Transitions**:
-    - "Import" with a valid entry and a matching password of at least 12
+    - "Import" (valid key + password) → **Home**
-      characters → creates the wallet, clears the navigation stack, and →
+    - "Back" → **AddWallet**
-      **Home**. The phrase and xprv modes then scan for further used addresses
-      and report the count as a flash message.
-    - "Import" with an invalid entry, a duplicate wallet or address, or a short
-      or mismatched password → flash message, no screen change
-    - "Back" → previous screen (Welcome, Home, or Settings)
 
-#### AddressDetail (`address`)
+#### AddressDetail
 
 - **When**: User tapped `[info]` on an address from Home.
 - **Elements**:
     - "Back" button
     - Blockie identicon (48px, centered)
     - Title: "Wallet Name — Address N"
-    - ENS name (if resolved, bold above the address)
+    - ENS name (if resolved, bold with color dot)
     - Full address (color dot, etherscan link, tap to copy)
     - USD total for address
     - Balance list: ETH + tracked ERC-20 tokens (4 decimal places, USD inline).
       Each balance row is clickable → **AddressToken**
-    - Send / Receive / + Token buttons and a "···" menu button
+    - Send / Receive / + Token buttons
-    - "···" dropdown containing a single "Export Private Key" entry
     - Transaction list (with ENS resolution for counterparties)
 - **Transitions**:
     - Tap balance row → **AddressToken** (for that token)
-    - "Send" → **Send** (refuses with a flash message on a zero balance)
+    - "Send" → **Send**
     - "Receive" → **Receive**
     - "+ Token" → **AddToken**
-    - "···" → "Export Private Key" → **ExportPrivKey**
     - Tap transaction row → **TransactionDetail**
-    - "Back" → previous screen (Home)
+    - "Back" → **Home**
 
-#### ExportPrivKey (`export-privkey`)
+#### AddressToken
-
-- **When**: User chose "Export Private Key" from the "···" menu on
-  AddressDetail. This screen discloses secret material.
-- **Elements**:
-    - "Back" button
-    - Blockie identicon (48px, centered)
-    - "Export Private Key" heading
-    - "Wallet Name — Address N" and the full address (etherscan link, tap to
-      copy)
-    - Warning that anyone holding the private key can transfer all funds from
-      the address
-    - Error line
-    - Password input and "Reveal" button, shown until the key is revealed
-    - The private key on a highlighted background, tap to copy, shown only after
-      the password has been accepted
-- **Transitions**:
-    - "Reveal" (correct password) → decrypts the wallet secret, derives this
-      address's key, hides the password input and shows the key (no screen
-      change)
-    - "Reveal" (wrong password) → "Wrong password." on the error line, nothing
-      revealed
-    - "Back" → clears the key and password from the DOM, then → previous screen
-      (AddressDetail)
-
-#### AddressToken (`address-token`)
 
 - **When**: User clicked a specific token balance on AddressDetail.
 - **Elements**:
@@ -505,64 +454,49 @@ screen, including ExportPrivKey, falls back to Home.
     - USD total for this token
     - Single token balance line (4 decimal places)
     - Send / Receive buttons
-    - Token contract well (ERC-20 only): full contract address (tap to copy,
-      etherscan link) plus name, symbol, decimals, holder count and project
-      website where known
     - Token-filtered transaction list (only this token's transfers)
 - **Transitions**:
-    - "Send" → **Send** (token locked: the dropdown is replaced by a static
+    - "Send" → **Send** (token pre-selected and locked in dropdown)
-      symbol and contract address)
     - "Receive" → **Receive** (ERC-20 warning shown for non-ETH tokens)
     - Tap transaction row → **TransactionDetail**
-    - "Back" → previous screen (AddressDetail)
+    - "Back" → **AddressDetail**
 
-#### Send (`send`)
+#### Send
 
-- **When**: User wants to send ETH or a token, from Home, AddressDetail, or
+- **When**: User wants to send ETH or a token from this address.
-  AddressToken.
 - **Elements**:
-    - "Back" button, "Send" heading
+    - "Send" heading, "Back" button
     - From: address with color dot + etherscan link
     - What to send: token dropdown (or static display with contract address when
       locked from AddressToken)
-    - To: address or ENS name input, with an inline validation message
+    - To: address or ENS name input
     - Amount input with current balance display
-    - "Review" button, disabled until the recipient validates
+    - "Review" button
 - **Transitions**:
     - "Review" (valid inputs, ENS resolved) → **ConfirmTx**
-    - "Review" with an unresolvable ENS name or an invalid amount → flash
+    - "Back" → **AddressToken** (if came from token view) or **AddressDetail**
-      message, no screen change
-    - "Back" → previous screen (Home, AddressDetail, or AddressToken)
 
-#### ConfirmTx (`confirm-tx`)
+#### ConfirmTx
 
 - **When**: User reviewed send details and is ready to authorize.
 - **Elements**:
-    - "Back" button, "Confirm Transaction" heading
+    - "Confirm Transaction" heading, "Back" button
     - Type: "Native ETH transfer" or "ERC-20 token transfer (SYMBOL)"
     - Token contract: full address + etherscan link (ERC-20 only)
     - From: blockie + color dot + full address + etherscan link + wallet title
     - To: blockie + color dot + full address + etherscan link + ENS name
     - Amount: value + symbol (USD in parentheses)
     - Your balance: value + symbol (USD in parentheses)
-    - Estimated network fee: "Estimating..." then the ETH amount (USD in
+    - Estimated network fee: ETH amount (USD in parentheses), fetched async
-      parentheses) or "Unable to estimate", fetched async
+    - Warnings (scam address, self-send)
-    - Warnings: inline warnings from the local checks (scam address, self-send)
-      plus four reserved warning boxes made visible by the async checks —
-      recipient with no transaction history, recipient is a contract, burn
-      address, and an Etherscan phishing/scam label
     - Errors (insufficient balance)
-    - Password: an inline field on this screen, not a modal, with its own error
+    - "Send" button (disabled if errors)
-      line
-    - "Sign & Send" button (disabled if errors)
 - **Transitions**:
-    - "Sign & Send" (correct password) → broadcast tx → **WaitTx**
+    - "Send" → password modal → broadcast tx → **WaitTx**
-    - "Sign & Send" (correct password) → broadcast fails → **ErrorTx**
+    - "Send" → password modal → broadcast fails → **ErrorTx**
-    - "Sign & Send" (wrong password) → "Wrong password." on the password error
-      line, no screen change
     - "Back" → **Send**
 
-#### WaitTx (`wait-tx`)
+#### WaitTx
 
 - **When**: Transaction has been broadcast, waiting for on-chain confirmation.
 - **Elements**:
@@ -576,24 +510,20 @@ screen, including ExportPrivKey, falls back to Home.
     - Receipt found → **SuccessTx**
     - 60 seconds without confirmation → **ErrorTx** (timeout message)
 
-#### SuccessTx (`success-tx`)
+#### SuccessTx
 
 - **When**: Transaction confirmed on-chain.
 - **Elements**:
     - "Transaction Confirmed" heading
-    - Decoded action well (shown when the transaction carried recognized
-      calldata; the top-level Amount and To are hidden in that case)
     - Amount + symbol
     - To: color dot + full address + etherscan link
     - Block number
     - Transaction hash: full hash (tap to copy) + etherscan link
     - "Done" button
 - **Transitions**:
-    - "Done" in the approval popup → closes the popup window
+    - "Done" → **AddressToken** (if `selectedToken` set) or **AddressDetail**
-    - "Done" otherwise → resets the navigation stack, then → **AddressToken**
-      (if `selectedToken` set) or **AddressDetail**
 
-#### ErrorTx (`error-tx`)
+#### ErrorTx
 
 - **When**: Transaction broadcast failed, or timed out waiting for confirmation.
 - **Elements**:
@@ -605,28 +535,24 @@ screen, including ExportPrivKey, falls back to Home.
       full hash (tap to copy) + etherscan link
     - "Done" button
 - **Transitions**:
-    - "Done" in the approval popup → closes the popup window
+    - "Done" → **AddressToken** (if `selectedToken` set) or **AddressDetail**
-    - "Done" otherwise → resets the navigation stack, then → **AddressToken**
-      (if `selectedToken` set) or **AddressDetail**
 
-#### Receive (`receive`)
+#### Receive
 
-- **When**: User wants to receive funds at this address, from Home,
+- **When**: User wants to receive funds at this address.
-  AddressDetail, or AddressToken.
 - **Elements**:
-    - "Back" button, "Receive" heading
+    - "Receive" heading, "Back" button
     - Instruction text
     - QR code encoding the address
     - Full address (color dot, selectable, etherscan link)
     - "Copy address" button
     - ERC-20 warning (shown when navigating from AddressToken for non-ETH token)
 - **Transitions**:
-    - "Back" → previous screen (Home, AddressDetail, or AddressToken)
+    - "Back" → **AddressToken** (if `selectedToken` set) or **AddressDetail**
 
-#### TransactionDetail (`transaction`)
+#### TransactionDetail
 
-- **When**: User tapped a transaction row on Home, AddressDetail, or
+- **When**: User tapped a transaction row from AddressDetail or AddressToken.
-  AddressToken.
 - **Elements** (grouped into logical blocks using light well containers; field
   labels are self-explanatory so groups have no headings):
     - "Transaction" heading, "Back" button
@@ -651,182 +577,91 @@ screen, including ExportPrivKey, falls back to Home.
     - Raw data (shown when calldata is present): full calldata in monospace
       dashed border
 - **Transitions**:
-    - "Back" → previous screen (Home, AddressDetail, or AddressToken)
+    - "Back" → **AddressToken** (if `selectedToken` set) or **AddressDetail**
 
-#### AddToken (`add-token`)
+#### AddToken
 
-- **When**: User wants to track an ERC-20 token, reached from "+ Token" on
+- **When**: User wants to track an ERC-20 token on this address.
-  AddressDetail.
 - **Elements**:
-    - "Back" button, "Add Token" heading
+    - "Add Token" heading, "Back" button
     - Instruction text (find contract address on Etherscan)
     - Contract address input
-    - Status line ("Looking up token...", cleared or replaced on failure)
+    - Token info preview (name, symbol — fetched from contract)
-    - Common token quick-pick buttons (top 25 by market cap), which fill the
+    - Common token quick-pick buttons
-      contract address input
     - "Add" button
 - **Transitions**:
-    - "Add" (valid contract) → tracks the token, pops the stack, and re-renders
+    - "Add" (valid contract) → **AddressDetail**
-      **AddressDetail**
+    - "Back" → **AddressDetail**
-    - "Add" with a token already tracked, a scam-listed address, or a failed
-      contract lookup → flash message, no screen change
-    - "Back" → previous screen (AddressDetail)
 
-#### Settings (`settings`)
+#### Settings
 
-- **When**: User tapped the Settings gear.
+- **When**: User tapped Settings gear from Home.
 - **Elements**:
-    - "Back" button, "Settings" heading
+    - "Settings" heading, "Back" button
-    - Wallets: one row per wallet with its name (tap to rename inline) and an
+    - Wallets: "+ Add wallet" button
-      `[x]` delete button, plus a "+ Add wallet" button
+    - Display: "Show tracked tokens with zero balance" checkbox
-    - Tracked Tokens: one row per tracked token with an `[x]` remove button,
+    - Ethereum RPC: endpoint URL input + "Save" button
-      plus a "+ Add token" button
+    - Blockscout API: endpoint URL input + "Save" button
-    - Display: "Show tracked tokens with zero balance" checkbox and a Theme
-      selector (System / Light / Dark)
-    - Network: network selector (Ethereum Mainnet / Sepolia Testnet); switching
-      resets the RPC and Blockscout endpoints to that network's defaults
-    - Ethereum RPC: endpoint URL input + "Save" button (validated against
-      `eth_chainId` before being saved)
-    - Blockscout API: endpoint URL input + "Save" button (validated against
-      `/stats` before being saved)
     - Token Spam Protection:
         - "Hide tokens with fewer than 1,000 holders" checkbox
         - "Hide transactions from detected fraud contracts" checkbox
         - "Hide dust transactions below N gwei" checkbox + threshold input
-        - "UTC Timestamps" checkbox
     - Allowed Sites: list with remove buttons
     - Denied Sites: list with remove buttons
-    - About: project link, license, author, version, release date, and the
-      commit, which links to the commit in the repository
-    - Debug: hidden until revealed, then an "Enable debug mode" checkbox that
-      turns on the red banner and verbose logging
 - **Transitions**:
     - "+ Add wallet" → **AddWallet**
-    - "+ Add token" → **SettingsAddToken**
+    - "Back" (or Settings gear again) → **Home**
-    - `[x]` on a wallet → **DeleteWallet**
-    - Tap wallet name → inline rename field (no screen change)
-    - `[x]` on a tracked token or a site → removes it in place (no screen
-      change)
-    - Ten clicks on the version → reveals the Debug well (no screen change)
-    - "Back" (or Settings gear again) → previous screen (Home)
 
-#### DeleteWallet (`delete-wallet-confirm`)
+#### SiteApproval
 
-- **When**: User tapped the `[x]` next to a wallet in Settings.
+- **When**: A website requests wallet access via `eth_requestAccounts`. Opened
-- **Elements**:
+  in a separate popup by the background script.
-    - "Back" button, "Delete Wallet" heading
-    - Warning naming the wallet and stating that deletion is permanent and any
-      funds are unrecoverable without the recovery phrase
-    - Error line
-    - Password input
-    - "Confirm Delete" button
-- **Transitions**:
-    - "Confirm Delete" (correct password, other wallets remain) → deletes the
-      wallet and its site permissions, then → **Settings** with a "Wallet
-      deleted." flash message
-    - "Confirm Delete" (correct password, last wallet) → deletes the wallet,
-      clears the selection and the navigation stack, then → **Welcome**
-    - Either way, the active address moves only if it belonged to the deleted
-      wallet, and `AUTISTMASK_ACTIVE_CHANGED` is broadcast when it does
-      (`src/shared/walletDelete.js`)
-    - "Confirm Delete" (wrong password) → "Wrong password." on the error line,
-      nothing deleted
-    - "Back" → previous screen (Settings)
-
-#### SettingsAddToken (`settings-addtoken`)
-
-- **When**: User tapped "+ Add token" in Settings. Tokens added here are tracked
-  across every address, unlike AddToken which is reached from one address.
-- **Elements**:
-    - "Back" button, "Add Token" heading
-    - Instruction text
-    - "Top tokens:" quick-pick buttons (top 10 by market cap; already-tracked
-      tokens are disabled)
-    - "Or pick from top 100:" dropdown (already-tracked tokens are disabled) +
-      "Add selected" button
-    - "Or enter contract address:" input, a status line, and an "Add" button
-- **Transitions**:
-    - Any of the three add paths, on success → adds the token and shows an
-      "Added SYMBOL" flash message (no screen change)
-    - A duplicate, a scam-listed address, or a failed contract lookup → flash
-      message, no screen change
-    - "Back" → previous screen (Settings)
-
-#### SiteApproval (`approve-site`)
-
-- **When**: A website requests wallet access via `eth_requestAccounts` or
-  `wallet_requestPermissions` and is on neither the allowed nor the denied list.
-  The background script prefers the toolbar popup (`action.openPopup()`) and
-  falls back to a separate popup window (`src/background/index.js`,
-  `requestApproval()`).
 - **Elements**:
     - "Connection Request" heading
-    - Phishing warning banner (shown when the hostname is on the phishing
+    - Site hostname (bold)
-      blocklist)
-    - Site hostname (bold) + "wants to connect to your wallet"
     - Address that will be shared (color dot + full address + etherscan link)
     - "Remember my choice for this site" checkbox
     - "Allow" / "Deny" buttons
 - **Transitions**:
-    - "Allow" / "Deny" → closes popup (returns result to background script; the
+    - "Allow" / "Deny" → closes popup (returns result to background script)
-      choice is persisted to the allowed or denied list when "Remember" is
-      checked)
-    - Popup closed without answering → treated as a denial
 
-#### TxApproval (`approve-tx`)
+#### TxApproval
 
 - **When**: A connected website requests a transaction via
-  `eth_sendTransaction`. Always opened in a separate popup window by the
+  `eth_sendTransaction`. Opened via the toolbar popup by the background script.
-  background script (`windows.create()`), because the request is triggered
-  programmatically rather than by a user gesture.
 - **Elements**:
     - "Transaction Request" heading
-    - Phishing warning banner (shown when the hostname is on the phishing
-      blocklist)
     - Site hostname (bold) + "wants to send a transaction"
     - Decoded action (if calldata is recognized): action name, token details,
       amounts, steps, deadline (see Transaction Decoding)
     - From: color dot + full address + etherscan link
-    - Contract: color dot + full address + etherscan link (or "contract
+    - To/Contract: color dot + full address + etherscan link (or "contract
       creation"), token symbol label if known
-    - Value: amount in ETH (4 decimal places, USD in parentheses)
+    - Value: amount in ETH (4 decimal places)
     - Raw data: full calldata displayed inline (shown if present)
-    - Password input and an error line
+    - Password input
     - "Confirm" / "Reject" buttons
 - **Transitions**:
-    - "Confirm" (correct password) → decrypts and signs in the popup, hands the
+    - "Confirm" (with password) → closes popup (returns result to background)
-      signed transaction to the background to broadcast, then → **WaitTx** in
-      the same popup window
-    - "Confirm" (wrong password) → error line, no screen change
     - "Reject" → closes popup (returns rejection to background)
-    - Popup window closed without answering → the request is rejected with
-      EIP-1193 code 4001
 
-#### SignApproval (`approve-sign`)
+#### SignApproval
 
 - **When**: A connected website requests a message signature via
-  `personal_sign`, `eth_sign`, or `eth_signTypedData_v4`. Opened the same way as
+  `personal_sign`, `eth_sign`, or `eth_signTypedData_v4`. Opened via the toolbar
-  TxApproval, in a separate popup window.
+  popup by the background script.
 - **Elements**:
     - "Signature Request" heading
-    - Phishing warning banner (shown when the hostname is on the phishing
-      blocklist)
     - Site hostname (bold) + "wants you to sign a message"
-    - Danger warning box (shown for `eth_sign`, which signs a raw hash)
     - Type: "Personal message" or "Typed data (EIP-712)"
     - From: color dot + full address + etherscan link
     - Message: decoded UTF-8 text (personal_sign) or formatted domain/type/
       message fields (EIP-712 typed data)
-    - Password input and an error line
+    - Password input
     - "Sign" / "Reject" buttons
 - **Transitions**:
-    - "Sign" (correct password) → signs locally → closes popup (returns
+    - "Sign" (with password) → signs locally → closes popup (returns signature)
-      signature)
-    - "Sign" (wrong password, or a signing failure) → error line, no screen
-      change
     - "Reject" → closes popup (returns rejection to background)
-    - Popup window closed without answering → the request is rejected with
-      EIP-1193 code 4001
 
 ### External Services
 
@@ -1011,7 +846,6 @@ hardcoded test phrase.
 - Create new HD wallet (generates 12-word recovery phrase)
 - Import HD wallet from existing 12 or 24 word recovery phrase
 - Import single-address wallet from private key
-- Import multi-address wallet from an extended private key (`xprv`)
 - Add multiple addresses within an HD wallet
 - Manage multiple wallets simultaneously
 - View ETH balance per address
@@ -1183,7 +1017,7 @@ Currently supported:
 
 ### Transactions
 
-- [x] Gas estimation and fee display before confirming
+- [ ] Gas estimation and fee display before confirming
 
 ### Testing
 

TODO.md

@@ -49,9 +49,6 @@ undefined identifiers, which is how
   fallback at 20x the Argon2id cost, pinned in both directions by
   `tests/manifest.test.js` and observed in the real popup by the e2e suite
   ([#182](https://git.eeqj.de/sneak/AutistMask/issues/182)).
-- 2026-08-11: README Screen Map rebuilt from the code — every screen, element
-  and transition re-verified against `src/popup/`
-  ([#164](https://git.eeqj.de/sneak/AutistMask/issues/164)).
 - 2026-08-11: `docs/README.md` rewritten against the code: no competitor names,
   all five network destinations documented, password/Settings/Add Wallet
   sections corrected ([#163](https://git.eeqj.de/sneak/AutistMask/issues/163)).

src/shared/vault.js

@@ -47,12 +47,7 @@ const EMPTY_WASM_MODULE = new Uint8Array([
     0x00, 0x61, 0x73, 0x6d, 0x01, 0x00, 0x00, 0x00,
 ]);
 
-// "wasm" or "asmjs": whether this realm may compile WebAssembly, which is
+// "wasm" or "asmjs": the libsodium backend in use in this realm.
-// what decides libsodium's backend when the CSP is the reason it cannot —
-// the case this codebase guards. It probes the realm, not libsodium, so a
-// fallback taken for some other reason (allocation failure, corrupt module)
-// would not be caught here; tests/vaultBackend.test.js checks libsodium's
-// own marker directly.
 async function cryptoBackend() {
     try {
         await WebAssembly.compile(EMPTY_WASM_MODULE);

tests/manifest.test.js

@@ -79,17 +79,9 @@ describe("shipped Content Security Policy", () => {
         assertPolicy(csp.extension_pages);
     });
 
-    // MV2 takes the policy as a bare string. Firefox does not require
+    // MV2 takes the policy as a bare string, and Firefox 102 and later
-    // 'wasm-unsafe-eval' for MV2 today — enforcement is report-only and
+    // require 'wasm-unsafe-eval' for extension pages exactly as Chrome
-    // Bugzilla 1770909 is still open — so this is future-proofing, not a
+    // does. Same policy, different manifest shape.
-    // mandate. It does not weaken anything under either baseline: Gecko's
-    // real MV2 default (extensions.webextensions.default-content-security-
-    // policy) is `script-src 'self' 'wasm-unsafe-eval';` with no object-src
-    // at all, so this string leaves script-src unchanged and ADDS
-    // object-src 'self', constraining <object>/<embed> sources that were
-    // previously unrestricted. Against MDN's documented MV2 default
-    // (`script-src 'self'; object-src 'self';`) it is a one-token loosening,
-    // identical to Chrome. Same policy, different manifest shape.
     test("firefox MV2 allows WASM and nothing else beyond 'self'", () => {
         const csp = readManifest("firefox").content_security_policy;
         expect(typeof csp).toBe("string");