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
docs(changelog): announce the ChatGPT and AR doc corrections, and retire the finished work order
nirholas48c303168575
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex b7e447290..37a808218 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,11 +7,17 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-08- **A GPU waking up now says so, instead of looking like a stuck progress bar**: Some of our 3D engines release their graphics card when nobody is using them, so the first request of a quiet spell has to boot one back up before any sculpting starts. That wait is normal and it ends, but several surfaces showed nothing but a spinning step while it happened, which reads as a hang. Now every place you can watch a model being built names it: the homepage forge, the Studio, the in-world item forge on /play, and the tools other apps drive us through all say a GPU is waking, how much of the boot is left, and that your job is already accepted and starts the second the worker answers. Every number comes from the generator itself, so nothing is a guessed timer. Two related fixes came out of it: the elapsed counter on /forge now reports how long your job has really been running rather than how long the tab has been open, so reopening the page mid-build no longer restarts the clock at zero; and the countdown now uses each engine's real boot budget instead of an estimate. The keep-warm schedule that holds those engines open during busy hours was also missing our highest-quality lane, which has the longest boot of the fleet. (`/forge`) `[improvement, fix]`+- **Agent Galaxy no longer strands you when the star map cannot be built**: When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link. (`/galaxy`) `[fix, improvement]`- **Avatars keep their real skin, eyes and hair, and we can prove it on a phone**: Every avatar the platform loads gets its skin, eyes, hair and teeth re-shaded with real-world material values the moment it appears: skin at the roughness bare skin actually has with a warm scattering layer, a wet cornea that catches a highlight, and hair that reads as strands rather than a helmet. That pass was already running, but the check meant to prove it was pointed at the wrong page and had been quietly reporting nothing at all, so it could not have caught the day it broke. It now runs against the same embed page your visitors see, at phone, tablet and desktop widths, and records exactly which materials it upgraded and to what values. Alongside it, a new check loads a full 4K-textured model on an emulated iPhone and Android phone over a slow mobile connection and measures the real bytes and load time, so a model that would not open on a phone is caught before it ships rather than after. `[improvement, infra]`- **Buttons that looked dead now respond, and the whole site paints from one palette**: A consistency pass across the platform. Fifty controls set the clickable cursor but had no hover styling at all, so the pointer changed shape and the button did not, which made working controls read as broken; the marketplace, Widget Studio, the brain workspace, the pump dashboard, agent detail and the on-chain deploy panel now all answer under the pointer, on the same timing. The retry buttons on an agent page were the worst case, because they only appear after something already failed. Separately, 73 colours were still typed in by hand across 24 stylesheets instead of coming from the shared palette, which is why a handful of panels stayed dark when you switched to the light theme and why some captions drifted a shade off everywhere else; they now all read from one source. Eight standalone pages that had quietly grown their own private palette (the demos, Widget Studio, the dashboard sub-pages, the print insert, agent detail) were folded back onto the shared one, so they also pick up the site-wide keyboard focus ring and the reduced-motion setting for the first time. Two new checks keep both from creeping back. (`/marketplace`) `[improvement, fix]`- **Forge tells you when uploads are down, instead of blaming your connection**: Adding a photo on the Forge could fail with "Network error during upload" when nothing was wrong with your network or your photo. Our asset storage had stopped accepting our credential, but the page had no way to know that: the browser is handed a short-lived upload address and sends the image straight to storage, and when storage refuses, the refusal comes back without the header a browser needs in order to show the page what happened. So a platform outage arrived looking exactly like a bad phone signal, and Retry could never fix it. The page now checks that storage will actually accept an upload before handing one out, and says so plainly when it will not, so you can tell "come back in a few minutes" apart from "try a different photo". The same fix covers the Forge Studio and 3D print upload paths. (`/forge`) `[fix]`+- **Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch**: Launch Studio, the catalog of 50 coin-launch recipes, was written entirely in white text and never flipped for the light theme, so on a light background its title, its recipe cards and its preview drawer were white on white with a dark strip painted across the top. The whole surface now draws from the site's colour system and reads in both themes. The bigger fix sits behind the Launch this coin button: every reward recipe promises that a coin's creator fees route to its subject, and that choice was being dropped the moment you left the studio, so the launch form opened with no recipient at all. The routing now travels with the coin, shows on the launch form before you mint, and opens the fee split pre-filled with that recipient the moment the coin is live, ready to review and sign. Two planner options no launch could ever apply were removed rather than left promising a payout. The preview drawer also behaves as a real dialog now: focus moves into it, Tab stays inside it, and closing it returns you to the card you opened. (`/launch-studio`) `[fix, improvement]`- **Robinhood Portfolios can now show you what a basket would have done, and what the rebalancing did to it**: Every generated portfolio now comes with a backtest, and it runs the basket twice: once rebalanced on the schedule it published, and once left alone. The gap between those two lines is the whole reason to pick one schedule over another, and it goes both ways, since rebalancing quietly harvests the swings in a basket whose holdings move against each other and quietly gives up gains in one where a single holding keeps winning. Coverage is stated rather than glossed over: a holding with no price history is named and left out, the window shown is only the stretch where every remaining holding has real observations, and nothing is filled in to close a gap. Getting that history at all took some doing, because this chain keeps no price archive and produces about 864,000 blocks a day, so reading a month of prices back off the chain is not something a page can do while you wait. Tokenized stocks are covered from their price feeds going back weeks, and a nightly snapshot now records the whole market so coverage keeps growing for everything else, memecoins included. Sharing a portfolio also got fixed: a link now carries the portfolio itself rather than the sentence that produced it, so what you send is exactly what the other person opens, where before the wording was re-run and could quietly come back as a different basket. There is a new endpoint for checking that a portfolio document really is the one a portfolio was published under, and a client library for developers who want the market, the generator, the backtest and that check from their own code. Along the way two data bugs were fixed that were quietly under-reporting the market: the tokenized-stock board had been describing only a couple of tokens per batch instead of all thirty, and the price-history reads had been silently returning less history the more of it you asked for. (`/markets/robinhood/portfolios`) `[feature, improvement]`+- **Text to 3D no longer stops when our image storage does**: Turning a written prompt into a model takes one step you never see: we paint a reference picture of what you asked for, save it somewhere our sculpting engines can read, and hand them the link. If that save failed, the whole thing was over before a graphics card was ever asked for anything, and the error you got back was our storage provider's own wording about signatures and access keys, which told you nothing you could act on. Making a model from a photo you upload was unaffected, because it brings its own picture, so half the feature could look perfectly healthy while the other half was completely down. Our own engines never needed that saved copy: they accept the picture itself, sent along with the request. So when storage will not take the write, the reference view now travels inside the job and your model still gets built. The engines that genuinely need a link, the outside ones you can pick by name, now say so in plain language and point you at the ones still running, instead of failing with a message about our secret keys. Generations that take this route lose the extra angles we normally paint to fill in a subject's back, so they are built from the single front view. (`/forge`) `[fix, improvement]`+- **The Agent Economy page is readable on a phone, and its x402 services finally have names**: On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled "Service", the price sat next to a raw token contract address, and the network read "eip155:8453" instead of "Base". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of "40+". (`/economy`) `[fix, improvement]`+- **The ChatGPT and AR docs now describe the AR launcher that actually runs**: Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation. (`/docs/ar`) `[docs, fix]`- **The club now takes $THREE at the door and at the stage, not just USDC**: The club has always advertised two ways to pay: USDC or $THREE, on Solana, for both the cover charge and every dance tip. Only one of them was reachable. The checkout window picked the first token a service offered and gave you no way to choose the other, so $THREE was quoted on every paid page and payable on none of them. Across every club tip ever settled, not one was paid in $THREE, which is what you would expect from a menu with a hidden second item. The checkout now shows a token picker whenever a service quotes more than one, with each token's real price on it, so you can compare 0.001 USDC against its $THREE equivalent before you approve anything, and the price at the top of the window follows what you pick. If you have agent wallets, they still pay in USDC only, and the window now says so instead of quietly hiding them when you switch tokens. Two settlement bugs behind the door were fixed at the same time. The first would have hit the very first person to pay in $THREE: sending a token to a wallet that has never held it requires opening an account for it on-chain, and the check that decides whether we can afford to sponsor a payment was ignoring that cost, so the payment would have been accepted and then failed on-chain for a reason that looked like something else entirely. The second was making the club look open when it was not: a healthy payer covering their own fees could reset a shared 'we can still sponsor payments' flag that belonged to a different wallet, so the door kept quoting prices it could not actually take. Finally, when payments are paused because the wallet that settles them needs topping up, the checkout now says that in a sentence and tells you nothing was charged, instead of showing you the raw error envelope it used to paste in, which read like a broken link. (`/club`) `[fix, improvement]`+- **The Launch a Coin button now works once you have filled the form**: On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read "Add name, symbol & description to launch" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into "Connect wallet to launch" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges. (`/launch`) `[fix, improvement]`## 2026-09-07diff --git a/data/changelog.json b/data/changelog.jsonindex b5d69d62e..1e5585871 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,20 @@{"$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-09-08",+ "title": "The ChatGPT and AR docs now describe the AR launcher that actually runs",+ "summary": "Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.",+ "tags": ["docs", "fix"],+ "link": "/docs/ar"+ },+ {+ "date": "2026-09-08",+ "title": "The Launch a Coin button now works once you have filled the form",+ "summary": "On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read \"Add name, symbol & description to launch\" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into \"Connect wallet to launch\" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.",+ "tags": ["fix", "improvement"],+ "link": "/launch"+ },{"date": "2026-09-08","title": "Text to 3D no longer stops when our image storage does",diff --git a/prompts/finish/014-openai-pr-06-docs-accuracy-reconciliation.md b/prompts/finish/014-openai-pr-06-docs-accuracy-reconciliation.mddeleted file mode 100644index d7c5692f2..000000000--- a/prompts/finish/014-openai-pr-06-docs-accuracy-reconciliation.md+++ /dev/null@@ -1,94 +0,0 @@-# Task 06: Fix doc accuracy and reconcile the tool-count story (P1)--Read [`openai-pr-00-START-HERE.md`](_context/openai-pr-00-START-HERE.md) first. This task cleans up the-documentation drift the audit found, EXCEPT the two docs owned by other tasks-(`apps-sdk/README.md` was Task 01, already landed on 2026-07-18; the `forge_free` tier-claim is Task 03). Do not fight those tasks for those specific edits; coordinate.--## The problems (verified)--1. **Tool-count inconsistency.** The free MCP connector exposes **9** tools: 6- generation (`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`,- `forge_avatar`, `refine_model`) + 3 persona (`create_agent_persona`,- `get_agent_persona`, `persona_say`). But docs tell different stories:- - `openai-submission.md` says "Nine tools."- - `docs/mcp-studio.md` headline tool table lists six, with the persona tools in a- later "Embodiment" section.- - Code comments drift: `tools.js:1-8` says "Six generation tools (five generators +- refine_model)"; `tests/mcp-studio.test.js` comment says "five allowed generation- tools" while the asserted array has six.- Reconcile these so every count is consistent and correct. The authoritative number- is whatever the running server returns from `tools/list`; verify it, then make all- docs and comments match.--2. **model-viewer version is not single-sourced.** Three surfaces load different- `model-viewer` versions: `api/ar.js` launch page (3.5.0 via jsdelivr), the MCP- widget in `component.js` (3.5.0), and `/viewer.html` (4.0.0). Pick one version,- pin it in one place they all reference (a constant/shared import), or at minimum- document the intended version per surface and why they differ. A reviewer opening- two of our surfaces should not get two different renderer versions with no reason.--3. **`docs/mcp-studio.md` cross-reference check.** It points the custom-GPT contract to- `./api-reference.md`. Verify that file exists and actually documents `/api/3d/studio`.- If not, fix the pointer to the authoritative schema (the served OpenAPI from Task 05)- or add the missing section. No dead doc links.--4. **General accuracy sweep of the ChatGPT-surface docs.** Read- `docs/mcp-studio.md`, `docs/chatgpt-ar.md`, `docs/mcp-3d-studio.md`, and- `docs/ar.md` end to end against the code. Every `ui://` URI, file path, endpoint,- env var, and example must resolve and be correct. Fix any that are stale. The audit- already confirmed `docs/chatgpt-ar.md` correctly points at `component.js` (good) and- that `apps-sdk/README.md` was the worst offender; Task 01 rewrote it on 2026-07-18,- so treat it as correct unless a link in it stops resolving.--## Constraints--- Every rule in `openai-pr-00-START-HERE.md`. Docs are real implementations: every code sample- must run, every link must resolve to a live path (`CLAUDE.md` documentation rules).-- Not a crypto surface; commit gate does not apply. Do not introduce any non-$THREE- coin reference into the docs.-- Coordinate: `apps-sdk/README.md` was rewritten by Task 01 (landed) and is accurate;- leave the `forge_free` tier language to Task 03. If Task 03 has not landed yet, note- the dependency rather than duplicating its edits.--## Verification--- Start from the live `tools/list` output (call `/api/mcp-studio` with an- `initialize` + `tools/list` JSON-RPC batch) and confirm the count and names, then- grep every doc/comment for tool counts and confirm they match.-- `grep -rn "model-viewer@" api public docs` shows a single intended version story.-- Every internal doc link resolves (spot-check with a link checker or by opening each- referenced path).-- `npm test` green (docs changes should not break tests, but run it).--## Definition of done--- [ ] Tool count is consistent and correct (9) across `openai-submission.md`,- `docs/mcp-studio.md`, code comments, and test comments.-- [ ] model-viewer version is single-sourced or its per-surface difference is- documented and justified.-- [ ] `docs/mcp-studio.md` cross-references resolve; no dead links in any- ChatGPT-surface doc.-- [ ] All ChatGPT-surface docs are accurate against the code (paths, URIs, endpoints,- env vars, examples).-- [ ] `data/changelog.json` entry with the `docs` tag.-- [ ] `npm test` green.--## Retire this prompt when it is done (required)--1. Verify every Definition of done line against actual command output in front- of you. Never claim a line you did not verify.-2. Record the outcome in this campaign's PROGRESS or INDEX file if it has one.-3. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares), and delete this- prompt file in that same commit:-- git rm prompts/finish/014-openai-pr-06-docs-accuracy-reconciliation.md-- A finished order left on disk reads as open work to the next agent, so the- shrinking directory is the campaign's progress ledger.--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/finish/_context/openai-pr-00-START-HERE.md b/prompts/finish/_context/openai-pr-00-START-HERE.mdindex 90ba78170..b6eb3aed1 100644--- a/prompts/finish/_context/openai-pr-00-START-HERE.md+++ b/prompts/finish/_context/openai-pr-00-START-HERE.md@@ -42,15 +42,15 @@ git history (`git log --diff-filter=D -- docs/openai-pr/`). What each closed:| 03 | `forge_free` tier story true everywhere | `api/_mcp-studio/tools.js` defaults to `standard`; the live tool description, the answer sheet and `forge-free-tier-evidence.json` agree || 04 | Test coverage on the ChatGPT-facing surface | `tests/api/ar-endpoint.test.js` (20), `tests/api/embodiment-embed-page.test.js` (7), `tests/api/3d-studio-actions-contract.test.js`, `tests/e2e/embodiment-embed.spec.js` (6); production `/api/ar` matches per user agent || 05 | Custom-GPT OpenAPI served, legal URLs aligned | `https://three.ws/.well-known/3d-studio-openapi.yaml` 200, two paths, `security: []`, Redocly lint clean; `/legal/privacy` and `/legal/tos` 200 |+| 06 | Doc accuracy + the tool-count story | Count reconciled at **eleven** everywhere (live `tools/list`, `docs/mcp-studio.md`, `openai-submission.md`, `TRACKER.md`, the `/openai` page, the partnership brief, `tools.js`, `tests/mcp-studio.test.js`, which pins it); model-viewer single-sourced at 4.0.0 across 110 references in 94 files with `check:model-viewer` tightened to catch semver RANGES; every link, path, `ui://` URI, env var and sample in the four ChatGPT-surface docs verified against live |Open:-| # | Brief | Priority | State (measured 2026-09-01) |+| # | Brief | Priority | State (measured 2026-09-08) || --- | --- | --- | --- |-| 06 | [Fix doc accuracy and reconcile the tool-count story](../014-openai-pr-06-docs-accuracy-reconciliation.md) | P1 | Partial. The 2026-08-06 reconciliation shipped and `docs/mcp-studio.md` says eleven, but `api/_mcp-studio/tools.js:3`, `openai-submission.md`, `live-tools-list.json`, `TRACKER.md`, the `/openai` page copy and its locale key, and the partnership brief still say ten or nine. || 07 | [Final live verification and submit checklist](../915-openai-pr-07-final-verification-and-submit.md) | P2 (runs last) | Never run. Its "exactly 10 tools" check must read 11; `initialize`, `tools/list`, `resources/list`, the served manifests and `/api/ar` pass today; the live `forge_free` and `POST /api/3d/studio` runs and the kit refresh remain. |-Run 06 first, then 07. The human steps at the end of 07 (partner-portal submit, deleting the+07 is the last brief. The human steps at its end (partner-portal submit, deleting thedraft GPT) stay with the owner.## Rules every task must follow (from `CLAUDE.md`)diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 3789eee18..fae4ed8ca 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-08T17:19:34.218Z",+ "generated_at": "2026-09-08T17:31:12.489Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3551,+ "total": 3557,"complete": false,"full_feed": "/changelog.json","entries": [@@ -20,6 +20,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Agent Galaxy no longer strands you when the star map cannot be built",+ "summary": "When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link.",+ "link": "/galaxy",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -52,6 +63,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch",+ "summary": "Launch Studio, the catalog of 50 coin-launch recipes, was written entirely in white text and never flipped for the light theme, so on a light background its title, its recipe cards and its preview drawer were white on white with a dark strip painted across the top. The whole surface now draws from the site's colour system and reads in both themes. The bigger fix sits behind the Launch this coin button: every reward recipe promises that a coin's creator fees route to its subject, and that choice was being dropped the moment you left the studio, so the launch form opened with no recipient at all. The routing now travels with the coin, shows on the launch form before you mint, and opens the fee split pre-filled with that recipient the moment the coin is live, ready to review and sign. Two planner options no launch could ever apply were removed rather than left promising a payout. The preview drawer also behaves as a real dialog now: focus moves into it, Tab stays inside it, and closing it returns you to the card you opened.",+ "link": "/launch-studio",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -63,6 +85,39 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Text to 3D no longer stops when our image storage does",+ "summary": "Turning a written prompt into a model takes one step you never see: we paint a reference picture of what you asked for, save it somewhere our sculpting engines can read, and hand them the link. If that save failed, the whole thing was over before a graphics card was ever asked for anything, and the error you got back was our storage provider's own wording about signatures and access keys, which told you nothing you could act on. Making a model from a photo you upload was unaffected, because it brings its own picture, so half the feature could look perfectly healthy while the other half was completely down. Our own engines never needed that saved copy: they accept the picture itself, sent along with the request. So when storage will not take the write, the reference view now travels inside the job and your model still gets built. The engines that genuinely need a link, the outside ones you can pick by name, now say so in plain language and point you at the ones still running, instead of failing with a message about our secret keys. Generations that take this route lose the extra angles we normally paint to fill in a subject's back, so they are built from the single front view.",+ "link": "/forge",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Agent Economy page is readable on a phone, and its x402 services finally have names",+ "summary": "On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled \"Service\", the price sat next to a raw token contract address, and the network read \"eip155:8453\" instead of \"Base\". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of \"40+\".",+ "link": "/economy",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The ChatGPT and AR docs now describe the AR launcher that actually runs",+ "summary": "Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.",+ "link": "/docs/ar",+ "tags": [+ "docs",+ "fix"+ ]+ },{"date": "2026-09-08","type": "update",@@ -74,6 +129,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Launch a Coin button now works once you have filled the form",+ "summary": "On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read \"Add name, symbol & description to launch\" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into \"Connect wallet to launch\" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.",+ "link": "/launch",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-07","type": "launch",@@ -1536,70 +1602,6 @@"improvement","fix"]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The Showcase directory is back after a stray change emptied it",- "summary": "Showcase lists every ERC-8004 agent that carries a 3D body, discovered across 22 chains and indexed from the canonical registries, and any card opens that agent in the live viewer. An unrelated change had emptied the file behind it, so for a while the page loaded and then showed nothing at all. It is restored and browsing again. While it was open we also gave the page a single real heading instead of two competing ones, which matters to anyone reading the site with a screen reader, and rewrote its description, which had been advertising a drag-and-drop model viewer rather than the agent directory it actually is.",- "link": "/showcase",- "tags": [- "fix"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The signal marketplace tells you how to get on it, and reads correctly to a screen reader",- "summary": "No verified trader has published a paid feed yet, so the marketplace's empty state is what everyone actually sees, and it only pointed at the leaderboard. It now also points at the place you publish from: the Signals tab of your agent wallet. The rank and network filters used to announce themselves as tabs, which promises a screen-reader user a panel to arrow between that this page does not have; they are now announced as the pressed toggles they really are, wired to the board they re-rank. The Retry button on a failed load and both empty-state buttons had no hover or keyboard-focus styling at all, so a keyboard user could not see where they were; all three now light up on hover and show a focus ring. Landing on the page with a stale or misspelled sort in the address bar rewrites it to the board you are actually looking at, so a shared link always opens the view it names. And a feed link that no longer resolves now gets a real page heading instead of a floating error message.",- "link": "/signals",- "tags": [- "improvement",- "fix"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The sniper scoreboard reads correctly in the light theme, and tells you what it is doing while it loads",- "summary": "The strategy board was building a second copy of its own stylesheet in JavaScript and appending it to the page, so those rules won every tie and quietly reverted the real one. In the light theme that meant profit figures and the LLM badges rendered in a near-white green and lavender on white paper, close to invisible; they now use the same colours as every other crypto page and read properly in both themes. Loading is no longer a blank space under the headline: the board paints a skeleton in the exact shape of the table while it reads each agent's live wallet balance off the chain. If the feed cannot be reached you now get a plain sentence about what went wrong plus a button to try again, instead of a raw browser error and a silent 30-second wait, and a refresh that fails on top of a board that already has numbers keeps the numbers, says they are the last good read, and offers the same retry. Switching the time window while a slower request is still in flight can no longer paint the wrong window's figures. The judgment ledger says so when there are no LLM verdicts in the window rather than disappearing. And the table stopped showing a hand cursor over rows and headers that were never clickable or sortable.",- "link": "/sniper/experiments",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The splat viewer lets go of the graphics card between scenes",- "summary": "Every scene the viewer opened built a fresh WebGL renderer, and tearing the old one down freed its memory but never released the graphics context itself. The library we use for splat rendering ends its own cleanup by removing an element from the page that was never there, which throws and skips the last of its teardown, so the contexts stacked up across a session of opening one capture after another. The viewer now releases each context by hand on every swap and when you leave the page. Recentering the camera no longer rebuilds the whole scene either: it moves the camera on the running viewer, so the stage snaps back instantly instead of flashing through the loading screen. If the browser does take the graphics context back, after a GPU reset or under memory pressure, the stage now says so and offers a way to reload rather than sitting on a frozen frame. Two smaller things while we were in there: a scene you opened by URL can be downloaded from the viewer, the same as an upload or a sample, and the drop zone now has a real button for keyboard users with a labelled URL field for screen readers.",- "link": "/splat",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The status page can tell one dark house from an outage",- "summary": "Connected homes now report on the public status page at /status, and the hard part was making that number honest. If your Home Assistant is switched off, your token expired or your internet dropped, that is your house: it shows up in your own home view, not as a three.ws outage and not as an alert to anyone. It takes at least ten homes failing at once before the platform will call it a problem on our side, because with three homes connected one holiday cottage losing power would look like a third of everything being broken. One thing is treated as an emergency at a count of one: an action that can open a building (a lock, a garage door, an alarm) recorded as having run without someone saying yes. That has no acceptable rate.",- "link": "/status",- "tags": [- "infra",- "improvement"- ]- },- {- "date": "2026-09-03",- "type": "update",- "title": "The tour atlas counts its stops correctly again",- "summary": "The atlas at /tour/atlas is the map of the guided tour: one card per stop, numbered in the order you would walk them. Two hundred and three of those cards were still carrying numbers from an older version of the tour, so the grid showed duplicate stop numbers, skipped others, and put cards out of order, under a heading that claimed one more stop than the grid actually held. Every card is now numbered by its real position in the tour and the count above the grid matches what is under it. Nothing about the stops themselves changed: same pages, same screenshots, same highlights.",- "link": "/tour/atlas",- "tags": [- "fix"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 0c1e5e18a..5cc611a2b 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-08T17:19:33.654Z",+ "generated_at": "2026-09-08T17:31:11.997Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -17,6 +17,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Agent Galaxy no longer strands you when the star map cannot be built",+ "summary": "When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link.",+ "link": "/galaxy",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -49,6 +60,17 @@"fix"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch",+ "summary": "Launch Studio, the catalog of 50 coin-launch recipes, was written entirely in white text and never flipped for the light theme, so on a light background its title, its recipe cards and its preview drawer were white on white with a dark strip painted across the top. The whole surface now draws from the site's colour system and reads in both themes. The bigger fix sits behind the Launch this coin button: every reward recipe promises that a coin's creator fees route to its subject, and that choice was being dropped the moment you left the studio, so the launch form opened with no recipient at all. The routing now travels with the coin, shows on the launch form before you mint, and opens the fee split pre-filled with that recipient the moment the coin is live, ready to review and sign. Two planner options no launch could ever apply were removed rather than left promising a payout. The preview drawer also behaves as a real dialog now: focus moves into it, Tab stays inside it, and closing it returns you to the card you opened.",+ "link": "/launch-studio",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-08","type": "update",@@ -60,6 +82,39 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "Text to 3D no longer stops when our image storage does",+ "summary": "Turning a written prompt into a model takes one step you never see: we paint a reference picture of what you asked for, save it somewhere our sculpting engines can read, and hand them the link. If that save failed, the whole thing was over before a graphics card was ever asked for anything, and the error you got back was our storage provider's own wording about signatures and access keys, which told you nothing you could act on. Making a model from a photo you upload was unaffected, because it brings its own picture, so half the feature could look perfectly healthy while the other half was completely down. Our own engines never needed that saved copy: they accept the picture itself, sent along with the request. So when storage will not take the write, the reference view now travels inside the job and your model still gets built. The engines that genuinely need a link, the outside ones you can pick by name, now say so in plain language and point you at the ones still running, instead of failing with a message about our secret keys. Generations that take this route lose the extra angles we normally paint to fill in a subject's back, so they are built from the single front view.",+ "link": "/forge",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Agent Economy page is readable on a phone, and its x402 services finally have names",+ "summary": "On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled \"Service\", the price sat next to a raw token contract address, and the network read \"eip155:8453\" instead of \"Base\". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of \"40+\".",+ "link": "/economy",+ "tags": [+ "fix",+ "improvement"+ ]+ },+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The ChatGPT and AR docs now describe the AR launcher that actually runs",+ "summary": "Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.",+ "link": "/docs/ar",+ "tags": [+ "docs",+ "fix"+ ]+ },{"date": "2026-09-08","type": "update",@@ -71,6 +126,17 @@"improvement"]},+ {+ "date": "2026-09-08",+ "type": "update",+ "title": "The Launch a Coin button now works once you have filled the form",+ "summary": "On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read \"Add name, symbol & description to launch\" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into \"Connect wallet to launch\" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.",+ "link": "/launch",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-07","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex 0a9e8fb6b..bf83f784a 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>improvement</category><description>Some of our 3D engines release their graphics card when nobody is using them, so the first request of a quiet spell has to boot one back up before any sculpting starts. That wait is normal and it ends, but several surfaces showed nothing but a spinning step while it happened, which reads as a hang. Now every place you can watch a model being built names it: the homepage forge, the Studio, the in-world item forge on /play, and the tools other apps drive us through all say a GPU is waking, how much of the boot is left, and that your job is already accepted and starts the second the worker answers. Every number comes from the generator itself, so nothing is a guessed timer. Two related fixes came out of it: the elapsed counter on /forge now reports how long your job has really been running rather than how long the tab has been open, so reopening the page mid-build no longer restarts the clock at zero; and the countdown now uses each engine's real boot budget instead of an estimate. The keep-warm schedule that holds those engines open during busy hours was also missing our highest-quality lane, which has the longest boot of the fleet.</description></item>+ <item>+ <title>Agent Galaxy no longer strands you when the star map cannot be built</title>+ <link>https://three.ws/galaxy</link>+ <guid isPermaLink="false">2026-09-08:Agent Galaxy no longer strands you when the star map cannot be built</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>When the embedding service behind the 3D agent map is unreachable, the page showed a sentence of explanation and nothing to click. It now offers the same agents as a browsable list plus a link to how the map is built. The keyboard experience was rebuilt too: every control on the page has a visible focus ring, and the search box and Money-Cam button drop out of the tab order while an overlay covers the map, so you can no longer tab into a search that has nothing to search. An agent card's Chat button now opens that agent's chat panel instead of repeating the View agent link.</description>+ </item><item><title>Avatars keep their real skin, eyes and hair, and we can prove it on a phone</title><link>https://three.ws/changelog</link>@@ -38,6 +46,14 @@<category>fix</category><description>Adding a photo on the Forge could fail with "Network error during upload" when nothing was wrong with your network or your photo. Our asset storage had stopped accepting our credential, but the page had no way to know that: the browser is handed a short-lived upload address and sends the image straight to storage, and when storage refuses, the refusal comes back without the header a browser needs in order to show the page what happened. So a platform outage arrived looking exactly like a bad phone signal, and Retry could never fix it. The page now checks that storage will actually accept an upload before handing one out, and says so plainly when it will not, so you can tell "come back in a few minutes" apart from "try a different photo". The same fix covers the Forge Studio and 3D print upload paths.</description></item>+ <item>+ <title>Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch</title>+ <link>https://three.ws/launch-studio</link>+ <guid isPermaLink="false">2026-09-08:Launch Studio reads in light mode, and a recipe's reward routing now reaches the launch</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Launch Studio, the catalog of 50 coin-launch recipes, was written entirely in white text and never flipped for the light theme, so on a light background its title, its recipe cards and its preview drawer were white on white with a dark strip painted across the top. The whole surface now draws from the site's colour system and reads in both themes. The bigger fix sits behind the Launch this coin button: every reward recipe promises that a coin's creator fees route to its subject, and that choice was being dropped the moment you left the studio, so the launch form opened with no recipient at all. The routing now travels with the coin, shows on the launch form before you mint, and opens the fee split pre-filled with that recipient the moment the coin is live, ready to review and sign. Two planner options no launch could ever apply were removed rather than left promising a payout. The preview drawer also behaves as a real dialog now: focus moves into it, Tab stays inside it, and closing it returns you to the card you opened.</description>+ </item><item><title>Robinhood Portfolios can now show you what a basket would have done, and what the rebalancing did to it</title><link>https://three.ws/markets/robinhood/portfolios</link>@@ -46,6 +62,30 @@<category>feature</category><description>Every generated portfolio now comes with a backtest, and it runs the basket twice: once rebalanced on the schedule it published, and once left alone. The gap between those two lines is the whole reason to pick one schedule over another, and it goes both ways, since rebalancing quietly harvests the swings in a basket whose holdings move against each other and quietly gives up gains in one where a single holding keeps winning. Coverage is stated rather than glossed over: a holding with no price history is named and left out, the window shown is only the stretch where every remaining holding has real observations, and nothing is filled in to close a gap. Getting that history at all took some doing, because this chain keeps no price archive and produces about 864,000 blocks a day, so reading a month of prices back off the chain is not something a page can do while you wait. Tokenized stocks are covered from their price feeds going back weeks, and a nightly snapshot now records the whole market so coverage keeps growing for everything else, memecoins included. Sharing a portfolio also got fixed: a link now carries the portfolio itself rather than the sentence that produced it, so what you send is exactly what the other person opens, where before the wording was re-run and could quietly come back as a different basket. There is a new endpoint for checking that a portfolio document really is the one a portfolio was published under, and a client library for developers who want the market, the generator, the backtest and that check from their own code. Along the way two data bugs were fixed that were quietly under-reporting the market: the tokenized-stock board had been describing only a couple of tokens per batch instead of all thirty, and the price-history reads had been silently returning less history the more of it you asked for.</description></item>+ <item>+ <title>Text to 3D no longer stops when our image storage does</title>+ <link>https://three.ws/forge</link>+ <guid isPermaLink="false">2026-09-08:Text to 3D no longer stops when our image storage does</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Turning a written prompt into a model takes one step you never see: we paint a reference picture of what you asked for, save it somewhere our sculpting engines can read, and hand them the link. If that save failed, the whole thing was over before a graphics card was ever asked for anything, and the error you got back was our storage provider's own wording about signatures and access keys, which told you nothing you could act on. Making a model from a photo you upload was unaffected, because it brings its own picture, so half the feature could look perfectly healthy while the other half was completely down. Our own engines never needed that saved copy: they accept the picture itself, sent along with the request. So when storage will not take the write, the reference view now travels inside the job and your model still gets built. The engines that genuinely need a link, the outside ones you can pick by name, now say so in plain language and point you at the ones still running, instead of failing with a message about our secret keys. Generations that take this route lose the extra angles we normally paint to fill in a subject's back, so they are built from the single front view.</description>+ </item>+ <item>+ <title>The Agent Economy page is readable on a phone, and its x402 services finally have names</title>+ <link>https://three.ws/economy</link>+ <guid isPermaLink="false">2026-09-08:The Agent Economy page is readable on a phone, and its x402 services finally have names</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>On a narrow screen the page laid itself out at desktop width and the browser quietly cut off two thirds of every section, so most of the content was simply unreachable on a phone. It now fits the screen at every size. The live x402 service list was also close to useless: every one of the ninety endpoints was labelled "Service", the price sat next to a raw token contract address, and the network read "eip155:8453" instead of "Base". Each row now carries a real name, its endpoint address, a clean price and a readable chain, an endpoint that takes path parameters no longer pretends to be a clickable page, and the list opens with a screenful you can expand to all of them. The three empty states tell you where to go next, and the services counter reports the true number instead of "40+".</description>+ </item>+ <item>+ <title>The ChatGPT and AR docs now describe the AR launcher that actually runs</title>+ <link>https://three.ws/docs/ar</link>+ <guid isPermaLink="false">2026-09-08:The ChatGPT and AR docs now describe the AR launcher that actually runs</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>docs</category>+ <description>Three corrections to the documentation for the ChatGPT surfaces and augmented reality. The AR reference still said the one-tap launcher at /api/ar draws the model itself in Google's model-viewer, which stopped being true when the launcher became a pure router: it now sends Android straight into Scene Viewer and everyone else to a bundled page that builds a real USDZ on the device, which is what iPhone's Quick Look needs. The pages are named correctly throughout, including which one does the file conversion, so nobody debugging an iPhone handoff starts in the wrong file. The ChatGPT AR page also credited a single generation engine for every model, when the connector actually tries the free engines in turn and steps down to a slower one if the first is cold, which is why generation keeps working when one lane is down. And the paid studio server's page promised that anyone can browse its tool catalogue without credentials, without mentioning that a connector client is deliberately answered with a sign-in challenge instead, as the connector standard requires; both paths are now written down, with a command that works. That page's tool tables also describe nine tools that were previously only named in its price list, so no tool appears with a price and no explanation.</description>+ </item><item><title>The club now takes $THREE at the door and at the stage, not just USDC</title><link>https://three.ws/club</link>@@ -54,6 +94,14 @@<category>fix</category><description>The club has always advertised two ways to pay: USDC or $THREE, on Solana, for both the cover charge and every dance tip. Only one of them was reachable. The checkout window picked the first token a service offered and gave you no way to choose the other, so $THREE was quoted on every paid page and payable on none of them. Across every club tip ever settled, not one was paid in $THREE, which is what you would expect from a menu with a hidden second item. The checkout now shows a token picker whenever a service quotes more than one, with each token's real price on it, so you can compare 0.001 USDC against its $THREE equivalent before you approve anything, and the price at the top of the window follows what you pick. If you have agent wallets, they still pay in USDC only, and the window now says so instead of quietly hiding them when you switch tokens. Two settlement bugs behind the door were fixed at the same time. The first would have hit the very first person to pay in $THREE: sending a token to a wallet that has never held it requires opening an account for it on-chain, and the check that decides whether we can afford to sponsor a payment was ignoring that cost, so the payment would have been accepted and then failed on-chain for a reason that looked like something else entirely. The second was making the club look open when it was not: a healthy payer covering their own fees could reset a shared 'we can still sponsor payments' flag that belonged to a different wallet, so the door kept quoting prices it could not actually take. Finally, when payments are paused because the wallet that settles them needs topping up, the checkout now says that in a sentence and tells you nothing was charged, instead of showing you the raw error envelope it used to paste in, which read like a broken link.</description></item>+ <item>+ <title>The Launch a Coin button now works once you have filled the form</title>+ <link>https://three.ws/launch</link>+ <guid isPermaLink="false">2026-09-08:The Launch a Coin button now works once you have filled the form</guid>+ <pubDate>Tue, 08 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>On the Launch a Coin page we fill in your token name and ticker from the agent you pick, but never the description, because only you can write that. The launch button read "Add name, symbol & description to launch" until all three were there, and that label was worked out once when the page drew itself and then never again. So the moment you typed your description the button was describing a form that no longer existed: it still said something was missing, and pressing it did nothing whatsoever, because it went looking for an empty field and found none. The button now keeps up with what you type, turning into "Connect wallet to launch" or the real launch action the instant the last field is filled, and back again if you clear one. Pressing it while something is genuinely missing now says which field it is, instead of silently moving your cursor there. Separately, if we cannot reach your agent list, the page now says so and offers a Try again button that recovers in place; it used to tell owners of a dozen agents that they had none yet and send them off to create a duplicate. The agent picker also fits a phone screen now instead of running off both edges.</description>+ </item><item><title>Awesome 3D Agents</title><link>https://three.ws/awesome</link>diff --git a/public/features.json b/public/features.jsonindex c9fe2bc67..9d91c635f 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-08T17:19:33.268Z",+ "generated_at": "2026-09-08T17:31:11.467Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",