SQUEEK'S FIRST ROAD TRIP: SINGLE FULL REVISION

Work in the order below. If anything has to be cut, cut from the bottom. Priority 1 items are mandatory.

HARD CONSTRAINTS

• Do not change the smart contract, its address or ABI, or any existing votes.
• Front-end changes only.
• Keep the current map library and OpenFreeMap tiles and restyle only. All other art is inline SVG/CSS with no external images.
• Google Fonts only, with a safe fallback.
• Everything that works today keeps working (see item 4).

PRIORITY 1 (MUST SHIP)

1. BLANK PAGE AFTER WALLET CONNECT (CRITICAL) After a visitor connects a wallet and returns, the page flashes for a second and then shows only the dotted background. Console error: "TypeError: v.getProvider is not a function", thrown during render. Deleting only "wagmi.store" from local storage fixes it. Likely cause: code calls getProvider() on the connector rehydrated from persisted wagmi state, which is a stub without methods, before reconnection has completed. Confirm the root cause and state it in the delivery notes. Required:

• No component calls a connector method unless it exists and wagmi's status is not reconnecting. Prefer wagmi's own hooks over manual getProvider calls.
• All chain reads (votes, tallies, route, leaderboard) use a public RPC client that is independent of any wallet, so the whole page renders with no wallet and with a broken saved connection.
• Wrap the whole app in an error boundary with a "Reset and reload" button that clears only the app's own keys (wagmi., hrt-, cbwsdk.*). A crash must never leave a blank page.
• Use a versioned wagmi storage key so saved connections from older builds are ignored.

2. RESILIENCE

• Use fallback RPC endpoints with retry.
• When reads fail, show a clear "Can't reach the network, retrying" state. Never show 0 votes or 0 km as a placeholder while loading or after an error.
• Design proper states for: a day with no votes, Squeek resting for several days, and the trip being complete.

3. SPECTATOR-FIRST WALLET FLOW

• Everything is visible without a wallet. Only voting asks for one.
• One-tap prompt to switch to Sepolia.
• If the wallet has no test ETH, show a clear message with the faucet link.
• Explicit transaction states: waiting for wallet, pending, confirmed, failed with the reason.
• Wallet connection must work on phones (WalletConnect, deep links, or an in-wallet browser). Test at 360px width.

4. PRESERVE EXISTING FUNCTIONALITY Voting, the countdown, the Destinations page, the Trip log page, the "?" help, transaction and explorer links, the faucet link, "Back to the ballot", the Up Next list, Navigators and the postcards section must all keep working. Apply the new look to every page.

5. VISUAL IDENTITY

• Replace the plain dark-template look completely. Use pixel-art styling built from the existing Squeek logo's colors, chunky borders and a pixel display font.
• Reuse the existing logo asset as the Squeek sprite. Show the sprite travelling the route with an animated wheel.
• The first screen must show Squeek's current state (running or resting), where Squeek is heading, and one clear action.
• Respect prefers-reduced-motion.
• Responsive from 360px, keyboard accessible, readable contrast.

6. PASSPORT AND LANDMARK POSTCARDS

• Build all 64 stops from one shared SVG kit: a regional sky gradient, a ground strip, the Squeek sprite and a postcard frame.
• Each landmark is a simple, recognisable geometric silhouette of the single most iconic, unambiguous landmark for that stop.
• Each postcard shows: "Greetings from [City]", the arrival date, the distance, the winning vote count, and a link to the finalizing transaction.
• A passport grid shows visited stops as postcards and unvisited stops as locked silhouettes.

7. DATA AND LABELS

• Use a plane icon for air crossings and a unique icon per stop.
• Plural-aware counts (e.g. "1 vote").
• Label Up Next dates "Voted [date]".
• Show consecutive wins by the same city as "Day 2 in [City]" instead of duplicate entries.
• The countdown says what it counts to, and the reset time is shown in the visitor's local time and in UTC.
• Empty and loading states everywhere.

PRIORITY 2 (SHOULD SHIP)

8. BALLOT Contender cards sorted by votes with share bars and a countdown, a search box over all 64 stops, and map-pin selection. Reflect whatever the contract allows about changing a vote.

9. ARRIVAL MOMENT AND RECAP A celebration and postcard reveal when Squeek arrives at a stop, plus a "while you were away" recap for returning visitors using a versioned last-seen block.

10. NAVIGATORS Generated names and avatars derived from the wallet address, rank titles, streaks derived from on-chain events, and the current visitor's row highlighted.

11. CLOSING A DAY When a day has ended, show a clear banner explaining that it is ready to close and why it matters. Show who closed it if the event data includes it.

12. SHARING Download a postcard as a PNG rendered client-side, with pre-filled share text.

13. HUMAN-SCALE DISTANCE A line such as "1,629 km is about Miami to Chicago", computed from stop coordinates.

14. TRUST AND PREVIEWS Footer with the contract address and explorer link plus "Testnet: no real money". Set the page title, description, favicon and social-preview meta tags (include a preview image only if it can be hosted with the site).

PRIORITY 3 (ONLY IF ALL ABOVE ARE UNTOUCHED)

Sound toggle (off by default), short fun facts per stop (only if confident they are accurate, otherwise omit), time-of-day sky on the map.

BEFORE DELIVERY, TEST ALL OF THESE

Connect wallet then reload; stale saved wagmi.store from an old build; two wallet extensions installed; wallet locked; wrong network; no wallet; private window; RPC failure; 360px mobile width.

DELIVERY NOTES REQUIRED

• The root cause of the blank-page bug.
• What shipped and what did not, including how many of the 64 landmarks are complete and which landmark was chosen for each stop.
• Confirmation that the contract, address and ABI are unchanged.