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
chore(prompts): retire the vault route audit work order now the page is verified
nirholas5279ecfddcd7
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 133fb546b..4abb3dd16 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -37,6 +37,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Plan checkout: a paid upgrade can only ever settle on real mainnet, and a late payment is no longer stranded**: Paying for a plan creates a quote, you send the funds, then the server checks the chain before it upgrades you. Three things in that path were wrong. The checkout side has always refused test-network quotes in production, because test-network dollars are free from a faucet, but the confirm side still let a caller name the test network itself, and it is the confirm side that decides which chain it looks at and which dollar it accepts. Both ends now read the same setting, so a production upgrade can only ever be settled by real funds on mainnet. Second, an Ethereum-side payment has to wait twelve blocks before it counts, which meant funds sent near the end of a session could land on-chain and then be refused for arriving late, with the money already gone; that lane now honors the same one-hour grace window the Solana lane has, so an on-chain payment is always claimable. Third, confirming an Ethereum payment could reach a Solana quote and mark it expired, and asking to buy a skill from a malformed agent id answered a generic server error instead of telling you what was wrong with the request. (`/pricing`) `[fix, security]`- **Portfolio token pages price Base and Arbitrum holdings correctly**: Opening a token from your portfolio asked Ethereum for the price no matter which chain the token was actually on. Almost every agent wallet runs on Base, so the most common holdings came back with no price, no chart and a shortened contract address instead of a ticker, even though the balance was right there in the list. Each token is now priced on its own chain, labelled with its real symbol and decimals, and native gas tokens use the right coin per chain (POL on Polygon, BNB on BNB Chain, AVAX on Avalanche) instead of always quoting ETH. Chains nobody prices, such as testnets, now say so plainly rather than showing another chain's number. `[fix]`- **Posed avatar renders finally come out posed**: Asking the public avatar renderer for a pose returned a T-pose on most models: it matched bone names against a short hand-written list, and any rig that did not use those exact names (including every Mixamo export) was silently left in its bind pose while the response still claimed the pose had been applied. The renderer now uses the same posing engine the pose studio uses, so a preset now lands whatever naming convention the model's skeleton uses, and the camera frames the posed figure rather than the unposed one. The background colour on both public renderers is now checked before it is used, and the per-render budget is counted across the whole fleet instead of per server. (`/docs/api-reference`) `[fix, security]`+- **Premium Vanity Inventory shows the whole shelf, and is readable in light mode**: The premium vanity shelf listed only the first hundred pre-ground addresses out of the hundreds actually in stock, with nothing on the page saying so: every address past that point was unbuyable because no one could see it. The page now loads sixty at a time, states plainly how many of the total you are looking at, and pages through the rest on demand. In light mode the page was close to unusable, because the addresses themselves, the buy dialog, and the custody notice were all painted in colours meant for the black background; the whole page now switches palette properly. Four smaller fixes shipped with it: the retry button on a failed load rendered as raw browser chrome and threw away your filter, so it is now a real button that simply re-runs the search you had; filtering down to no matches now offers a one-click way to clear the filter instead of just suggesting it; the word x402 in the intro linked to the vanity gallery rather than the x402 page; and keyboard users get a visible focus ring on the search and sort controls, which previously had theirs suppressed. (`/vanity/premium`) `[fix, improvement]`- **Private avatars no longer show their picture in registry lookups**: The registry lookup that turns an agent id, avatar id, slug, or Solana mint into one record already refused to hand out the 3D model of a private avatar, but it still returned the rendered preview image of that same avatar, so anyone holding the id could see what a private creation looked like. The preview is now gated on exactly the same visibility as the model: a private avatar returns its name and identity and no imagery at all. The embeddable widget read did the same thing with its avatar thumbnail and got the same gate. Separately, every read path that turns a stored thumbnail into a URL now goes through the one resolver that drops the old broken image keys, so agent manifests, token metadata, and launch feeds stop publishing image links that answer 404. `[security, fix]`- **Push notification sign-up now only accepts a real push service address**: Turning on browser notifications hands the platform the address your browser wants alerts delivered to, and that address is one the platform later calls from its own servers. It was stored exactly as given, so a crafted sign-up could point it at an internal address instead of a push service and use the delivery job as a way to knock on doors inside our own network. Sign-up now checks the address before storing it: it has to be an ordinary secure web address on a genuinely public host, or it is refused with a clear reason. If the check cannot finish because name lookup is briefly down, the browser is told to try again rather than being turned away for good. Delivery re-checks every stored address at send time too, so anything registered before this landed can never be dialed, and an address that could never be legal is dropped from the list the way an expired one already was. `[security]`- **Rotating or revoking an x402 API key now requires a proof the request came from you**: The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all. (`/billing/keys`) `[security, fix]`@@ -46,6 +47,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Seeding an agent from GitHub is locked to your own click, and a mistyped pick no longer costs you six hours**: Three fixes to the GitHub memory lane, the one that reads the profile, repositories, and READMEs you tick and distills them into what your agent knows about your work. First: writing or deleting those memories now requires the one-time token the site attaches to your own actions, so another site cannot make your browser re-seed or wipe an agent behind your back. Every neighbouring memory action already worked this way; this one did not. Second: seeding is allowed once every six hours per agent, and that window used to be spent by attempts that never read anything, so ticking nothing and pressing Seed, or picking a repository that had been renamed since the list loaded, locked you out for six hours over a correctable mistake. The window is now taken only once your selection checks out, immediately before anything is actually read. Third: when every model provider is busy at once, the seed used to fail with a bare internal error and a support reference; it now says plainly that nothing was read, that your existing memories are untouched, and roughly how long until you can try again. (`/docs/github-memory-seeding`) `[security, fix]`- **Self-hosting docs no longer hand you a command that wipes your environment**: The deployment guide told self-hosters to set Cloud Run environment variables with `gcloud run services update --set-env-vars`. That flag replaces the service environment wholesale, so following the instruction for a single key silently deletes every other variable the service had. The guide now uses `--update-env-vars` and says plainly why. Four more corrections landed in the same sweep across the deployment, configuration and contributing pages: the Avaturn signup link and the GitHub Discussions links were dead (Discussions are not enabled on the repository, so bug reports and design questions both go to Issues); the in-browser avatar builder was documented as needing its own hosted origin in production when the normal build already serves it same-origin at /avatar-studio; and three counts that had drifted from the code (cron jobs, MCP server packages, contract tests) were replaced with pointers to the files that hold the real numbers. (`/docs/deployment`) `[docs, fix]`- **Sending $THREE from the wallet works, and swaps stopped failing outright**: Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error. `[fix]`+- **Solana Vanity Wallet: one footer, a working toast, and the gift fee actually shows up**: The sealed-gift composer opened with "Loading pricing…" and, depending on which finished first, could sit on that line forever: the translation pass reapplied the placeholder over the fee the page had already fetched, so nobody learned what a gift costs. The same collision could wipe the grind time estimate. Both now hold their own text. Confirmation toasts ("Claim link copied", "Funds reclaimed") were built with one class name and styled under another, so instead of floating over the page they dropped in as unstyled text at the very bottom, out of sight; that applies to the gift claim page too. Assigning a freshly ground wallet to an agent succeeded on the server and then reported "Network error" anyway, because the success message referenced an address it could not see. The page also shipped two footers stacked on top of each other, one of them a stale copy with broken markup and a Docs button wearing the X logo; the duplicate is gone. Rounding it out: the sign-in prompt pointed at a legacy /login.html URL, the gift form fields had no labels for screen readers, the expiry and asset choices now follow what the server actually accepts, keyboard focus is visible on every control (the text fields had their ring suppressed), buttons have press states, a failed agent list offers a retry instead of a raw error, and copying an address still works when the browser denies clipboard access. (`/vanity-wallet`) `[fix, improvement]`- **The 3D API and agent manifest references now match what the endpoints actually return**: The agent manifest page told you to validate a manifest with assertValid from @three-ws/avatar-schema. That package validates avatar manifests (mesh, skeleton, owner), not agent manifests, so the sample always threw. It now shows loadManifest from the published bundle, running against a live agent, and says plainly which document the avatar schema covers. On the 3D API page, the sample responses showed a model URL shape the service never returns, the inspect example was a stale capture of a model that has since been re-exported, and the Forge Pro tier table claimed draft and standard generations come back with no textures when every tier bakes them (1K, 2K, and 4K plus PBR at high). All three are corrected against live calls, and the page now explains why browser code should load a generated GLB through the first-party CDN path rather than the object store URL directly. The prompt art-director note is confirmed accurate and the code comment that contradicted it was fixed. (`/docs/3d-api`) `[fix, docs]`- **The 3D pipeline docs stop telling you to run a command that does not exist**: Every paid stage on the 3D asset pipeline page (rig, remesh, game-ready, stylize, background removal) showed you how to pay for it by running npx @x402/fetch. There is no such command: that package publishes a library, not a CLI, so anyone who copied a sample got a could-not-determine-executable error and no asset. The samples are now the real thing: an unpaid curl that returns the live 402 challenge and costs nothing, plus one Node snippet that wraps fetch with our published @three-ws/x402-fetch buyer and actually settles. The end-to-end generate, rig and game-ready walkthrough was rewritten the same way and now polls the forge job with the fields the API really returns. The page also stops promising a specific settlement network, because the 402 challenge names the networks itself. Alongside it: the changelog page CDN pinning table listed four alias URLs that all 404 and pointed at an integrity file for a version that no longer publishes one; the AgenC page opening sentence linked the word AgenC to a different protocol page; and the vanity protocol spec showed a stale copy of the service key document, which now matches what the live endpoint serves. (`/docs/3d-pipeline`) `[docs, fix]`- **The AgenC task room explains itself now, instead of showing a wall of raw error text**: The task room renders every task a wallet has posted on the AgenC coordination protocol as a 3D agent driven by its live on-chain state. It has been rebuilt around the moments where it used to leave you stuck. An unreadable wallet address, a Solana outage, and a dropped connection all used to print the raw server reply into an otherwise empty page; each now gets its own explanation, a Retry button, and a link to the docs on posting a task, and the room keeps retrying by itself when the fault is upstream and stops when it is something only you can fix. A wallet with no tasks says so and offers to check the other cluster instead of leaving you guessing. While a load is in flight you get skeleton cards rather than the word loading, and a line above the grid tells you how many tasks are showing, on which cluster, and when they were last refreshed. Card status colors now match the states the chain actually reports, so a task in progress or awaiting validation is no longer left uncolored, and each card links to its account on Solana Explorer. On a phone the wallet field no longer runs off the edge of the screen, the title no longer sits under the site logo, both form fields are labelled for screen readers, and every control has a visible focus ring. The room also stops running a 3D viewer for every card at once: avatars load as their cards come into view, up to eight at a time, and are released when you scroll past, which keeps a large board from stalling the browser and stops off-screen cards polling the chain for nothing. (`/agenc/room`) `[improvement, fix]`diff --git a/data/changelog.json b/data/changelog.jsonindex 93c8d773c..2ee99ff88 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -22956,6 +22956,26 @@"fix"],"link": "/claim-wallet"+ },+ {+ "date": "2026-08-15",+ "title": "Premium Vanity Inventory shows the whole shelf, and is readable in light mode",+ "summary": "The premium vanity shelf listed only the first hundred pre-ground addresses out of the hundreds actually in stock, with nothing on the page saying so: every address past that point was unbuyable because no one could see it. The page now loads sixty at a time, states plainly how many of the total you are looking at, and pages through the rest on demand. In light mode the page was close to unusable, because the addresses themselves, the buy dialog, and the custody notice were all painted in colours meant for the black background; the whole page now switches palette properly. Four smaller fixes shipped with it: the retry button on a failed load rendered as raw browser chrome and threw away your filter, so it is now a real button that simply re-runs the search you had; filtering down to no matches now offers a one-click way to clear the filter instead of just suggesting it; the word x402 in the intro linked to the vanity gallery rather than the x402 page; and keyboard users get a visible focus ring on the search and sort controls, which previously had theirs suppressed.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/vanity/premium"+ },+ {+ "date": "2026-08-15",+ "title": "Solana Vanity Wallet: one footer, a working toast, and the gift fee actually shows up",+ "summary": "The sealed-gift composer opened with \"Loading pricing…\" and, depending on which finished first, could sit on that line forever: the translation pass reapplied the placeholder over the fee the page had already fetched, so nobody learned what a gift costs. The same collision could wipe the grind time estimate. Both now hold their own text. Confirmation toasts (\"Claim link copied\", \"Funds reclaimed\") were built with one class name and styled under another, so instead of floating over the page they dropped in as unstyled text at the very bottom, out of sight; that applies to the gift claim page too. Assigning a freshly ground wallet to an agent succeeded on the server and then reported \"Network error\" anyway, because the success message referenced an address it could not see. The page also shipped two footers stacked on top of each other, one of them a stale copy with broken markup and a Docs button wearing the X logo; the duplicate is gone. Rounding it out: the sign-in prompt pointed at a legacy /login.html URL, the gift form fields had no labels for screen readers, the expiry and asset choices now follow what the server actually accepts, keyboard focus is visible on every control (the text fields had their ring suppressed), buttons have press states, a failed agent list offers a retry instead of a raw error, and copying an address still works when the browser denies clipboard access.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/vanity-wallet"}]}diff --git a/prompts/swarm-100/route-vault.md b/prompts/swarm-100/route-vault.mddeleted file mode 100644index a78a573f3..000000000--- a/prompts/swarm-100/route-vault.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /vault (Vault: Buy & Unlock Encrypted 3D Models on BNB 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==='/vault')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/vault" 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/vault--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: /vault ("Vault: Buy & Unlock Encrypted 3D Models on BNB Chain", section "crypto").-Declared purpose: Browse encrypted 3D listings, buy access with a real BSC testnet transaction, watch the cross-chain Greenfield permission grant settle, then unlock and view the model: decrypted entirely client-side, the raw key never leaves your browser.--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/vault. 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 /vault: 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-vault.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/prompts/swarm-100/route-world-lines.md b/prompts/swarm-100/route-world-lines.mddeleted file mode 100644index bf434bdd2..000000000--- a/prompts/swarm-100/route-world-lines.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /world-lines (World Lines: agent proof-of-presence quests)--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==='/world-lines')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/world-lines" 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/world-lines--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: /world-lines ("World Lines: agent proof-of-presence quests", section "main").-Declared purpose: Walk to an AI agent's real-world spot, complete its AR challenge, and earn a cryptographically real, agent-signed proof of presence. Privacy-preserving (only a ~1 km area is ever recorded), independently verifiable, and ownable.--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/world-lines. 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 /world-lines: 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-world-lines.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 637b59911..1746b1dbc 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-15T19:26:15.723Z",+ "generated_at": "2026-08-15T19:33:01.845Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -338,6 +338,17 @@"security"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Premium Vanity Inventory shows the whole shelf, and is readable in light mode",+ "summary": "The premium vanity shelf listed only the first hundred pre-ground addresses out of the hundreds actually in stock, with nothing on the page saying so: every address past that point was unbuyable because no one could see it. The page now loads sixty at a time, states plainly how many of the total you are looking at, and pages through the rest on demand. In light mode the page was close to unusable, because the addresses themselves, the buy dialog, and the custody notice were all painted in colours meant for the black background; the whole page now switches palette properly. Four smaller fixes shipped with it: the retry button on a failed load rendered as raw browser chrome and threw away your filter, so it is now a real button that simply re-runs the search you had; filtering down to no matches now offers a one-click way to clear the filter instead of just suggesting it; the word x402 in the intro linked to the vanity gallery rather than the x402 page; and keyboard users get a visible focus ring on the search and sort controls, which previously had theirs suppressed.",+ "link": "/vanity/premium",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",@@ -435,6 +446,17 @@"fix"]},+ {+ "date": "2026-08-15",+ "type": "update",+ "title": "Solana Vanity Wallet: one footer, a working toast, and the gift fee actually shows up",+ "summary": "The sealed-gift composer opened with \"Loading pricing…\" and, depending on which finished first, could sit on that line forever: the translation pass reapplied the placeholder over the fee the page had already fetched, so nobody learned what a gift costs. The same collision could wipe the grind time estimate. Both now hold their own text. Confirmation toasts (\"Claim link copied\", \"Funds reclaimed\") were built with one class name and styled under another, so instead of floating over the page they dropped in as unstyled text at the very bottom, out of sight; that applies to the gift claim page too. Assigning a freshly ground wallet to an agent succeeded on the server and then reported \"Network error\" anyway, because the success message referenced an address it could not see. The page also shipped two footers stacked on top of each other, one of them a stale copy with broken markup and a Docs button wearing the X logo; the duplicate is gone. Rounding it out: the sign-in prompt pointed at a legacy /login.html URL, the gift form fields had no labels for screen readers, the expiry and asset choices now follow what the server actually accepts, keyboard focus is visible on every control (the text fields had their ring suppressed), buttons have press states, a failed agent list offers a retry instead of a raw error, and copying an address still works when the browser denies clipboard access.",+ "link": "/vanity-wallet",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-15","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 9275698f9..475a4eeea 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -254,6 +254,14 @@<category>fix</category><description>Asking the public avatar renderer for a pose returned a T-pose on most models: it matched bone names against a short hand-written list, and any rig that did not use those exact names (including every Mixamo export) was silently left in its bind pose while the response still claimed the pose had been applied. The renderer now uses the same posing engine the pose studio uses, so a preset now lands whatever naming convention the model's skeleton uses, and the camera frames the posed figure rather than the unposed one. The background colour on both public renderers is now checked before it is used, and the per-render budget is counted across the whole fleet instead of per server.</description></item>+ <item>+ <title>Premium Vanity Inventory shows the whole shelf, and is readable in light mode</title>+ <link>https://three.ws/vanity/premium</link>+ <guid isPermaLink="false">2026-08-15:Premium Vanity Inventory shows the whole shelf, and is readable in light mode</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The premium vanity shelf listed only the first hundred pre-ground addresses out of the hundreds actually in stock, with nothing on the page saying so: every address past that point was unbuyable because no one could see it. The page now loads sixty at a time, states plainly how many of the total you are looking at, and pages through the rest on demand. In light mode the page was close to unusable, because the addresses themselves, the buy dialog, and the custody notice were all painted in colours meant for the black background; the whole page now switches palette properly. Four smaller fixes shipped with it: the retry button on a failed load rendered as raw browser chrome and threw away your filter, so it is now a real button that simply re-runs the search you had; filtering down to no matches now offers a one-click way to clear the filter instead of just suggesting it; the word x402 in the intro linked to the vanity gallery rather than the x402 page; and keyboard users get a visible focus ring on the search and sort controls, which previously had theirs suppressed.</description>+ </item><item><title>Private avatars no longer show their picture in registry lookups</title><link>https://three.ws/changelog</link>@@ -326,6 +334,14 @@<category>fix</category><description>Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error.</description></item>+ <item>+ <title>Solana Vanity Wallet: one footer, a working toast, and the gift fee actually shows up</title>+ <link>https://three.ws/vanity-wallet</link>+ <guid isPermaLink="false">2026-08-15:Solana Vanity Wallet: one footer, a working toast, and the gift fee actually shows up</guid>+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The sealed-gift composer opened with "Loading pricing…" and, depending on which finished first, could sit on that line forever: the translation pass reapplied the placeholder over the fee the page had already fetched, so nobody learned what a gift costs. The same collision could wipe the grind time estimate. Both now hold their own text. Confirmation toasts ("Claim link copied", "Funds reclaimed") were built with one class name and styled under another, so instead of floating over the page they dropped in as unstyled text at the very bottom, out of sight; that applies to the gift claim page too. Assigning a freshly ground wallet to an agent succeeded on the server and then reported "Network error" anyway, because the success message referenced an address it could not see. The page also shipped two footers stacked on top of each other, one of them a stale copy with broken markup and a Docs button wearing the X logo; the duplicate is gone. Rounding it out: the sign-in prompt pointed at a legacy /login.html URL, the gift form fields had no labels for screen readers, the expiry and asset choices now follow what the server actually accepts, keyboard focus is visible on every control (the text fields had their ring suppressed), buttons have press states, a failed agent list offers a retry instead of a raw error, and copying an address still works when the browser denies clipboard access.</description>+ </item><item><title>The 3D API and agent manifest references now match what the endpoints actually return</title><link>https://three.ws/docs/3d-api</link>diff --git a/public/features.json b/public/features.jsonindex 8739aeead..c66119210 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-15T19:26:15.578Z",+ "generated_at": "2026-08-15T19:33:01.708Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",