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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(forged): surface the real reason the gallery failed and stop the thumbnails drag-orbiting under their own link
nirholas1817ded0d621
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex cdb874871..dd0aab45b 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -38,12 +38,14 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Tabbing into the Forge prompt box now shows you where you are**: The Forge composer (three.ws/forge and the maximum-quality lane at three.ws/forge-max) draws its describe-it box, its photo-guidance box and its sketch-description box without a border, so the card reads as one clean surface. That styling had also switched off the browser focus outline, which meant anyone moving through the page with the Tab key landed in the main prompt field with no visible sign that they were there: the page looked identical whether the box had keyboard focus or not, on the single most important input on the surface. All three boxes now draw a focus ring when you reach them by keyboard, and only by keyboard, so clicking in with a mouse keeps the seamless look it always had. The rest of the lane was driven end to end in a real browser at phone, tablet and desktop widths: High stays pinned when you open /forge-max, the quality switches move between Draft, Standard and High with the holder gate reflected on the Generate button, and a busy or failing generator lands on a designed message with a retry rather than a blank panel. (`/forge-max`) `[fix, improvement]`- **Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down**: The /create/video page turns one of your avatars plus an audio clip into a lip-synced video, and it was driven end to end in a real browser: every state, every button, every width. The worst finding was invisible from the page. The reference frame the GPU worker renders from was being taken from whatever the browser had handy, which for an avatar with no thumbnail meant its 3D model file. The worker saved that as the reference photo and then failed on it minutes later, after the wait had already been spent. The page now sends only the avatar, and the server resolves a real image for it: the stored thumbnail, or a fresh portrait render when there is none. Second, the GPU renderer is a separate service, and when it is not running the only signal was a failure after you had already picked a file and uploaded it. The page now asks first and, if the lane is down, says so at the top, keeps Generate switched off, and points at the Avatar Studio and prompt-to-avatar in the meantime. The rest is the ordinary polish an audit turns up: a failed avatar list used to look identical to owning no avatars, so it sent people off to create one they already had, and now it says what broke and offers a retry; having no avatars yet gets a real empty state with a link to make one; the Generate button always explains what it is still waiting for and, once audio is in, how many clips of video that audio is worth; the clip you picked can be played back with its length and size before you spend a generation on it; a render job that goes unreachable now says so after thirty seconds instead of spinning for twenty minutes; and after a spent free trial the button under the error no longer stayed stuck on Upgrade plan for every later error. Avatar thumbnails are real buttons with visible focus rings, the two form fields have proper labels, and the second animated avatar that the site companion used to drop onto this page no longer loads over the one you are working on. (`/create/video`) `[fix, improvement]`- **Text to 3D gets its footer back, a retry button that knows when to open, and an honest name for the model that refined your prompt**: The /forge-spark page was driven end to end in a real browser. The closing note under the workspace was written as a page footer, and the site's old corner-credit styling for the 3D viewer pages had quietly claimed it: it was pulled out of the layout into a floating monospace strip that sat on top of the viewer on a desktop, and on a 320px phone it landed across the composer with its link to the full studio pushed off the edge of the screen entirely. That note is now ordinary page text, centered under the workspace where it belongs, and the real three.ws footer, with its full set of links, is on the page for the first time. When a generation fails there is now a Try again button inside the error itself, so recovery does not mean scrolling back to the top; when the generator answers that it is busy, the button counts down and opens exactly when a retry can actually get through. A stage that fails is marked in red instead of silently dropping back to grey, the wait now shows real elapsed seconds so a cold reconstruction lane no longer reads as a hang, and the first step is renamed to whatever model actually answered, because the prompt refiner is a chain of engines and Nemotron is only the first one it tries. (`/forge-spark`) `[fix, improvement]`+- **The Agent-Forged Gallery says what actually went wrong, and its thumbnails stop fighting the link they sit in**: The gallery of 3D props that the platform's autonomous agents bought with real USDC was driven end to end in a real browser: a hundred live cards, the category chips, prompt search, all four sorts, and the loading, empty and error states at phone, tablet and desktop widths. The finding worth caring about was in the error state. When the feed failed with a server error rather than a dropped connection, the page still said only "Something went wrong", because the translation pass ran after the failed request and overwrote the specific reason the page had just written there. The reason now lives on its own line that translation leaves alone, so a failure tells you what it was and the Try again button next to it recovers the full gallery. Each prop's spinning preview had also been set up to drag-orbit under the link that wraps it, from an attribute written to do the exact opposite; the previews are now purely decorative and the whole tile is just a link to the 3D viewer. The category chips announced themselves to screen readers as tabs without being tabs, and never said which family the grid was filtered to; they are now a labelled group of toggle buttons that report their own state. Every control on the page (search box, sort, chips, the Preview and Download buttons, the thumbnail itself) now shows a focus ring when reached by keyboard, where the search box previously had its ring switched off entirely. A prop still waiting on its settlement no longer renders an empty price, and one whose model file is not written yet no longer offers a Preview and Download that lead nowhere. (`/forged`) `[fix, improvement]`- **The avatar SDK bundle we ship is now built from the code we deploy**: The <agent-3d> runtime that sites load from three.ws is a single bundled file, and the production build never rebuilt it. It was copied from whatever the build machine happened to have on disk, which could be days older than the code being deployed, so a fix to the avatar element could ship everywhere else on the site and quietly not reach the SDK. The deploy now rebuilds that bundle from the same commit as the rest of the release, every time. Nothing to change on your side: existing embeds keep working and simply pick up the current runtime. (`/avatar-sdk`) `[fix, sdk, infra]`- **The Character Library counts its own characters, and fills the screen while it does**: The library page had been advertising 106 rigged characters since launch. There are 107 on the shelf today, and there will be more tomorrow, so the number is no longer typed into the headline, the page description or the share card: the page asks the library how many it has and prints the answer under the hero. The grid also stopped wasting a third of a desktop screen. A layout rule left the page shrink-to-fitting to about two thirds of the window, so a wide monitor showed three columns where five fit; it now uses the full width it was designed for. Every character card previously carried a hidden second tab stop that announced the same name as the card itself, which made keyboard browsing twice as long as it needed to be, and thumbnails could not be dragged out of alignment by an accidental swipe anymore because the preview no longer pretends to be an interactive 3D control. The search box has a visible focus ring again instead of a one pixel border shift, and when the library cannot be reached the page now says what actually went wrong rather than reverting to a generic sentence a moment later. (`/character-library`) `[fix, improvement]`- **The Characters gallery pages past the first screen, and stops fighting dark mode**: The character gallery at /characters was audited end to end in a real browser: loading the feed, both sort orders, search, Load more, following a card through to its character page, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that the Top sort was quietly broken. Sorting by most-chatted read the right first screen, but pressing Load more asked the server to continue from the wrong place, so the feed ended after eight characters out of more than two thousand. It now pages all the way through, in order. The page also ignored the site theme: it painted a fixed light-blue background under the dark header no matter what you had chosen, which is now fixed in both directions, and wallet addresses on the cards were nearly invisible on a light background everywhere they appear on the site. The gallery filled only a narrow strip down the middle of a desktop screen and now uses the full width, up to four cards across. If the feed failed to load you got one line of grey text and no way to retry; there is now a proper message with a Try again button, a failed Load more keeps the characters you already had, and searching for something with no matches offers to clear the search rather than leaving you at a dead end. Pressing Top while the first screen was still loading used to light up the button and change nothing, so you were left reading New results under a Top heading. The search box had no label for screen readers, the sort buttons never showed which was selected, and neither they nor Load more showed a focus outline for anyone navigating by keyboard. Keyboard users can also now skip the header and land in the gallery. Finally, the feed itself is several times faster to answer on a cold request, because it no longer counts every conversation of every published character just to show you twenty-four of them. (`/characters`) `[fix, improvement]`- **The Community page's live activity feed renders as readable rows again**: The activity list on the Community page was building each row as a link wrapped around another link, which no browser can parse: every entry was torn into three stray fragments, so the creator, the item and its thumbnail landed on separate lines with gaps between them and the whole list was unreadable. Rows are now single, valid entries again: click anywhere on one to open the creation, or click the creator's name to open their profile. If the feed cannot load, or returns something the page cannot read, you get a clear message and a Try again button instead of skeleton placeholders that never resolve. The page also follows the light and dark theme switch now instead of staying black on a light canvas, and the newsletter section finally has the signup field its text promises, rather than sending you hunting for the one in the footer. (`/community`) `[fix, improvement]`- **The Concierge page stops cutting itself off on a phone, and its install tabs work from the keyboard**: Three fixes to the Concierge landing page. On a narrow phone screen the whole page was being sized against the longest line of the install snippet, which pushed the column roughly twice as wide as the screen; because the site clips sideways overflow, the right-hand half of every headline, paragraph and button was simply cut off with no way to scroll to it. The column now fits the screen and the code snippet scrolls inside its own box, the way it already did on a laptop. The four install tabs (one tag, web component, npm, imperative) announced themselves to a screen reader as tabs but were not wired to the panels they open and ignored the arrow keys; they now move with Left, Right, Home and End, and each tab is properly tied to its snippet. Copy buttons also say which snippet they copy, and if the browser blocks the clipboard the snippet is selected for you so Ctrl+C still works. Finally, the passive "Have you tried" suggestion card could land on top of the live concierge demo in the corner; it now stacks clear of it. (`/concierge`) `[fix, improvement]`- **The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it**: Three fixes to the front door for creating, plus a strip of your own avatars that was never once drawn. The page is meant to greet a returning creator with "Start from one of yours" and a row of the avatars they have already made, one click from remixing any of them. It read the library reply in the wrong shape, decided it had received nothing, and hid the row every single time, so nobody has ever seen it. It reads the reply correctly now and the row appears, with a real thumbnail for each avatar. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says "Coming soon" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image. (`/create`) `[fix, improvement]`+- **The Money Flow Map stops cutting its own table off on a phone, and a refresh no longer blanks the map**: The map of who pays whom at three.ws/flow was driven end to end in a real browser: every window, every filter, the legend toggles, search, zoom, the wallet table and the loading, empty and error states, at phone, tablet and desktop widths. Two findings mattered. On a phone the page was quietly cutting itself in half: the "What the money bought" panel and the entire wallet table were laid out wider than the screen and then clipped away, with no way to scroll to them, so the text version of the graph (the part a screen reader and a keyboard actually use) was unreachable on mobile. The table now scrolls inside its own frame and nothing runs off the edge. Second, the page re-reads the chain every minute, and every one of those re-reads used to cover the drawn map with a loading spinner, so a live page flickered into looking broken once a minute. A background re-read now leaves the map alone and reports itself on the timestamp next to the controls, and if it fails, the graph you were reading stays on screen with the failure named there instead of being wiped for an error panel. Switching the time window still shows the loading state, because that genuinely replaces the topology, and it now cancels a read that is still in flight: a slow 90-day request could previously land after you had already switched to 7 days and draw a window you were not looking at, under a button that said something else. The rest is the polish an audit turns up: the table's own caption said "no wallets match the current filters" even in a quiet window where you had set no filters, and now tells those two situations apart; the empty state no longer offers a "Show 90 days" button while you are already on 90 days, and offers the next longer window instead; the clear-search cross stayed on screen after Clear filters had already emptied the box; and the canvas now resolves its colours once per frame rather than several times per line, which is what a four-hundred-route graph feels like on a laptop. (`/flow`) `[fix, improvement]`- **The Pole Club audio controls no longer fall off the edge of a small phone**: On a narrow phone the club's top bar ran out of room and simply cut off whatever did not fit, and the page cannot scroll sideways, so the mute button and the 8D audio toggle were gone with no way to reach them. The bar now gives up the parts that are only there to read (the tagline and the price and rail labels, all of which the panel's How it works section repeats) and keeps both controls at full size at every width, down to a 320px screen. (`/club`) `[fix]`- **The Pole Club leaderboard now ranks the dancers who are actually on the poles**: The club's leaderboard was reading names out of the payout registry instead of off the stage, so it listed four dancers under names matching none of the three at the poles, every one of them sitting at zero. It now names each dancer exactly as her pole card does, drops entries for dancers who are not in tonight's lineup and have never been tipped, and says what a quiet board actually means: the 24h and 1h views tell you the club has been quiet rather than claiming nobody has ever tipped, which was never true while the all-time board was full. Keyboard and screen-reader visitors get the rest of the pass: the page carries one real heading instead of five competing ones, Skip to stage now lands you on the stage, and the controls belonging to the walk-in (the agent picker, the Enter the club prompt) no longer sit invisibly in the tab order once you are inside the room. (`/club`) `[fix, improvement]`- **The Runway Lab called a stalled payment rail healthy, because nobody had tried to pay that day**: The Runway Lab at /economy-lab is the page that tells you whether platform payments can still settle, and it was audited end to end in a real browser. It was getting the headline exactly backwards. The fee wallet that pays Solana network fees is currently below the hard floor it is never allowed to spend past, so nothing could settle at all, and the banner read "settlement is healthy" in green. The cause was that the page seeded its demand knob from measured traffic, the rail had taken no payments in 24 hours, and a projection of zero attempts came back with nothing refused, which the model scored as success. Zero attempts is now its own answer rather than a pass mark, and when the log shows no traffic the knob starts at a stated example load and says so instead of quietly projecting nothing. The live panel matches: a wallet under its floor no longer shows a green daily allowance it cannot reach, and an unread balance no longer prints as a confident 0.0%. If the page cannot read the rail at all, every knob now visibly switches off and there is a retry button, rather than six sliders that look live and do nothing. The projection chart was unreadable on a small balance, labelling all five of its gridlines 0.002 or 0.001, and on a phone it clipped those labels, ran its legend off the panel and stamped its own captions over the bars. Tapping a knob's help mark on a phone opened its explanation and closed it again in the same tap, so the explanations were unreachable on touch. Underneath, a projection of a starved rail was doing one full pass of the real settle-path check per refused payment, hundreds of thousands of them for a single slider drag; it now settles each refused hour in one step and gives the same numbers. (`/economy-lab`) `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex 1014410f7..1b19ed228 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,26 @@{"$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": "The Money Flow Map stops cutting its own table off on a phone, and a refresh no longer blanks the map",+ "summary": "The map of who pays whom at three.ws/flow was driven end to end in a real browser: every window, every filter, the legend toggles, search, zoom, the wallet table and the loading, empty and error states, at phone, tablet and desktop widths. Two findings mattered. On a phone the page was quietly cutting itself in half: the \"What the money bought\" panel and the entire wallet table were laid out wider than the screen and then clipped away, with no way to scroll to them, so the text version of the graph (the part a screen reader and a keyboard actually use) was unreachable on mobile. The table now scrolls inside its own frame and nothing runs off the edge. Second, the page re-reads the chain every minute, and every one of those re-reads used to cover the drawn map with a loading spinner, so a live page flickered into looking broken once a minute. A background re-read now leaves the map alone and reports itself on the timestamp next to the controls, and if it fails, the graph you were reading stays on screen with the failure named there instead of being wiped for an error panel. Switching the time window still shows the loading state, because that genuinely replaces the topology, and it now cancels a read that is still in flight: a slow 90-day request could previously land after you had already switched to 7 days and draw a window you were not looking at, under a button that said something else. The rest is the polish an audit turns up: the table's own caption said \"no wallets match the current filters\" even in a quiet window where you had set no filters, and now tells those two situations apart; the empty state no longer offers a \"Show 90 days\" button while you are already on 90 days, and offers the next longer window instead; the clear-search cross stayed on screen after Clear filters had already emptied the box; and the canvas now resolves its colours once per frame rather than several times per line, which is what a four-hundred-route graph feels like on a laptop.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/flow"+ },+ {+ "date": "2026-08-17",+ "title": "The Agent-Forged Gallery says what actually went wrong, and its thumbnails stop fighting the link they sit in",+ "summary": "The gallery of 3D props that the platform's autonomous agents bought with real USDC was driven end to end in a real browser: a hundred live cards, the category chips, prompt search, all four sorts, and the loading, empty and error states at phone, tablet and desktop widths. The finding worth caring about was in the error state. When the feed failed with a server error rather than a dropped connection, the page still said only \"Something went wrong\", because the translation pass ran after the failed request and overwrote the specific reason the page had just written there. The reason now lives on its own line that translation leaves alone, so a failure tells you what it was and the Try again button next to it recovers the full gallery. Each prop's spinning preview had also been set up to drag-orbit under the link that wraps it, from an attribute written to do the exact opposite; the previews are now purely decorative and the whole tile is just a link to the 3D viewer. The category chips announced themselves to screen readers as tabs without being tabs, and never said which family the grid was filtered to; they are now a labelled group of toggle buttons that report their own state. Every control on the page (search box, sort, chips, the Preview and Download buttons, the thumbnail itself) now shows a focus ring when reached by keyboard, where the search box previously had its ring switched off entirely. A prop still waiting on its settlement no longer renders an empty price, and one whose model file is not written yet no longer offers a Preview and Download that lead nowhere.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/forged"+ },{"date": "2026-08-17","title": "watsonx Constellation: stars actually open when you click them, and the page says which model really answered",diff --git a/docs/api-reference.md b/docs/api-reference.mdindex 206cfe019..66b52eeb0 100644--- a/docs/api-reference.md+++ b/docs/api-reference.md@@ -1706,7 +1706,9 @@ only.```GET /api/forged → recent agent-bought props (status done)-GET /api/forged?category=crate → filter by prop family (crate|barrel|furniture|terrain)+GET /api/forged?category=container → filter by prop family (club-decor|ar-object|+ diorama-set|avatar-item|vehicle|container|+ furniture|terrain)GET /api/forged?status=all → include queued/failed rows (audit view)GET /api/forged?limit=60 → page size (default 30, max 100)```diff --git a/pages/forged.html b/pages/forged.htmlindex acc3a3762..2fd898788 100644--- a/pages/forged.html+++ b/pages/forged.html@@ -169,6 +169,8 @@.ch-state-icon { font-size: 40px; margin-bottom: 12px; }.ch-state h2 { color: var(--ink); margin: 0 0 8px; font-size: 20px; }.ch-state p { max-width: 52ch; margin: 0 auto 18px; line-height: 1.55; }+ .ch-state-detail { font-family: var(--font-mono); font-size: 12.5px; color: var(--ink-dim); }+ .ch-state-detail:empty { display: none; }.ch-hbtn {display: inline-flex; align-items: center; gap: 8px; padding: 10px 18px;@@ -261,7 +263,11 @@<div data-role="error" class="ch-state" hidden><div class="ch-state-icon">⚠️</div><h2 data-i18n="forged.couldn_t_load_the_gallery">Couldn't load the gallery</h2>- <p data-role="error-msg" data-i18n="forged.something_went_wrong_loading_the_agent_forge">Something went wrong loading the agent-forged gallery.</p>+ <p data-i18n="forged.something_went_wrong_loading_the_agent_forge">Something went wrong loading the agent-forged gallery.</p>+ <!-- The specific reason is written by the page script and must NOT carry a+ data-i18n key: the translation pass runs after the failed fetch and would+ overwrite it with the generic sentence above. -->+ <p class="ch-state-detail" data-role="error-msg"></p><button class="ch-hbtn ch-hbtn--secondary" data-role="retry" data-i18n="forged.try_again">Try again</button></div></main>diff --git a/prompts/swarm-100/route-forged.md b/prompts/swarm-100/route-forged.mddeleted file mode 100644index af0c543ce..000000000--- a/prompts/swarm-100/route-forged.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /forged (Agent-Forged Gallery)--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==='/forged')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/forged" 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/forged--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: /forged ("Agent-Forged Gallery", section "main").-Declared purpose: 3D props bought by autonomous AI agents with real USDC over x402. Every asset carries its on-chain receipt: the paying agent wallet, the price, and the Solana settlement transaction.--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/forged. 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 /forged: 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-forged.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.jsonindex 09739bc6a..b373f6933 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T06:57:02.770Z",+ "generated_at": "2026-08-17T07:34:35.423Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -357,6 +357,17 @@"improvement"]},+ {+ "date": "2026-08-17",+ "type": "update",+ "title": "The Agent-Forged Gallery says what actually went wrong, and its thumbnails stop fighting the link they sit in",+ "summary": "The gallery of 3D props that the platform's autonomous agents bought with real USDC was driven end to end in a real browser: a hundred live cards, the category chips, prompt search, all four sorts, and the loading, empty and error states at phone, tablet and desktop widths. The finding worth caring about was in the error state. When the feed failed with a server error rather than a dropped connection, the page still said only \"Something went wrong\", because the translation pass ran after the failed request and overwrote the specific reason the page had just written there. The reason now lives on its own line that translation leaves alone, so a failure tells you what it was and the Try again button next to it recovers the full gallery. Each prop's spinning preview had also been set up to drag-orbit under the link that wraps it, from an attribute written to do the exact opposite; the previews are now purely decorative and the whole tile is just a link to the 3D viewer. The category chips announced themselves to screen readers as tabs without being tabs, and never said which family the grid was filtered to; they are now a labelled group of toggle buttons that report their own state. Every control on the page (search box, sort, chips, the Preview and Download buttons, the thumbnail itself) now shows a focus ring when reached by keyboard, where the search box previously had its ring switched off entirely. A prop still waiting on its settlement no longer renders an empty price, and one whose model file is not written yet no longer offers a Preview and Download that lead nowhere.",+ "link": "/forged",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-17","type": "update",@@ -424,6 +435,17 @@"improvement"]},+ {+ "date": "2026-08-17",+ "type": "update",+ "title": "The Money Flow Map stops cutting its own table off on a phone, and a refresh no longer blanks the map",+ "summary": "The map of who pays whom at three.ws/flow was driven end to end in a real browser: every window, every filter, the legend toggles, search, zoom, the wallet table and the loading, empty and error states, at phone, tablet and desktop widths. Two findings mattered. On a phone the page was quietly cutting itself in half: the \"What the money bought\" panel and the entire wallet table were laid out wider than the screen and then clipped away, with no way to scroll to them, so the text version of the graph (the part a screen reader and a keyboard actually use) was unreachable on mobile. The table now scrolls inside its own frame and nothing runs off the edge. Second, the page re-reads the chain every minute, and every one of those re-reads used to cover the drawn map with a loading spinner, so a live page flickered into looking broken once a minute. A background re-read now leaves the map alone and reports itself on the timestamp next to the controls, and if it fails, the graph you were reading stays on screen with the failure named there instead of being wiped for an error panel. Switching the time window still shows the loading state, because that genuinely replaces the topology, and it now cancels a read that is still in flight: a slow 90-day request could previously land after you had already switched to 7 days and draw a window you were not looking at, under a button that said something else. The rest is the polish an audit turns up: the table's own caption said \"no wallets match the current filters\" even in a quiet window where you had set no filters, and now tells those two situations apart; the empty state no longer offers a \"Show 90 days\" button while you are already on 90 days, and offers the next longer window instead; the clear-search cross stayed on screen after Clear filters had already emptied the box; and the canvas now resolves its colours once per frame rather than several times per line, which is what a four-hundred-route graph feels like on a laptop.",+ "link": "/flow",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-17","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex e2c7bebb5..a98b15d75 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -262,6 +262,14 @@<category>fix</category><description>The /forge-spark page was driven end to end in a real browser. The closing note under the workspace was written as a page footer, and the site's old corner-credit styling for the 3D viewer pages had quietly claimed it: it was pulled out of the layout into a floating monospace strip that sat on top of the viewer on a desktop, and on a 320px phone it landed across the composer with its link to the full studio pushed off the edge of the screen entirely. That note is now ordinary page text, centered under the workspace where it belongs, and the real three.ws footer, with its full set of links, is on the page for the first time. When a generation fails there is now a Try again button inside the error itself, so recovery does not mean scrolling back to the top; when the generator answers that it is busy, the button counts down and opens exactly when a retry can actually get through. A stage that fails is marked in red instead of silently dropping back to grey, the wait now shows real elapsed seconds so a cold reconstruction lane no longer reads as a hang, and the first step is renamed to whatever model actually answered, because the prompt refiner is a chain of engines and Nemotron is only the first one it tries.</description></item>+ <item>+ <title>The Agent-Forged Gallery says what actually went wrong, and its thumbnails stop fighting the link they sit in</title>+ <link>https://three.ws/forged</link>+ <guid isPermaLink="false">2026-08-17:The Agent-Forged Gallery says what actually went wrong, and its thumbnails stop fighting the link they sit in</guid>+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The gallery of 3D props that the platform's autonomous agents bought with real USDC was driven end to end in a real browser: a hundred live cards, the category chips, prompt search, all four sorts, and the loading, empty and error states at phone, tablet and desktop widths. The finding worth caring about was in the error state. When the feed failed with a server error rather than a dropped connection, the page still said only "Something went wrong", because the translation pass ran after the failed request and overwrote the specific reason the page had just written there. The reason now lives on its own line that translation leaves alone, so a failure tells you what it was and the Try again button next to it recovers the full gallery. Each prop's spinning preview had also been set up to drag-orbit under the link that wraps it, from an attribute written to do the exact opposite; the previews are now purely decorative and the whole tile is just a link to the 3D viewer. The category chips announced themselves to screen readers as tabs without being tabs, and never said which family the grid was filtered to; they are now a labelled group of toggle buttons that report their own state. Every control on the page (search box, sort, chips, the Preview and Download buttons, the thumbnail itself) now shows a focus ring when reached by keyboard, where the search box previously had its ring switched off entirely. A prop still waiting on its settlement no longer renders an empty price, and one whose model file is not written yet no longer offers a Preview and Download that lead nowhere.</description>+ </item><item><title>The avatar SDK bundle we ship is now built from the code we deploy</title><link>https://three.ws/avatar-sdk</link>@@ -310,6 +318,14 @@<category>fix</category><description>Three fixes to the front door for creating, plus a strip of your own avatars that was never once drawn. The page is meant to greet a returning creator with "Start from one of yours" and a row of the avatars they have already made, one click from remixing any of them. It read the library reply in the wrong shape, decided it had received nothing, and hid the row every single time, so nobody has ever seen it. It reads the reply correctly now and the row appears, with a real thumbnail for each avatar. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says "Coming soon" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image.</description></item>+ <item>+ <title>The Money Flow Map stops cutting its own table off on a phone, and a refresh no longer blanks the map</title>+ <link>https://three.ws/flow</link>+ <guid isPermaLink="false">2026-08-17:The Money Flow Map stops cutting its own table off on a phone, and a refresh no longer blanks the map</guid>+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The map of who pays whom at three.ws/flow was driven end to end in a real browser: every window, every filter, the legend toggles, search, zoom, the wallet table and the loading, empty and error states, at phone, tablet and desktop widths. Two findings mattered. On a phone the page was quietly cutting itself in half: the "What the money bought" panel and the entire wallet table were laid out wider than the screen and then clipped away, with no way to scroll to them, so the text version of the graph (the part a screen reader and a keyboard actually use) was unreachable on mobile. The table now scrolls inside its own frame and nothing runs off the edge. Second, the page re-reads the chain every minute, and every one of those re-reads used to cover the drawn map with a loading spinner, so a live page flickered into looking broken once a minute. A background re-read now leaves the map alone and reports itself on the timestamp next to the controls, and if it fails, the graph you were reading stays on screen with the failure named there instead of being wiped for an error panel. Switching the time window still shows the loading state, because that genuinely replaces the topology, and it now cancels a read that is still in flight: a slow 90-day request could previously land after you had already switched to 7 days and draw a window you were not looking at, under a button that said something else. The rest is the polish an audit turns up: the table's own caption said "no wallets match the current filters" even in a quiet window where you had set no filters, and now tells those two situations apart; the empty state no longer offers a "Show 90 days" button while you are already on 90 days, and offers the next longer window instead; the clear-search cross stayed on screen after Clear filters had already emptied the box; and the canvas now resolves its colours once per frame rather than several times per line, which is what a four-hundred-route graph feels like on a laptop.</description>+ </item><item><title>The Pole Club audio controls no longer fall off the edge of a small phone</title><link>https://three.ws/club</link>diff --git a/public/features.json b/public/features.jsonindex a25ab7473..c58675fba 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T06:57:02.679Z",+ "generated_at": "2026-08-17T07:34:35.315Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/src/forged-gallery.js b/src/forged-gallery.jsindex ee567220d..98ac68d75 100644--- a/src/forged-gallery.js+++ b/src/forged-gallery.js@@ -52,11 +52,11 @@ function formatWhen(ts) {// A card's <model-viewer> is deliberately control-free. model-viewer reads// `camera-controls` as a boolean attribute, so the old `camera-controls="false"`-// switched controls ON: it made every thumbnail drag-orbit and swallow the click-// meant for the link that wraps it, so the card's primary action did nothing.-// Dropping the attribute leaves auto-rotate (which does not need controls) and-// hands the click straight to the link. The `disable-*` and `interaction-prompt`-// attributes went with it; they only ever qualified camera-controls.+// switched controls ON, so every thumbnail drag-orbited under the link that+// wraps it: the opposite of what the attribute was written to say. Dropping it+// leaves auto-rotate (which does not need controls) and the link as the card's+// only affordance. The `disable-*` and `interaction-prompt` attributes went+// with it; they only ever qualified camera-controls.function renderCard(p) {const glbUrl = p.glb_url || '';const alt = p.prompt || 'Agent-forged prop';@@ -180,7 +180,7 @@ async function load() {applyView();} catch (err) {show(els.loading, false); show(els.grid, false); show(els.empty, false); show(els.emptySearch, false); show(els.error, true);- if (els.errorMsg) els.errorMsg.textContent = `Failed to load the gallery: ${err?.message || 'network error'}`;+ if (els.errorMsg) els.errorMsg.textContent = err?.message || 'network error';}}