handle
Routes one inbound session_request into the engine and maps the reply.
The engine never throws for protocol failures — it returns a JSON-RPC error — so this maps error responses to WcResponse.Error (carrying the CIP-0103 / EIP-1193 code) and everything else to WcResponse.Success.
Answered exactly once per (topic, requestId). WalletConnect clients re-emit a still-pending request (on reconnect, on foreground, after a respond) and the relay can redeliver one; a duplicate waits for, or reuses, the first answer instead of reaching the engine, and the user, a second time. For a payment that is the difference between one approver and two.