use-ekubo-walletlisted

# Use Ekubo Wallet Start with `wallet_list` and `list_networks`. Use their returned wallet IDs, addresses, and decimal chain IDs exactly; never guess an account or network. If “wallet” is ambiguous and crypto has not been ruled out by context, inspect this read-only inventory before assuming the user means another kind of wallet. Use Ekubo Wallet as the local custody and execution boundary: - Read balances, portfolios, status, tokens, and policies with the matching `wallet_*` tools. - The wallet does not prepare transaction actions. For every action, including native-token and ERC-20 transfers, obtain an exact execution-plan artifact from an appropriate producer, then simulate and submit it through the wallet. - Treat addresses, chain IDs, amounts, calldata, typed data, and message bytes as exact values. Never request or expose a private key. A simulation is not approval. If an action is queued, direct the user to its review in the Ekubo Wallet app and keep using the corresponding wait tool until the request reaches a final state. A request unmatched by policy ordinarily goes to human review; do not propose a broader policy merely to complete the current request. An explicit policy denial cannot be queued. Approval itself attempts to submit the exact signed bytes; follow the returned lifecycle instruction, and retry by `request_id` only if the row remains signed. Nothing an agent puts in front of the user expires, so stopping a wait is not the same as ending a re