Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

test(chains): lock in the TVL board's row-selection and landmark repairs

nirholas4a2b182dd2a1
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5ed79381b..1fc6dc64b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,8 +6,12 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-08-17
+- **A shared ASL letter link now opens on that letter, not on A**: The manual alphabet at /asl-alphabet was audited end to end in a real browser, and six repairs came out of it. Sharing a letter was the worst of them: a /asl-alphabet?letter=W link built the whole page around the letter A and only corrected itself once the 3D avatar had finished downloading, so anyone on a slow connection read A's description, saw A's key lit and A's look-alike note for the entire wait, on a link that promised W. The page now reads the link before it builds anything, so the right letter is on the card from the first paint and the avatar simply catches up. The Spell anything box had the opposite problem: it reported an empty or unspellable word only in the small caption pinned to the avatar, which on a phone sits a full screen above the box you just typed in, so pressing Spell it with a word full of punctuation looked like a dead button. It now answers in its own line, right under the input, and while the hand is spelling it lays the word out letter by letter and lights each one as the hand reaches it, so a long word can be followed without scrolling back up to the A-to-Z grid. That caption itself was white text on a scrim too faint to read over a pale avatar or in light mode, and is now a proper legible chip. Opening the avatar picker no longer lets a keystroke through to sign a letter behind the dialog. Switching avatars used to leave 'Loading avatar…' on screen forever once the new one had arrived, which also meant screen readers were never told the load had finished. And the Spell panel is no longer stretched to the height of the drill beside it, which left a large empty box on desktop. (`/asl-alphabet`) `[fix, improvement]`
- **Avatar Studio now shows your whole avatar, and its Save button fits on a phone**: The studio camera was framing the base body from the shoulders to the knees: the face you were sculpting and the shoes you were picking were both outside the picture, and the only way to see them was to orbit the camera yourself every time the page loaded. The framing is now solved from the lens rather than guessed at, so a full-body shot really does hold the avatar head to toe, arms included, on any window shape, and the half-body and headshot views stay as tight as their names promise. On a 320px phone the top bar had been running past the edge of the screen and taking the Save avatar button with it, so a look built on a phone could not be saved at all; the bar now fits, with the Back and title labels standing down to make room. The tab strip on that same narrow layout had been hiding its labels without putting anything in their place, leaving six blank buttons, and now shows an icon per tab. The Parametric body badge that read 120+ sliders was white text on a white pill and invisible everywhere. A failed save now says the connection could not be reached and that your look is still there, instead of repeating the browser phrase Failed to fetch, and every accessory search box, every tab and the Back link now carry names a screen reader can read. Opening avatar-studio in local development also serves the same page production does, which it previously did not. (`/avatar-studio`) `[fix, improvement]`
+- **Blockchain TVL by Chain is readable again, and its numbers can be copied**: The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it. (`/chains`) `[fix, improvement]`
+- **Crypto Categories reads correctly in all 84 languages**: The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one. (`/categories`) `[fix]`
- **The viewer's backdrop picker stops vanishing while you read it, and sharing no longer posts "Meet Agent"**: Five fixes to the 3D model viewer at /app. Opening the Backdrop picker and taking a few seconds to read the six choices used to make the picker fade out from under the cursor: the viewer hides its controls after five seconds of stillness, and the picker was not on the list of surfaces that keep them awake, so an open picker went invisible and unclickable while still counting as open. It now stays put until you choose a backdrop or close it, and the controls resume fading once it is shut. Typing in the animation search while the clips were still loading stacked a second, contradictory message under the first, so the panel read "Loading clips" and "No clips matching" at the same time, and clearing the box left behind the nonsense line "No clips matching" with nothing in the quotes; the search now stays quiet until there are clips to search. Sharing the viewer to X, Farcaster or Telegram published "Meet Agent", an internal placeholder name, for anyone who had not loaded an agent of their own, and now uses the generic line instead. The page also shipped a sign-in panel and a welcome card that its own stylesheet blanked unconditionally, four links nobody could ever reach, and the preview card shown when the page is shared described the platform instead of the viewer. The avatar gallery behind the Avatar button is now announced to screen readers as a named dialog. (`/app`) `[fix, improvement]`
+- **Wallet Intelligence stops reporting win rates like 570% and 9790%**: The pump.fun track record at /claim-wallet was audited end to end in a real browser, and the headline numbers were wrong. Lifetime win rate, early-entry win rate and dump rate are stored as percentages, but the page multiplied them by a hundred a second time, so a wallet that wins 5.7% of its trades was shown as '570% lifetime' and a 97.9% dump rate read '9790%'. The meters beside them were pinned full for the same reason, and the colour that flags a heavy dumper was triggered by anything above 0.3%. All three now read the real figure. Four other repairs came out of the same pass. A wallet the reputation brain has graded but whose per-coin rows are still indexing used to show an empty ledger captioned 'No coins match these filters', blaming filters that were not the cause; it now explains that the ledger is still filling in. When filters genuinely do hide everything, the table says how many coins were hidden and offers one click to clear them. The ledger header no longer claims 60 coins while showing 52, since dust is hidden by default. A dropped connection used to blank the report and print the browser's raw 'Failed to fetch' beside the search box with no way forward, and now shows a proper panel naming the cause with a Try again button. The Analyze button's 'Analyzing…' label was being overwritten by the translation pass and never appeared. Keyboard and screen-reader users can now sort the ledger and open any coin: the column sorters are real buttons that announce their sort direction, every row carries a real link to that coin's dashboard, the time-window and filter controls report whether they are on, and every control on the page shows a visible focus ring. (`/claim-wallet`) `[fix, improvement]`
## 2026-08-16
diff --git a/data/changelog.json b/data/changelog.json
index 419971d46..8c0591e93 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,45 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-17",
+ "title": "Blockchain TVL by Chain is readable again, and its numbers can be copied",
+ "summary": "The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/chains"
+ },
+ {
+ "date": "2026-08-17",
+ "title": "A shared ASL letter link now opens on that letter, not on A",
+ "summary": "The manual alphabet at /asl-alphabet was audited end to end in a real browser, and six repairs came out of it. Sharing a letter was the worst of them: a /asl-alphabet?letter=W link built the whole page around the letter A and only corrected itself once the 3D avatar had finished downloading, so anyone on a slow connection read A's description, saw A's key lit and A's look-alike note for the entire wait, on a link that promised W. The page now reads the link before it builds anything, so the right letter is on the card from the first paint and the avatar simply catches up. The Spell anything box had the opposite problem: it reported an empty or unspellable word only in the small caption pinned to the avatar, which on a phone sits a full screen above the box you just typed in, so pressing Spell it with a word full of punctuation looked like a dead button. It now answers in its own line, right under the input, and while the hand is spelling it lays the word out letter by letter and lights each one as the hand reaches it, so a long word can be followed without scrolling back up to the A-to-Z grid. That caption itself was white text on a scrim too faint to read over a pale avatar or in light mode, and is now a proper legible chip. Opening the avatar picker no longer lets a keystroke through to sign a letter behind the dialog. Switching avatars used to leave 'Loading avatar…' on screen forever once the new one had arrived, which also meant screen readers were never told the load had finished. And the Spell panel is no longer stretched to the height of the drill beside it, which left a large empty box on desktop.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/asl-alphabet"
+ },
+ {
+ "date": "2026-08-17",
+ "title": "Wallet Intelligence stops reporting win rates like 570% and 9790%",
+ "summary": "The pump.fun track record at /claim-wallet was audited end to end in a real browser, and the headline numbers were wrong. Lifetime win rate, early-entry win rate and dump rate are stored as percentages, but the page multiplied them by a hundred a second time, so a wallet that wins 5.7% of its trades was shown as '570% lifetime' and a 97.9% dump rate read '9790%'. The meters beside them were pinned full for the same reason, and the colour that flags a heavy dumper was triggered by anything above 0.3%. All three now read the real figure. Four other repairs came out of the same pass. A wallet the reputation brain has graded but whose per-coin rows are still indexing used to show an empty ledger captioned 'No coins match these filters', blaming filters that were not the cause; it now explains that the ledger is still filling in. When filters genuinely do hide everything, the table says how many coins were hidden and offers one click to clear them. The ledger header no longer claims 60 coins while showing 52, since dust is hidden by default. A dropped connection used to blank the report and print the browser's raw 'Failed to fetch' beside the search box with no way forward, and now shows a proper panel naming the cause with a Try again button. The Analyze button's 'Analyzing…' label was being overwritten by the translation pass and never appeared. Keyboard and screen-reader users can now sort the ledger and open any coin: the column sorters are real buttons that announce their sort direction, every row carries a real link to that coin's dashboard, the time-window and filter controls report whether they are on, and every control on the page shows a visible focus ring.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/claim-wallet"
+ },
+ {
+ "date": "2026-08-17",
+ "title": "Crypto Categories reads correctly in all 84 languages",
+ "summary": "The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/categories"
+ },
{
"date": "2026-08-17",
"title": "The viewer's backdrop picker stops vanishing while you read it, and sharing no longer posts \"Meet Agent\"",
diff --git a/prompts/swarm-100/route-chains.md b/prompts/swarm-100/route-chains.md
deleted file mode 100644
index 692b72a7a..000000000
--- a/prompts/swarm-100/route-chains.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Route audit: /chains (Blockchain TVL by Chain)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. This route's declared entry (path, description, added date):
-
- node -e "const p=require('./data/pages.json');for(const s of p.sections)for(const g of s.pages)if(g.path==='/chains')console.log(JSON.stringify(g,null,2))"
-
-2. Find the serving implementation: grep "/chains" in vercel.json (the live
- route table server/index.mjs boots from), then list matching files in
- pages/ and src/. STRUCTURE.md maps every surface to its directory if the
- grep is ambiguous.
-3. Production right now:
-
- curl -so /dev/null -w '%{http_code}\n' https://three.ws/chains
-
-4. Start (or reuse) the local dev server: npm run dev (vite, port 3000).
-
-## Task: audit this one route end to end, then fix everything found
-
-Route: /chains ("Blockchain TVL by Chain", section "crypto").
-Declared purpose: A leaderboard of every blockchain by total value locked, with each chain's dominance share of on-chain DeFi. Live from DeFiLlama: see where liquidity actually sits across L1s and L2s.
-
-Drive the page in a real headless browser. Playwright is already a dev
-dependency; keep your probe script in the session scratchpad, never in the
-repo.
-
-1. Load http://localhost:3000/chains. Record the HTTP status, every console
- error and warning, and every failed network request.
-2. Exercise it like a first-time user: click the primary actions, run the
- primary flow if one exists, follow the page's internal links. Every button
- must do something real; every link must resolve. If the page renders data,
- prove in the network log that it came from a live endpoint, not a baked-in
- fallback array.
-3. States: verify populated, empty, loading, and error states are designed and
- reachable. Block the page's primary fetch in Playwright and confirm an
- actionable error state appears, not a blank void or a raw exception.
-4. Responsive: render at 320, 768, and 1440 px. No horizontal page scroll, no
- overlapping or clipped controls.
-5. Accessibility basics: one h1; interactive elements are real buttons or
- links with visible focus states; images carry alt text; form fields have
- labels.
-6. Head: a specific title tag and meta description that match the declared
- purpose above.
-7. Fix every defect at its root in the page's real source files and re-run the
- probe until clean. Defects in shared modules are in scope when this route
- exercises them.
-
-## Definition of done
-
-- [ ] Local load of /chains: HTTP 200, zero console errors, zero unhandled
- failed requests (a third-party outage must land in a designed fallback,
- not a broken page).
-- [ ] No dead interactive element on the page: no stub href="#", no button
- without a handler, no link to a missing path.
-- [ ] Empty, loading, error, and populated states verified.
-- [ ] 320 / 768 / 1440 px renders verified clean.
-- [ ] Title and meta description present and specific.
-- [ ] npm test passes; npm run check:rules -- --paths <touched files> exits 0.
-- [ ] Production status from step 0 recorded in the report; if production
- needs a deploy to pick up a fix, the report says so (deploys stay
- owner-gated).
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/route-chains.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index 34ab74e19..549d22401 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,22 @@
{
- "generated_at": "2026-08-17T00:54:37.680Z",
+ "generated_at": "2026-08-17T01:16:11.489Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
"entries": [
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "A shared ASL letter link now opens on that letter, not on A",
+ "summary": "The manual alphabet at /asl-alphabet was audited end to end in a real browser, and six repairs came out of it. Sharing a letter was the worst of them: a /asl-alphabet?letter=W link built the whole page around the letter A and only corrected itself once the 3D avatar had finished downloading, so anyone on a slow connection read A's description, saw A's key lit and A's look-alike note for the entire wait, on a link that promised W. The page now reads the link before it builds anything, so the right letter is on the card from the first paint and the avatar simply catches up. The Spell anything box had the opposite problem: it reported an empty or unspellable word only in the small caption pinned to the avatar, which on a phone sits a full screen above the box you just typed in, so pressing Spell it with a word full of punctuation looked like a dead button. It now answers in its own line, right under the input, and while the hand is spelling it lays the word out letter by letter and lights each one as the hand reaches it, so a long word can be followed without scrolling back up to the A-to-Z grid. That caption itself was white text on a scrim too faint to read over a pale avatar or in light mode, and is now a proper legible chip. Opening the avatar picker no longer lets a keystroke through to sign a letter behind the dialog. Switching avatars used to leave 'Loading avatar…' on screen forever once the new one had arrived, which also meant screen readers were never told the load had finished. And the Spell panel is no longer stretched to the height of the drill beside it, which left a large empty box on desktop.",
+ "link": "/asl-alphabet",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-17",
"type": "update",
@@ -17,6 +28,27 @@
"improvement"
]
},
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "Blockchain TVL by Chain is readable again, and its numbers can be copied",
+ "summary": "The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it.",
+ "link": "/chains",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "Crypto Categories reads correctly in all 84 languages",
+ "summary": "The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one.",
+ "link": "/categories",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-08-17",
"type": "update",
@@ -28,6 +60,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-17",
+ "type": "update",
+ "title": "Wallet Intelligence stops reporting win rates like 570% and 9790%",
+ "summary": "The pump.fun track record at /claim-wallet was audited end to end in a real browser, and the headline numbers were wrong. Lifetime win rate, early-entry win rate and dump rate are stored as percentages, but the page multiplied them by a hundred a second time, so a wallet that wins 5.7% of its trades was shown as '570% lifetime' and a 97.9% dump rate read '9790%'. The meters beside them were pinned full for the same reason, and the colour that flags a heavy dumper was triggered by anything above 0.3%. All three now read the real figure. Four other repairs came out of the same pass. A wallet the reputation brain has graded but whose per-coin rows are still indexing used to show an empty ledger captioned 'No coins match these filters', blaming filters that were not the cause; it now explains that the ledger is still filling in. When filters genuinely do hide everything, the table says how many coins were hidden and offers one click to clear them. The ledger header no longer claims 60 coins while showing 52, since dust is hidden by default. A dropped connection used to blank the report and print the browser's raw 'Failed to fetch' beside the search box with no way forward, and now shows a proper panel naming the cause with a Try again button. The Analyze button's 'Analyzing…' label was being overwritten by the translation pass and never appeared. Keyboard and screen-reader users can now sort the ledger and open any coin: the column sorters are real buttons that announce their sort direction, every row carries a real link to that coin's dashboard, the time-window and filter controls report whether they are on, and every control on the page shows a visible focus ring.",
+ "link": "/claim-wallet",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-16",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index 671cd1ef6..42be23dab 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -6,6 +6,14 @@
<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/>
<description>What's new on three.ws: features, improvements, and releases, newest first.</description>
<language>en</language>
+ <item>
+ <title>A shared ASL letter link now opens on that letter, not on A</title>
+ <link>https://three.ws/asl-alphabet</link>
+ <guid isPermaLink="false">2026-08-17:A shared ASL letter link now opens on that letter, not on A</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The manual alphabet at /asl-alphabet was audited end to end in a real browser, and six repairs came out of it. Sharing a letter was the worst of them: a /asl-alphabet?letter=W link built the whole page around the letter A and only corrected itself once the 3D avatar had finished downloading, so anyone on a slow connection read A's description, saw A's key lit and A's look-alike note for the entire wait, on a link that promised W. The page now reads the link before it builds anything, so the right letter is on the card from the first paint and the avatar simply catches up. The Spell anything box had the opposite problem: it reported an empty or unspellable word only in the small caption pinned to the avatar, which on a phone sits a full screen above the box you just typed in, so pressing Spell it with a word full of punctuation looked like a dead button. It now answers in its own line, right under the input, and while the hand is spelling it lays the word out letter by letter and lights each one as the hand reaches it, so a long word can be followed without scrolling back up to the A-to-Z grid. That caption itself was white text on a scrim too faint to read over a pale avatar or in light mode, and is now a proper legible chip. Opening the avatar picker no longer lets a keystroke through to sign a letter behind the dialog. Switching avatars used to leave 'Loading avatar…' on screen forever once the new one had arrived, which also meant screen readers were never told the load had finished. And the Spell panel is no longer stretched to the height of the drill beside it, which left a large empty box on desktop.</description>
+ </item>
<item>
<title>Avatar Studio now shows your whole avatar, and its Save button fits on a phone</title>
<link>https://three.ws/avatar-studio</link>
@@ -14,6 +22,22 @@
<category>fix</category>
<description>The studio camera was framing the base body from the shoulders to the knees: the face you were sculpting and the shoes you were picking were both outside the picture, and the only way to see them was to orbit the camera yourself every time the page loaded. The framing is now solved from the lens rather than guessed at, so a full-body shot really does hold the avatar head to toe, arms included, on any window shape, and the half-body and headshot views stay as tight as their names promise. On a 320px phone the top bar had been running past the edge of the screen and taking the Save avatar button with it, so a look built on a phone could not be saved at all; the bar now fits, with the Back and title labels standing down to make room. The tab strip on that same narrow layout had been hiding its labels without putting anything in their place, leaving six blank buttons, and now shows an icon per tab. The Parametric body badge that read 120+ sliders was white text on a white pill and invisible everywhere. A failed save now says the connection could not be reached and that your look is still there, instead of repeating the browser phrase Failed to fetch, and every accessory search box, every tab and the Back link now carry names a screen reader can read. Opening avatar-studio in local development also serves the same page production does, which it previously did not.</description>
</item>
+ <item>
+ <title>Blockchain TVL by Chain is readable again, and its numbers can be copied</title>
+ <link>https://three.ws/chains</link>
+ <guid isPermaLink="false">2026-08-17:Blockchain TVL by Chain is readable again, and its numbers can be copied</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it.</description>
+ </item>
+ <item>
+ <title>Crypto Categories reads correctly in all 84 languages</title>
+ <link>https://three.ws/categories</link>
+ <guid isPermaLink="false">2026-08-17:Crypto Categories reads correctly in all 84 languages</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The sector leaderboard at /categories was audited end to end in a real browser: the table, the search box, the sortable columns, the paging, and the loading, empty, error and rate-limited states all behave, at phone, tablet and desktop widths. One real defect turned up, and it only showed outside English. The page's own summary line and the description search engines and link previews read were translated once against an older wording and had kept a dash where the English now uses a colon, so every non-English visitor saw punctuation the platform does not use, in the headline copy and in the shared-link preview. All 83 translated catalogs are corrected, with the full-width colon that Japanese, Korean and Chinese actually want rather than a Latin one.</description>
+ </item>
<item>
<title>The viewer's backdrop picker stops vanishing while you read it, and sharing no longer posts &quot;Meet Agent&quot;</title>
<link>https://three.ws/app</link>
@@ -22,6 +46,14 @@
<category>fix</category>
<description>Five fixes to the 3D model viewer at /app. Opening the Backdrop picker and taking a few seconds to read the six choices used to make the picker fade out from under the cursor: the viewer hides its controls after five seconds of stillness, and the picker was not on the list of surfaces that keep them awake, so an open picker went invisible and unclickable while still counting as open. It now stays put until you choose a backdrop or close it, and the controls resume fading once it is shut. Typing in the animation search while the clips were still loading stacked a second, contradictory message under the first, so the panel read &quot;Loading clips&quot; and &quot;No clips matching&quot; at the same time, and clearing the box left behind the nonsense line &quot;No clips matching&quot; with nothing in the quotes; the search now stays quiet until there are clips to search. Sharing the viewer to X, Farcaster or Telegram published &quot;Meet Agent&quot;, an internal placeholder name, for anyone who had not loaded an agent of their own, and now uses the generic line instead. The page also shipped a sign-in panel and a welcome card that its own stylesheet blanked unconditionally, four links nobody could ever reach, and the preview card shown when the page is shared described the platform instead of the viewer. The avatar gallery behind the Avatar button is now announced to screen readers as a named dialog.</description>
</item>
+ <item>
+ <title>Wallet Intelligence stops reporting win rates like 570% and 9790%</title>
+ <link>https://three.ws/claim-wallet</link>
+ <guid isPermaLink="false">2026-08-17:Wallet Intelligence stops reporting win rates like 570% and 9790%</guid>
+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The pump.fun track record at /claim-wallet was audited end to end in a real browser, and the headline numbers were wrong. Lifetime win rate, early-entry win rate and dump rate are stored as percentages, but the page multiplied them by a hundred a second time, so a wallet that wins 5.7% of its trades was shown as '570% lifetime' and a 97.9% dump rate read '9790%'. The meters beside them were pinned full for the same reason, and the colour that flags a heavy dumper was triggered by anything above 0.3%. All three now read the real figure. Four other repairs came out of the same pass. A wallet the reputation brain has graded but whose per-coin rows are still indexing used to show an empty ledger captioned 'No coins match these filters', blaming filters that were not the cause; it now explains that the ledger is still filling in. When filters genuinely do hide everything, the table says how many coins were hidden and offers one click to clear them. The ledger header no longer claims 60 coins while showing 52, since dust is hidden by default. A dropped connection used to blank the report and print the browser's raw 'Failed to fetch' beside the search box with no way forward, and now shows a proper panel naming the cause with a Try again button. The Analyze button's 'Analyzing…' label was being overwritten by the translation pass and never appeared. Keyboard and screen-reader users can now sort the ledger and open any coin: the column sorters are real buttons that announce their sort direction, every row carries a real link to that coin's dashboard, the time-window and filter controls report whether they are on, and every control on the page shows a visible focus ring.</description>
+ </item>
<item>
<title>Docs · Avatar Artifact viewer</title>
<link>https://three.ws/docs/avatar-artifact</link>
diff --git a/public/features.json b/public/features.json
index 0a808daa6..4a3b7551b 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T00:54:37.530Z",
+ "generated_at": "2026-08-17T01:16:11.355Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/tests/e2e/chains-tvl.spec.js b/tests/e2e/chains-tvl.spec.js
new file mode 100644
index 000000000..338613359
--- /dev/null
+++ b/tests/e2e/chains-tvl.spec.js
@@ -0,0 +1,152 @@
+// /chains: the defects the route audit found, all of which reproduce on the
+// pre-fix page.
+//
+// 1. Every row carries data-href and a click handler that navigates. Dragging
+// across a cell to copy a TVL figure ends in a click on that row, so the
+// page threw the selection away and left for /chain/:name instead. There was
+// no way to copy a number off the leaderboard.
+//
+// 2. The page wrapped the shared nav in its own <header>, and nav.html supplies
+// <header class="nav"> of its own. Two banner landmarks, one nested inside
+// the other, which is three axe violations and an ambiguous landmark tree.
+//
+// 3. src/chains.js briefly shipped its row-click helpers declared twice at
+// module scope. A redeclaration is a SyntaxError, so the module never
+// evaluated and the page sat on its skeleton forever. The hydration
+// assertions here fail loudly on any repeat of that.
+//
+// DeFiLlama is live, so the assertions are about structure and behaviour rather
+// than a chain sitting at a particular rank.
+
+import { test, expect } from '@playwright/test';
+import { collectPageErrors } from './_support.js';
+
+const ROWS = '#chains-table tbody tr';
+
+async function loadPopulated(page) {
+ await page.goto('/chains', { waitUntil: 'domcontentloaded', timeout: 60_000 });
+ await page.waitForSelector(ROWS, { timeout: 60_000 });
+}
+
+test('/chains hydrates the live board from DeFiLlama with no uncaught error', async ({ page }) => {
+ const errors = collectPageErrors(page);
+ await loadPopulated(page);
+
+ // A redeclaration SyntaxError shows up exactly here: the module never runs,
+ // so no row, stat card or attribution line is ever painted.
+ expect(await page.locator(ROWS).count()).toBeGreaterThan(1);
+ await expect(page.locator('#chains-stats .cv-stat-card')).toHaveCount(3);
+ await expect(page.locator('#chains-updated')).toContainText('Data: DeFiLlama');
+ expect(errors).toEqual([]);
+
+ // Every row links to a chain page that the route table actually serves.
+ const hrefs = await page.locator(`${ROWS} td.name-cell a`).evaluateAll((a) => a.map((e) => e.getAttribute('href')));
+ expect(hrefs.length).toBe(await page.locator(ROWS).count());
+ for (const href of hrefs) expect(href).toMatch(/^\/chain\/[A-Za-z0-9 ._%-]{1,40}$/);
+});
+
+test('/chains lets a visitor select a figure out of a row instead of navigating away', async ({
+ page,
+}) => {
+ await loadPopulated(page);
+
+ const cell = page.locator(`${ROWS} td.price`).nth(1);
+ const box = await cell.boundingBox();
+ await page.mouse.move(box.x + 4, box.y + box.height / 2);
+ await page.mouse.down();
+ await page.mouse.move(box.x + box.width - 4, box.y + box.height / 2, { steps: 12 });
+ await page.mouse.up();
+
+ // The drag ends inside a row that has a click handler on it. Before the fix
+ // this navigated and discarded the selection.
+ await expect(page).toHaveURL(/\/chains$/);
+ const selected = await page.evaluate(() => window.getSelection().toString().trim());
+ expect(selected).toMatch(/\$/);
+});
+
+test('/chains still opens a chain page on a plain click anywhere in the row', async ({ page }) => {
+ await loadPopulated(page);
+
+ const row = page.locator(ROWS).first();
+ const href = await row.getAttribute('data-href');
+ expect(href).toMatch(/^\/chain\//);
+
+ // Clicking a cell that is not the name anchor exercises the row handler
+ // itself, which the drag guard must not have disabled.
+ await row.locator('td.price').click();
+ await expect(page).toHaveURL(new RegExp(`${href.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')}$`));
+});
+
+test('/chains declares exactly one banner landmark', async ({ page }) => {
+ await loadPopulated(page);
+
+ const banners = page.locator('header, [role="banner"]');
+ await expect(banners).toHaveCount(1);
+ await expect(banners.first()).toHaveClass(/\bnav\b/);
+});
+
+test('/chains sorts by keyboard and keeps focus on the header that was activated', async ({
+ page,
+}) => {
+ await loadPopulated(page);
+
+ const dominance = page.locator('#chains-table th[data-key="share_pct"]');
+ await expect(dominance).toHaveAttribute('aria-sort', 'none');
+ await dominance.focus();
+ await page.keyboard.press('Enter');
+
+ // The header node is replaced by the re-render, so without the refocus the
+ // keyboard user is dropped back to the document.
+ await expect(page.locator('#chains-table th[data-key="share_pct"]')).toHaveAttribute(
+ 'aria-sort',
+ 'descending',
+ );
+ expect(await page.evaluate(() => document.activeElement.dataset.key)).toBe('share_pct');
+});
+
+test('/chains offers a working retry when the feed fails, and distinct copy when it is empty', async ({
+ page,
+}) => {
+ await page.route('**/api/defi/chains', (r) => r.abort());
+ await page.goto('/chains', { waitUntil: 'domcontentloaded', timeout: 60_000 });
+
+ const failed = page.locator('#chains-table .cv-empty');
+ await expect(failed).toContainText('temporarily unavailable');
+ // A "$0.00" total would read as a claim that cross-chain TVL is zero.
+ await expect(page.locator('#chains-stats .cv-stat-card')).toHaveCount(0);
+
+ await page.unroute('**/api/defi/chains');
+ await failed.locator('[data-act="retry"]').click();
+ await page.waitForSelector(ROWS, { timeout: 60_000 });
+ expect(await page.locator(ROWS).count()).toBeGreaterThan(1);
+
+ await page.route('**/api/defi/chains', (r) =>
+ r.fulfill({
+ status: 200,
+ contentType: 'application/json',
+ body: JSON.stringify({ total_tvl: 0, chain_count: 0, chains: [], updated_at: Date.now() }),
+ }),
+ );
+ await page.reload({ waitUntil: 'domcontentloaded' });
+ await expect(page.locator('#chains-table .cv-empty')).toContainText('No chain TVL is being reported');
+});
+
+test('/chains fits a 320px viewport without a sideways scroll', async ({ page }) => {
+ await page.setViewportSize({ width: 320, height: 900 });
+ await loadPopulated(page);
+
+ const overflow = await page.evaluate(
+ () => document.documentElement.scrollWidth > document.documentElement.clientWidth + 1,
+ );
+ expect(overflow).toBe(false);
+
+ // The rank and share-bar columns drop out below 640px so chain, TVL and
+ // dominance all land inside the viewport rather than behind a scroller.
+ const wrapScrolls = await page.evaluate(() => {
+ const w = document.querySelector('#chains-table .cv-table-wrap');
+ return w.scrollWidth > w.clientWidth + 1;
+ });
+ expect(wrapScrolls).toBe(false);
+ await expect(page.locator('#chains-table th[data-key="tvl"]')).toBeVisible();
+ await expect(page.locator('#chains-table th[data-key="share_pct"]')).toBeVisible();
+});