Now: any source snapshot older than 5 minutes turns the pulse to "Source delayed", stamps sections "Delayed source snapshot" and adds "is delayed" notices to the leaderboard and catalog. The API's snapshots are routinely older than that, so the warning is the normal state and says the source is late when the app does not know that.

Change to: export const STALE_MS = 90 * 60_000; keep the source time in every stamp, and change "older than five minutes" in the About text (main.ts:149) and "older than five minutes" in README.md:73 to "older than 90 minutes".

Why: the brief's banner is for an API that is actually "stale". A warning that is usually on stops being read, including when the data really is old.

Now: the same text, blaming the 2026-11-05 CORS check and saying the other sections "remain accessible", shows for any failure, including 503, 429 and a timeout while those sections are also down. It also repeats the notice above it. On each refresh load() sets pending, so the block swaps to the "Reading ..." section and back, moving the checklist below it, and the Find member button turns to a disabled "Finding…", which drops keyboard focus if it was there.

Change to: delete the hard-coded sentences and keep the issue(r) notice, which holds the real error, plus the official-site link. Show the waiting block only when r.state.pending && !r.state.error. In lookup(), set disabled and "Finding…" only when resultToReveal === selected.

Why: the bar is that each state says only what the app knows and none moves unrelated content; the brief says "explaining exactly what is unavailable".

Now: clicking Retry or Refresh within 30 seconds of the last attempt returns before any request and changes nothing on screen. The explanation goes only to the sr-only announcer (main.ts:235-236), so a sighted visitor sees a dead button.

Change to: in issue(), when r.state.lastAttempt + CACHE_MS > Date.now(), label the button "Retry after HH:MM:SS UTC" using clock(lastAttempt + CACHE_MS). Give the Leaderboard Refresh button the same label from its soonest resource. Keep the 30-second limit.

Why: the brief requires polite 30-second caching, which stays. The bar requires the retry state to say what the app knows.

Now: render() rebuilds the pager and replaceMain() refocuses the same button. On the last page Next is disabled, as is Previous on the first page, so focus() does nothing and focus drops to body. The next Tab restarts from the skip link and header.

Change to: after render() in this handler, if document.activeElement is not a pager button, focus the other one: main.querySelector([data-action="${action==='next'?'prev':'next'}"])?.focus({preventScroll:true}).

Why: the brief says "keyboard-navigable".

Now: previousRanks rolls forward on every successful fetch, but the API's ranks only change when snapshot.computedAt changes. A move appears for one poll, then the next identical response compares equal and the row shows "↔ 0".

Change to: roll previousRanks only when leaderboard.state.data.snapshot?.computedAt differs from the last seen value, and set previousRankTime from that snapshot. Change the note at main.ts:145 to say arrows compare the previous snapshot seen in this tab.

Why: the brief asks for "rank movement arrows". GET /leaderboard has no movement field (checked live), so the in-tab comparison is all the site has and should not discard its result after one poll.

Now: the only dot grid and hamster illustration in the interface are inside .hamster-art, which is on the Board only and hidden at 660 and below. A phone visitor gets a 36px favicon on an otherwise plain dark layout, and Leaderboard and About have no dot treatment at any width. The block also carries orbit lines and two art points that compete with the dots.

Change to: move the existing dot background to the shared strip: .pulse-shell{background-color:var(--color-surface);background-image:radial-gradient(circle,#354035 1px,transparent 1px);background-size:12px 12px}. Delete .orbit and .art-point with their four spans; the hamster stays centred in its block.

Why: the brief asks for an "Original dark, LED-dot, hamster-inspired" look that "works on mobile", and says this is not a "generic dashboard template".

Now: at 660 and below .board-layout stacks .board-content before .community-side, so the member list follows all 35 badge cards. A visitor with no code is told to look "below" and meets none.

Change to: Use a public invite code or choose a member on the leaderboard.. The existing p a underline rule styles the link.

Why: the brief offers lookup by "a leaderboard row", and this is the only route for a visitor with no code.

Now: the input outline is --color-border #354035, on a #171c18 fill over a #101311 page, so the field edge barely shows. The same token outlines .secondary buttons.

Change to: border:1px solid var(--color-subtle) on input, and border-color:var(--color-subtle) on .secondary. Structural dividers keep --color-border.

Why: the brief requires accessibility, WCAG 1.4.11 asks 3:1 for control boundaries, and a control must still look like a control.