fix(sdk-core): keep intent tokenName for token-wallet TSS signing

[ralph-bitgo]

Description

SOL:USDT / SOL:USDC withdrawals and SOL consolidations from the affected SOL TSS
hot wallet failed UI signing with Tx outputs does not match with expected txParams recipients, leaving every txRequest stuck in pendingDelivery,
unsigned, with no txid (customer blocked; Case376984).

Root cause (token withdrawals). On a token wallet, baseCoin.getChain()
returns the token name itself (e.g. sol:usdt). populateIntent therefore
persists amount.symbol = 'sol:usdt' (sendMany on a token wallet carries no
recipient tokenName), but at signing time resolveEffectiveTxParams treated a
symbol equal to chainName as a native transfer and dropped the tokenName
fallback. Sol.verifyTransaction then had no mint to derive the recipient's
associated token account from, and rejected the transaction.

Fix. resolveEffectiveTxParams
(modules/sdk-core/src/bitgo/utils/tss/recipientUtils.ts) now keeps
amount.symbol as tokenName when chainName is itself a statics-registered
token — i.e. the wallet is a token wallet. Native wallets keep the strict
symbol !== chainName rule; names registered nowhere (neither statics nor the
runtime/AMS registry that GlobalCoinFactory feeds into it) are left unchanged
rather than guessed, so the fail-closed posture is preserved.

Consolidations were already fixed on master by WCN-2952 (sweep-to-base-address
verification); this PR closes the remaining token-withdrawal path.

Pending requests. The six listed txRequests carry valid intents and unsigned
transactions, and verification runs at signing time in the SDK — so once the UI
runs a SDK build containing this fix (plus WCN-2952 for the consolidations), they
can be signed as-is and do not need to be rejected and recreated.

Issue Number

Ticket: WCI-1723

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• New regression tests in
  modules/sdk-core/test/unit/bitgo/utils/tss/recipientUtils.ts: token wallet
  (sol:usdt / tsol:usdc with chainName = symbol) keeps tokenName;
  native transfer (symbol === chainName === 'tsol') still drops it; chain
  name not in statics still drops it; all RED against the pre-fix code, GREEN
  after.
• New end-to-end tests in modules/sdk-coin-sol/test/unit/sol.ts: a mainnet
  sol:usdt withdrawal resolved through resolveTssVerifyTransactionOptions
  with a production-shaped intent (symbol = token chain, no tokenData) passes
  verifyTransaction; a tampered intent recipient is still rejected with the
  exact production error.
• Suites: sdk-coin-sol 790 passing; sdk-core 890 passing; bitgo tssUtils
  subsets match the master baseline (11 pre-existing failures: missing native
  sodium functions and pre-existing assertions, identical on master).
• sdk-coin-sol and sdk-core clean builds (tsc) green; eslint clean;
  commitlint passes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My code compiles correctly for both Node and Browser environments
• I have commented my code, particularly in hard-to-understand areas
• My commits follow Conventional Commits and I have properly described any BREAKING CHANGES
• The ticket or github issue was included in the commit message as a reference
• I have made corresponding changes to the documentation and on any new/updated functions and/or methods - jsdoc
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Ticket: WCI-1723

[linear-code]

WCI-1723

[github-actions]

⚠️ Unit tests are failing on Node 26.x (Current release line, non-blocking). This is not an LTS version yet, so it does not block merge, but it signals an incompatibility to fix before Node 26.x becomes LTS.

View run