Now: renderToken keeps its #app reference across awaited chain reads and later replaces the page even when the visitor has navigated to Launch, erasing entered form values.

Change to: capture a route/render generation before the first await and verify it before every token-page DOM write, including the not-found branch; discard results when the active route or generation differs. Reuse the cancellation pattern in renderRewards.

Why: a completed read must update only the view that requested it; changing routes must not discard unrelated work.

Now: loadPads catches failed getCode requests without retaining the error, leaving every pad marked not live. renderSetup then states “Not deployed yet” and tells visitors to edit CONFIG, with no recovery control.

Change to: distinguish failed deployment reads from a successful 0x response. For failed reads, show “Could not reach the chain. Reload to try again.” with a Reload button, and reserve “Not deployed yet” for successful reads that actually return no code. Keep the existing addresses and providers.

Why: the error state must state only what the app knows and offer a visitor recovery path; a network failure does not establish that contracts are missing.

Now: the launch form always says “Holders earn their 3% in IMD”, including when Deflationary selects 0% holders / 3% burn. The Rewards introduction and empty state similarly promise 3% for every token.

Change to: replace the launch sentence with “Every token is paired with IMD. Buyers can pay with ETH or IMD. Choose below how the 3% is split.” Use “Holder rewards depend on each token’s fee split and are paid in IMD or ETH.” for the Rewards introduction and empty-state claim; keep the existing computed split note.

Why: fee copy must match the selectable, permanent fee allocation before the visitor commits money.

Now: .pill.chain uses the light-theme accent #0a8f3c on white for 10px Ethereum labels, producing 4.19:1 contrast.

Change to: use the existing --text color for .pill.chain, as .pill.eth already does; retain the border and Ethereum text so the network remains explicit.

Why: normal-size text needs at least 4.5:1 contrast; the chain label is essential information for choosing where a token trades.

Now: showNft appends an unlabelled div overlay but leaves focus on the obscured collection button. Tab continues through the background collection, and Escape does not close the overlay.

Change to: give the existing overlay dialog semantics and an accessible name; save the triggering tile, move focus into the dialog when opened, keep Tab/Shift+Tab within it, make the background inert, close on Escape, and restore focus to the tile on every close path. Reuse the existing Close button.

Why: keyboard and assistive-technology visitors must be able to identify, operate and dismiss the visible dialog without activating content behind it.

Now: the idle planet and clouds rotate continually before wallet connection even when prefers-reduced-motion is reduce. The CSS-only motion probe reports zero animations and misses this requestAnimationFrame loop.

Change to: read prefers-reduced-motion and skip idle world/cloud rotation when it is reduce; render the static gate scene and retain the existing movement controls for intentional gameplay. Respond if the preference changes.

Why: the access screen does not need endless background motion, and the review bar requires that this motion stop for reduced-motion visitors.

Now: the live terminal uses 11px text with 1.8 line height at phone widths, making adjacent linked trade rows 19.8px tall with no vertical gap; the fixed log also cuts through its oldest visible row.

Change to: give .scr-log .ln a minimum 24px height and flex-shrink:0, then render only the newest whole rows that fit the existing log height. Keep the terminal and launch control in place; let the remaining rows occupy the same log area without a half-line at the top.

Why: these rows navigate to different tokens and fail the 24px target/spacing bar; a finger should not need to distinguish links less than 20px apart.