• highfidelity: the first phone screen contains no vault product dataweb/src/Vault.tsx:168

  Now: On phones the character is ordered before the title, after the banner, 267 px header, shelf and wallet-help panel. At 390×844 the first viewport ends partway through the illustration; both the product explanation and vault figures are below it.

  Change to: In a separately approved replacement patch, move the existing “Inside the basket” summary ahead of the character/title panel on phones, keeping the header wallet action and restriction text. Let that summary occupy the space currently leading into the illustration; keep the illustration below the product data.

  Why: The review criterion explicitly requires the product on the first 390 px screen. This is a preserved composition defect, not a failure to apply the supplied patch; fixing it requires revising the immutable patch rather than silently restyling this submission.

  Chromium, fresh no-wallet context at 390×844.

  Open the production export at / (Vault), wait for chain reads and document.fonts.ready, keep scrollY=0. getBoundingClientRect() gives h1 “A basket of stocks.” top=982.375 px, first section.panel “Inside the basket” top=1134.359375 px, and .page-title.has-character top=699.375 px / height=418.984375 px.

  Thus neither heading nor any NAV/share figure intersects the first 844 px.

  Connect wallet and navigation do intersect it.

  The first-viewport screenshot ends inside the character panel.

  Expected: a visitor can identify and inspect the actual vault tool before scrolling.

  whole reproduction

• mediumbug: a delayed Connect reply reverses a later Disconnectweb/src/wallet.tsx:213

  Now: connect() accepts its asynchronous account reply unconditionally, clears the saved disconnect flag and restores the account even when Disconnect was pressed after that request began.

  Change to: In a corrected upstream patch, give explicit connect/disconnect actions an intent generation; capture it before eth_requestAccounts and ignore its result if a later explicit disconnect changed it. Preserve account-event handling and the existing transaction code.

  Why: The brief requires Disconnect to forget this page’s connection and keep it disconnected until the visitor presses and answers Connect wallet again; the current guard covers the initial eth_accounts reply only.

  Chromium, 390×844, production dist at /#deposit. Inject an EIP-1193 provider with eth_accounts => [], eth_chainId => "0x1237", and a deferred eth_requestAccounts promise.

  1. Press the header Connect wallet.
  2. Before resolving its promise, emit accountsChanged(["0x1111111111111111111111111111111111111111"]).
  3. Press the now-visible Disconnect. Observe basket-disconnected-4663="1" and no displayed address.
  4. Resolve that earlier eth_requestAccounts with the same account without another Connect press. Actual: the flag becomes null and the address plus Disconnect reappear; a subsequent reload therefore reconnects. Expected: the later Disconnect remains authoritative. Recorded wallet methods before/after step 4: [eth_accounts,eth_chainId,eth_requestAccounts] / [eth_accounts,eth_chainId,eth_requestAccounts,eth_chainId]. No public transaction was requested. Repeated in WebKit 27.2 with the same result. With the mock preserving its allowed account across reload, a reload after step 4 also restores the address and Disconnect button, with only eth_accounts and eth_chainId requests.

  whole reproduction

• mediumfidelity: shared links have no Open Graph title or imageweb/index.html:11

  Now: The page shell defines a favicon and HTML title but no og:title or og:image. The production HTML retains the same omission.

  Change to: In a separately approved patch that permits the page-shell change, add og:title="Basket Protocol" and an og:image with an absolute public URL to a valid existing project image, and rebuild the export.

  Why: The design checklist requires a share title and image. This is an inherited metadata omission; the current exact-patch preservation gate freezes web/index.html, so it must not be bypassed to implement this recommendation.

  At 390 px or any width, open the production export and evaluate document.querySelectorAll("meta[property="og:title"], meta[property="og:image"]").length: actual 0, expected 2.

  Inspect web/index.html and dist/index.html: both contain title, description and favicon but neither Open Graph field.

  The unchanged taste@1 probe reports share=false, “missing or default: og:title, og:image”.

  No external unfurl service was assumed or tested.

• mediumbug: the 24/7 redemption label overflows at 661 px with the fallback fontweb/src/styles.css:530

  Now: The first redemption sentence is forced onto one line. In the two-column Redeem layout at 661 px, the blue label is 240.5 px wide including 32 px of border/padding, but its bold sentence is about 238.97 px wide. The final characters extend beyond the blue background and become white on the white panel.

  Change to: In a corrected supplied patch, change .hours-tag strong from white-space: nowrap to white-space: normal, allowing breaks between words inside the existing label. Keep the exact sentence, font size and layout structure.

  Why: The review forbids critical interface text being cut off, and check-art explicitly requires each tag word to remain inside its label. The site declares a system sans-serif fallback, so it must accommodate that fallback’s metrics.

  Chromium 156 and WebKit 27.2 on Linux with Arial/Helvetica unavailable and sans-serif resolving to DejaVu Sans, viewport 661×900.

  Load dist/#redeem and scroll to the blue 24/7 label (the vault read may succeed or fail; the label is unconditional). .hours-tag bounds: left=49, right=289.5, width=240.5 px.

  Its strong text bounds: left=65, right=303.96875 in Chromium / 303.967285 in WebKit, spilling about 14.47 px beyond the blue label.

  The screenshot shows the line ending visibly at “24/”; the remaining white characters merge into the panel.

  Expected: the complete 24/7 statement remains legible inside the blue background.

  Run unchanged node scripts/check-art.mjs with this browser/font environment: it fails at line 509, “Chromium redeem 661: tag words split or outside”, actual ["outside: 24/7."].

  Chromium CDP CSS.getPlatformFontsForNode confirms the actual font is DejaVuSans-Bold (not a missing-font loading state).

  WebKit 26.6 also reproduces the overflow; Chromium 153 with Liberation Sans instead measures 199.234375 px and fits, confirming the fallback-font dependency.

  The project check was also rerun with Chromium 153/WebKit 26.6: it passed Chromium, then failed the same line 509 assertion at WebKit redeem 661.

  whole reproduction

Failed in the task.