docs: qualify failed purchases and saved revocation

llms.txt

@@ -49,7 +49,7 @@
 - [Connect an application](https://bitcoinuniverseio.github.io/docs-wallet/tasks/connect-an-application): Approve a site's connection request, choose the idle window, and check the one line on the screen that a hostile page cannot forge.
 - [Hardware wallets](https://bitcoinuniverseio.github.io/docs-wallet/tasks/hardware-wallet): Keystone is the one hardware integration present in this build. Ledger and Trezor are shown as coming soon and cannot be connected.
 - [Locking and passwords](https://bitcoinuniverseio.github.io/docs-wallet/tasks/lock-and-password): What the password actually protects, how to set the auto-lock window, and what changing a password does and does not do.
-- [Manage connections](https://bitcoinuniverseio.github.io/docs-wallet/tasks/manage-connections): See every site that can reach the wallet, what each one can read, when it was last used, and how to end one or all of them.
+- [Manage connections](https://bitcoinuniverseio.github.io/docs-wallet/tasks/manage-connections): Identify connected sites by origin and chain, read the displayed connection state, and verify that revocation was saved.
 - [Receive](https://bitcoinuniverseio.github.io/docs-wallet/tasks/receive): Get an address, create a payment request with an amount and a note, and understand what appears while a payment is still unconfirmed.
 - [Review a PSBT](https://bitcoinuniverseio.github.io/docs-wallet/tasks/review-a-psbt): How to read a partially signed transaction someone else built, which sighash flags change what you are agreeing to, and when to refuse outright.
 - [Review a transaction](https://bitcoinuniverseio.github.io/docs-wallet/tasks/review-a-transaction): How to read the approval screen in the order it is built, the four lines that matter most, and the ones that should make you reject.

src/content/docs/tasks/activity.mdx

@@ -2,9 +2,9 @@
 title: Read your activity
 description: What pending really means, how many confirmations to wait for, and what to do about a transaction that will not confirm.
 sourceRepo: bitcoinuniverseio/wallet
-sourcePath: frontend/ui/pages/Wallet/HistoryScreen.tsx
+sourcePath: frontend/ui/pages/Wallet/HistoryScreen/index.tsx
 lifecycle: experimental
-lastVerified: 2026-09-01
+lastVerified: 2026-09-17
 ---
 
 import { Aside } from '@astrojs/starlight/components';
@@ -19,7 +19,13 @@ import { Aside } from '@astrojs/starlight/components';
 | --- | --- |
 | Pending | Broadcast, sitting in the mempool, not in a block. It can still be dropped. |
 | Confirmed | Included in a block. Each new block adds a confirmation. |
-| Failed | The network rejected it. Nothing moved and no fee was paid. |
+| Failed | A failure was reported. Check the recorded evidence to distinguish a rejected request from an unknown outcome. |
+
+A timeout, interrupted page or error message alone does not establish that no funds moved or no fee
+was paid. For a marketplace purchase, keep the existing execution or request reference and return to
+that purchase to check its recorded status. Do not start a replacement purchase or clear wallet
+storage to resolve an uncertain outcome. See
+[Zcash market listings](/docs-wallet/assets/zcash-market-listings).
 
 ## How many confirmations
 

src/content/docs/tasks/manage-connections.md

@@ -1,31 +1,34 @@
 ---
 title: Manage connections
-description: See every site that can reach the wallet, what each one can read, when it was last used, and how to end one or all of them.
+description: Identify connected sites by origin and chain, read the displayed connection state, and verify that revocation was saved.
 sourceRepo: bitcoinuniverseio/wallet
-sourcePath: frontend/ui/pages/ConnectedSites
+sourcePath: frontend/ui/pages/Approval/ConnectedSitesScreen.tsx, backend/background/service/permission.ts
 lifecycle: experimental
-lastVerified: 2026-09-01
+lastVerified: 2026-09-17
 ---
 
 **Intended reader:** anyone who has connected sites, which is anyone who has used a marketplace.
 **Goal:** a connection list you recognise, with nothing on it you cannot account for.
 **Prerequisites:** an unlocked wallet.
-**Safety:** disconnecting is always safe. It cannot lose funds and cannot break anything permanently.
+**Safety:** disconnecting cannot retract a signature or transaction already delivered.
 
 ## Steps
 
 1. Open **Connected sites**.
-2. Read the list. Each entry shows the origin, the address and network it can read, and when it was
-   last used.
+2. Read the exact origin and displayed chain for each entry. A site name or icon is not its identity.
 3. Disconnect anything you do not recognise, or no longer use.
-4. There is a control to end every connection at once. Use it if you are unsure.
+4. If you use a group revoke action, check the result for each affected site.
+5. Wait for the wallet to confirm that removal was saved. Reload the wallet's connection list and
+   verify that the unwanted entry is gone.
 
 ## What the list tells you
 
-- **Origin.** What the browser reported. This is the identity that matters.
-- **Scope.** Which address, on which network, this site can read.
-- **Last used.** How recently it interacted with the wallet. An old date on a site you use daily
-  means it is not the connection you think it is.
+- **Origin.** The exact website origin reported to the wallet.
+- **Chain.** The chain shown on the connection card.
+- **Signature status.** The card shows **Signed** or **Unsigned**. This does not replace reviewing
+  a new signature request.
+- **Connection state.** The card shows **Active** or **Stored only** for the saved record.
+- **Expiry.** Read the expiry text displayed for that connection.
 
 Universe Wallet also scores connections for risk locally, on your device, and offers to revoke risky
 sites in one step.
@@ -39,12 +42,13 @@ sites in one step.
 
 ## Expected result
 
-The list contains only sites you recognise and still use. Disconnected sites must ask again from the
-beginning, and you see the full approval screen when they do.
+After the wallet confirms removal, the origin should be absent from a successfully refreshed list.
+The disconnected site must request access again. A failed save or read does not establish that
+access ended.
 
 ## What disconnecting does not do
 
-Disconnecting stops a site from asking for anything new. It does not:
+A successfully saved disconnect ends the site's saved wallet access. It does not:
 
 - reverse a transaction you approved,
 - revoke a signature you already gave, including a partial signature someone can still complete,
@@ -61,8 +65,13 @@ If you are here because something went wrong, disconnect first, then go to
 | What you see | What it means | What to do |
 | --- | --- | --- |
 | A site you do not recognise | You connected and forgot, or a page you visited requested it | Disconnect. Then check activity for anything you did not authorize. |
-| A site reappears after disconnecting | It requested again and you approved again | Read the approval window before approving |
-| A site still shows you as connected on its own page | Its display is stale | The wallet's list is authoritative. Reload the page. |
+| The connection list cannot be loaded | Current permissions could not be read | Retry the read. A load error is not an empty permission list. |
+| Disconnect or revoke fails | Removal has not been confirmed | Retry, then reload the wallet list. Treat access as unresolved until the saved result is verified. |
+| A site reappears after disconnecting | Removal may not have been saved, or a new connection was approved | Check the saved result and read any new approval before accepting it. |
+| A site still shows you as connected on its own page | Its display may be stale | Confirm removal in a successfully refreshed wallet list, then reload the site. |
+
+Keep wallet storage intact while resolving a failed permission read or write. If the failure
+continues, use [support](/docs-wallet/help/support).
 
 ## Related