#50 Auto-resolve Liquid asset ID in sideshift send

[andycreed0x]

Purpose

Auto-resolve the Liquid asset ID from the deposit coin ticker in sideshift_send, eliminating the UX friction where non-L-BTC Liquid assets (e.g. USDt) required manually passing a 64-char hex --liquid-asset-id.

Closes #50 sideshift send: requires --liquid-asset-id manually for non-L-BTC assets

Main Changes

• ✨ Added resolve_liquid_asset_id() in assets.py — single source of truth that maps a (coin, network) pair to a Liquid asset hex ID, short-circuits to None for non-Liquid networks and L-BTC, raises ValueError with actionable known-ticker list for unknown tickers, and passes explicit overrides through unchanged
• ♻️ Refactored tools.sideshift_send to call resolve_liquid_asset_id before contacting the SideShift manager — unknown tickers fail fast before any custodial order is created
• ♻️ Removed duplicate inline auto-resolve logic from cli/sideshift.py (now delegates to the shared helper)
• 📝 Updated MCP tool schema description and sideshift_send prompt — AI assistants no longer need to look up liquid_asset_id manually via lw_list_assets
• ✅ Added TestResolveLiquidAssetId (10 cases) in test_assets.py and TestToolsSideShiftSendAutoResolve (5 cases) in test_sideshift.py

Checklist

• No hardcoded values (they should go in constants.py, .env, or our database)
• Added/updated tests (if necessary)
• Added/updated relevant documentation (if necessary)

[marinate305]

Checks are failing after PR #86 merged — looks like the branch needs to be rebased onto develop to pick up the is_mnemonic_encrypted → requires_user_password rename. Happy to re-review once the tests are green.

[marinate305]

Tests are green and conflicts resolved. Approving.