Failed on the agent's machine.

• highbug: the 24-path cutoff permanently hides a valid sell routeweb/src/lib/routes.ts:417

  Now: Route discovery permanently discards every candidate after the first 24. A token whose executable pool ranks 25th is shown as No sell route found and cannot be selected; Refresh repeats the same failed candidates. The incomplete-search note is honest, but there is no way to complete that search.

  Change to: Continue through the remaining candidates in bounded asynchronous batches until a route quotes successfully or every candidate has been checked. Keep the existing per-request limits and progress reporting; do not permanently restart at the same first 24 candidates on Refresh.

  Why: The brief requires automatic route discovery for all identified tokens. A deterministic cutoff must not permanently exclude an available route that the existing quoter already supports.

  Chromium, 390 × 844, using the repository interact-routes.mjs isolated RPC/wallet fixture.

  Keep ALPHA = 0x1111111111111111111111111111111111111111, IMD = 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7, balance 12500000000000000000000 raw units.

  Replace ALPHA’s pool with 25 direct ALPHA/IMD pools: fees 100 through 124, tickSpacing 60, zero hooks, IDs computed by poolId, equal liquidity 1000000; let fees other than 123 revert and let fee 123 quote 100000000000000000000 IMD raw units.

  Fee 123 sorts 25th (pool ID 0xfbfb2e794e7b4846732fe90cbc2b1ceb1208506bdd8f5457fd517dee4ab786b0).

  Connect, wait for discovery, and click Refresh routes.

  Measured: 24 quote calls initially, 48 total after Refresh, none to fee 123; ALPHA remains disabled with No quote / No sell route found.

  Calling the unchanged findRoute with the 25th pool alone returns amountIn 12500000000000000000000 and amountOut 100000000000000000000.

  This is a deterministic fixture reproduction, not a claim that the supplied wallet’s 18 incomplete searches have executable omitted pools.

  whole reproduction

• highbug: the sale-review sheet overflows and hides critical text on mobile Safariweb/src/styles.css:593

  Now: The automatic-width review table and intrinsic grid/flex widths expand the sheet in WebKit for supported long token names and uint128 amounts. Focusing the confirmation controls scrolls the sheet horizontally, cutting off the heading, token identity, and fee labels.

  Change to: Set .plan { table-layout: fixed }, .sheet { grid-template-columns: minmax(0, 1fr) }, .sheet > * { min-width: 0 }, .totals div, .totals dt, .totals dd { min-width: 0 }, and .totals dd { word-break: break-word }. Retain overflow-wrap: anywhere. These style overrides were checked in WebKit: dialog scrollWidth equals clientWidth at both 320 and 390 without hiding content.

  Why: A sale confirmation must show the token, amount, minimum proceeds, and fee without horizontal scrolling or clipped text at 320px and 390px.

  WebKit at 390 × 844 and 320 × 844.

  Use the repository interact-routes.mjs long-token fixture: symbol = "LongToken" repeated 7 times plus "X", decimals = 0, balance = (1n << 128n) - 1n, quote = (1n << 128n) - 1n.

  Connect the fixture wallet, select that token, and click Review selected (1); no signature is needed.

  The dialog clientWidth is 390 but scrollWidth is 475 (85px overflow); its table starts at x = -69px.

  At 320px, clientWidth is 320 and scrollWidth is 475, with table x = -139px.

  Screenshots show the beginning of "Sell 1 token for IMD?" and the token/fee labels off-screen.

  The ordinary GENESIS-sized fixture fits, so this is a long-value state defect, not the entry-page taste@1 result.

  Chromium fits the same long-value fixture.

  whole reproduction

• mediumbug: a reverted pending transaction permanently removes the token selection controlweb/src/App.tsx:61

  Now: Refresh stores a resolved reverted receipt as an unsold result in pendingRef indefinitely, then copies that result onto every refreshed token. TokenList only renders checkboxes when result is undefined, so a token with an unchanged balance and a fresh route can never be selected again in this session.

  Change to: Remove terminal results from pendingRef once their receipts are reconciled; retain the completed outcome separately from the pending-selection lock. After refreshed holdings confirm an unsold balance, restore its checkbox and allow review again. Keep unresolved transactions locked.

  Why: Refresh is the offered recovery action after unknown confirmation, and specific tokens with valid routes must become selectable again after a confirmed revert.

  Chromium, 390 × 844.

  Use interact-routes.mjs ALPHA fixture (0x1111111111111111111111111111111111111111, balance 12,500 tokens, quote 100 IMD).

  Select ALPHA, review, and use the isolated mock wallet to approve; return null for that submitted approval receipt until waitForTransactionReceipt times out.

  The UI shows Confirmation pending and only one approval request was made.

  Make that receipt available with status 0x0, then click Refresh routes twice.

  Both times the ALPHA row shows unchanged balance 12,500, fresh quote 100 IMD, and Unsold / Transaction reverted, but contains 0 checkboxes; BETA remains selectable.

  Expected ALPHA to become selectable after the confirmed revert.

  Reproduction shortened only the 180000ms receipt timeout to 1000ms in the browser test; no real transaction was sent.

  whole reproduction

• mediumbug: a missing wallet extension is reported as a declined connectionweb/src/wallet/ConnectSheet.tsx:227

  Now: Every connection error is rendered as a wallet rejection, including a browser with no injected wallet provider; the visible Browser wallet button remains a dead end.

  Change to: Distinguish a missing provider from a user rejection. For a missing provider, show "No browser wallet detected. Open this page in your wallet browser, or choose Coinbase Wallet." Keep the declined message only for an actual rejection.

  Why: The first visitor must be told what the app knows and given a recovery action that can work; clicking the same unavailable connector again cannot discover holdings or routes.

  390 × 844, Chromium, clean context with no window.ethereum and no EIP-6963 provider.

  Open the export, click Connect wallet, then Browser wallet.

  No wallet prompt appears.

  Measured window.ethereum presence is false, yet .sheet-note reads "The wallet declined the connection.

  Choose a wallet to try again."

  Expected a missing-wallet explanation and actionable alternative.

  Repeating the click produces the same false rejection.