feat(transaction-pay-controller): support Predict withdraw in the server strategy

[matthewwalsh0]

Explanation

The server strategy declined Predict withdraws, so they could only be quoted and submitted through the Relay strategy.

• The server strategy now supports each Predict withdraw variant:
  • Safe: quotes honour refundTo, and gas estimation and gas fee token lookups use the Safe that holds the source token.
  • Polymarket deposit wallet: quotes are requested from the deposit wallet in USDC.e with useDepositAddress. On submit, the Polymarket relayer unwraps pUSD directly to the provider deposit address, then any leftover or refunded USDC.e is swept back to the deposit wallet. No source network fee is charged, as the relayer pays origin gas.
  • Payment overrides (e.g. withdrawing to a Money Account): non-atomic quotes settle on the override recipient, and the override calls run as a second leg.
• Post-quote quotes include the original transaction in gas estimation and reserve the gas fee token cost from the source amount.
• Server quote requests accept useDepositAddress. The deposit step is identified as a plain ERC-20 transfer with no extra calldata or native value, and deposit-address quotes without one are ignored.

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

High Risk
Changes core server quote/submit orchestration for withdraws, refunds, multi-leg settlement, and Polymarket relayer paths where incorrect gas, recipient, or sweep timing could mis-route funds or double-execute calls.

Overview
Server strategy now handles Predict withdraw instead of leaving those flows to Relay. Quoting and submission paths were extended for Safe, Polymarket deposit wallet, and non-atomic payment overrides.

Safe / legacy Predict withdraw: post-quote requests pass refundTo to the server; source gas uses estimateSourceGas (including the original tx), with deposit routes estimated from the Safe and fee-token lookups on the Safe account.

Polymarket deposit wallet: quotes use useDepositAddress, USDC.e from the deposit wallet as sender/refund, and no gasless flag; only quotes with a plain ERC-20 transfer deposit step are kept (deposit-step.ts). Submit replaces quote steps with submitPolymarketWithdraw to the deposit address, zeros user origin fees, sweeps leftover/refunded USDC.e after polling, and PolymarketDepositWallet is removed from server unsupported reasons.

Non-atomic overrides (e.g. Money Account): settlement recipient comes from the override; requiresSecondLeg is true; override calls are not embedded in the quote batch but built in the second leg via getCalls. Post-quote flows can re-quote the same provider to reserve gas paid in the source token.

Submit also assigns leading gas limits to prepended post-quote txs, skips prepending override calls when atomic === false, and returns terminal intent status from polling so deposit-wallet sweep can run before failures are surfaced.

^{Reviewed by Cursor Bugbot for commit e27abb2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e27abb2. Configure here.}