[brendanjryan]

Stacked on #290 (base brendan/machine-fetch-integration). Retarget to main once #290 merges.

machine-fetch 0.3.2 ships the cross-chain fixes this integration first made in the CLI (tempoxyz/machine-fetch#88–#92). This PR removes the CLI's copies. Each one went only after a test showed machine-fetch covers the same case. One commit per workaround, so each rebases on its own if #290 changes.

Removed

Workaround	Now covered by	Shown by
crossChainDeadlineSeconds = 300 and the deadlineSeconds override in src/request/evm-charge.ts	tempoxyz/machine-fetch#88: a cross-chain funder defaults to 300 s when policy sets no deadline	test/cross-chain-deadline.test.ts runs a payment through machine-fetch with no policy deadline and checks the bridge's quote gets 300 s. The --dry-run preview now uses the funder's own defaultDeadlineSeconds.
confirmedDelivery, DeliveryFloor, destinationBalanceAt, the target/floor plumbing through fundingRoutes/crossChainFunders, and the DeliveredStatus alias	tempoxyz/machine-fetch#89 (polls the destination balance until the deadline, retrying failed reads) and tempoxyz/machine-fetch#90 (recover confirms a spent delivery from destinationTxs)	test/cross-chain-delivery.test.ts runs each case the wrapper handled through machine-fetch with the CLI's readers. Base read lag: in the lagging-RPC e2e test (test/e2e/lagging-rpc.ts), logging each balance read showed 0, 0, 0, 100000 after the bridge reported completion. machine-fetch's polling alone covers it, so the block-floor read is gone.
Recording the source block (blockNumber, fromBlock) in new Stargate quotes, and the OFTSent search for new operations	tempoxyz/machine-fetch#91: saveReference	The route signs its send, saves the signed transaction's hash, then broadcasts. The kill mid-bridge e2e test checks that the saved hash is the send's own.

Kept, and why

• destinationDelivery (src/shared/chains.ts): it is now the funder's delivered reader and returns only the amount. machine-fetch needs a reader from the app because the CLI's Relay and Stargate routes are its own, so neither brings one.
• The OFTSent search (findSent): it runs only for operations saved before this change, which have fromBlock and no validBefore in their quote data. The never-recorded-hash e2e test now rewrites a saved operation to that shape.
• dexSwapSpend, canSpend, beforeSwap (src/wallet/access-key.ts, src/request/funding.ts, src/payment/tempo-funding.ts, src/commands/swap.ts): tempoxyz/machine-fetch#92's spendLimit applies only to machine-fetch's built-in auto-swap, which the CLI turns off (autoSwap: false). The CLI's own DEX funder and wallet swap still need the 2× budget and the tempo wallet keys update hint. Nothing here duplicates fix(request): strip credentials on cross-origin redirects #92, so nothing is removed.
• Asking the route first in funding recover and in reconciliation before a new funding: machine-fetch's recover throws on refunded and pending operations instead of reporting them. So the CLI still reads route.status, and calls the funder's recover (new operationStatus) only to confirm a completion on chain. A completion not yet visible stays pending, as before.

Behavior to review

• Stargate sends now expire. A send is signed with Tempo's validBefore set to the quote's expiry. A saved send with no receipt counts as refunded once Tempo's latest block is at least 60 s past validBefore; the margin covers an RPC whose receipts lag its head. machine-fetch's docs ask routes to handle a reference that was saved but never broadcast. The dropped reader (getBlock plus receipt-not-found) is covered through the route's unit tests. No e2e test makes the local chain drop a signed send.
• funding recover waits longer. Confirming a completion now polls for up to 15 s (reconciliation: 10 s) before saying pending. Before, it read once.

Verification

• Unit tests (pnpm test): 3,119 passed.
• E2E (pnpm test:e2e): 41 of 41 passed.
• pnpm check (format, lint, types, test types, tests), pnpm docs:check and pnpm changelog:validate all pass.
• Each commit passes types, unit tests and e2e on its own.
• CI will fail at install, like feat(request)!: pay MPP and x402 from any Tempo stablecoin, on Tempo or Base, through machine-fetch #290's: Aegis blocks the just-published machine-fetch 0.3.2 as recentlyPublished.
• Everything ran on local chains; no real funds moved.

[brendanjryan]

Folded into #290 (fast-forwarded onto its branch) so the wallet ships as one PR. The extra changelog entry was dropped, since the replaced copies never reached main.