docs: AML scope note, human-blocked items, Task #11 pre-flight inventory

- Add AML scope note to Handoff - RN Multichain Probe (sanctions-only vs full KYT)
- Add human-blocked section with 3 precise next steps for owner
- Create Task 11 Pre-flight Inventory: library choice, dev/prod flow, admin UI gaps, backend gaps, risks, acceptance criteria

04 - Flows/Payment Flow - DePay & Web3.md

@@ -63,7 +63,7 @@ Legacy alternative pay-in path: the buyer connects their own wallet (MetaMask /
     - Optionally decodes the `Transfer` event log to confirm `from`, `to`, and `value` match the expected payment.
 13. On success the backend:
     - Updates the `Payment`: `status = 'completed'`, `escrowState = 'funded'`, `blockchain.transactionHash`, `blockchain.confirmations`, `blockchain.confirmedAt = now`.
-    - Triggers the **same cascade** as the SHKeeper webhook: mark winning offer accepted, reject others, transition request to `payment`, create chat, send notifications, emit socket events.
+    - Triggers the **same funded-escrow cascade**: mark winning offer accepted, reject others, transition request to `payment`, create chat, send notifications, emit socket events.
 14. Returns `{ status: 'confirmed', confirmations, blockNumber }`.
 
 ### Phase 6 — Frontend reaction
@@ -123,8 +123,8 @@ sequenceDiagram
 
 ## Database writes
 
-- **`payments`** — same model as the SHKeeper flow. `provider` distinguishes the source.
-- **`selleroffers`**, **`purchaserequests`**, **`chats`**, **`notifications`** — identical cascade to [[Payment Flow - SHKeeper]] (offer accepted, others rejected, request → `payment`, chat created, notifications fanned out).
+- **`payments`** — same model as the Request Network flow. `provider` distinguishes the source.
+- **`selleroffers`**, **`purchaserequests`**, **`chats`**, **`notifications`** — identical funded-escrow cascade (offer accepted, others rejected, request → `payment`, chat created, notifications fanned out).
 
 ## Socket events emitted