Skip to content

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

docs(wardrobe): document the forge's bounded job resume and log the /wardrobe fixes

nirholas0a8dc6a80880
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2d5dd98ab..133fb546b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -28,6 +28,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Daily usage caps stopped resetting themselves partway through the day**: When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over. `[fix, infra]`
- **Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands**: Nine documentation pages are written as article drafts, so each one starts with a small block of publishing metadata: the title, where it is meant to run, its tags. That block is meant for the tooling, not for you, but the docs reader had no idea what it was and rendered it as an enormous heading at the very top of the article, above the actual writing. It is now recognised and hidden, on the page and in the Copy page text, so those articles begin where they should. Reading the same pages closely turned up claims that had drifted: several said three.ws was already live on AWS Marketplace and billing usage to your AWS invoice. The integration is built and deployed, but the listing itself has not been published yet and the pricing decision is a free subscription with no AWS metering, so the AWS pages now say exactly that and point at the page that tracks the status. The MCP article's vanity-address tool was also listed at a metered price of up to fifty cents; it is a flat five cents per grind, which is what the code has always charged. (`/docs/aws-marketplace`) `[docs, fix]`
- **Eight build tutorials now match what the platform actually does**: An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations. (`/tutorials/connect-ai-brain`) `[docs, fix]`
+- **Grind-Bounty Market: shared bounty links now open the bounty, and "Grind this" grinds that one**: Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers. (`/vanity/bounties`) `[fix, improvement]`
- **Looking up an on-chain agent by its CAIP reference works again**: The public resolver that turns an ERC-8004 agent reference into its owner, token URI and verified agent card could not be reached at all. An agent reference ends in a slash before its token id, and the documentation told callers to percent-encode the whole reference, which turns that slash into %2F. The API refuses any address segment holding an encoded separator, because that is the same trick used to escape a path and reach files that were never meant to be served, so every correctly-formed lookup was turned away as an unknown address before it ever reached the resolver. The verification badge you can embed on your own site built its request in exactly that shape, so it never showed a result either. The resolver now accepts the reference with its slash as a normal part of the address, the badge asks for it that way, and the documentation shows the form that works. The protection against encoded separators is untouched. New tests resolve the address through the same routing the live site uses, so this cannot quietly break again. (`/docs/api-reference`) `[fix]`
- **Oracle stops answering "nothing is happening" when the database is the thing that is down**: Several Oracle reads shared a habit: if the database was unreachable for a few seconds, they answered normally with an empty result. The movers panel said nothing was moving, the stats hero said no coin had ever been scored and no agent was armed, a coin's conviction sparkline came back flat, and the machine-readable signal endpoint told autonomous agents there were no plays, which is exactly the cue for an agent to stand down. Every one of those answers was then cached at the edge for a minute or two, so a blip lasting seconds kept showing a dead market long after the database was back. Those endpoints now tell the difference between a connectivity failure and an ordinary query fault: the first is reported honestly as a temporary outage with a retry hint and is never cached, the second still degrades to the empty answer it always did. The social ingest got the sharper end of the same bug: it used to reply that a batch had been accepted while reporting zero mints written, a receipt for a write that never landed. It now fails loudly so the sender retries. Shared conviction cards behave too: one built during an outage is no longer pinned to a coin's link preview for 15 minutes. (`/oracle`) `[fix, improvement]`
- **Pages stop loading a 3D robot you have not scrolled to yet**: The small animated robot in the site footer was starting up the moment a page opened, at the bottom of a page nobody had scrolled to. On plain pages that meant downloading a whole second 3D engine (253 KB) before anything else, and on the Forge it was the single busiest thing on the page: nearly 20 seconds of browser work, more than the Forge itself. It now waits until you are about a screen away from the footer, so it still greets you on the way down but no longer competes with the page you actually opened. It also stops taking a 3D slot away from the avatars on the page, which on a busy grid could leave a real avatar unable to render. Separately, the Forge's example prompt chips no longer shove the page down as they shuffle to a fresh set on load. (`/forge`) `[improvement, fix]`
@@ -64,6 +65,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The live trade tape now says when live trades are unavailable**: The per-coin trade tape streams from PumpPortal, which gates per-token trade subscriptions behind a funded API key. When that subscription was refused, the connection stayed open and simply never delivered a trade, so the tape showed a lit 'live' indicator above rows that could never arrive, and there was no way for a viewer to tell that apart from a genuinely quiet coin. The stream now forwards the refusal to the browser and the tape reports it plainly, keeping the settled trades it already loaded. A malformed coin address on the stream is also rejected up front with a clear error instead of opening a connection that can never match anything. `[fix]`
- **The LLM usage panel in your dashboard settings finally shows your real numbers**: Settings has a panel meant to show how much AI inference your agents have used this month. It always said "No usage yet", no matter how much you had used, because the endpoint behind it never sent the figures the panel was written to read. It does now: calls this month, tokens consumed, what those calls cost, and a per-model table showing which models did the work, busiest first. The same response also had two storage limits going out as text rather than numbers, which is the kind of difference that turns a size comparison into nonsense; both are numbers now. An API key with the profile scope can read all of it, so you can pull your own usage from a script, and the developer guide shows the exact shape. (`/dashboard/settings`) `[fix, improvement]`
- **The multiplayer worlds server connects on any local port, and its README documents what it actually reads**: Two fixes to the server that runs every live world (/play, /walk, /agora, /irl, /play/war, the Living Stages, /ar/studio). Running two copies of the site on one machine used to break the worlds: the second copy gets the next free web port, and the server only accepted connections from the first four, so the world silently refused to join. Outside production it now accepts any connection coming from the same machine, while the live server keeps its exact origin list unchanged. Its README also described six settings when the server reads more than thirty, and listed two web endpoints when it serves seven, so anyone running or deploying it was working from a map that no longer matched the ground; the settings, the endpoints, and how the admin monitor is protected are now written down as they really behave, and the origin rules, the refusal to boot production without a real signing secret, and the closed admin monitor are covered by tests. `[fix, docs, infra]`
+- **The pay-as-you-learn tutor can take a payment again**: Every question on the tutor page died at the "Confirming price" step with a raw browser error, so no explanation was ever bought and the checkout never even reached the tutor service. The shared payment library was asking the service for its price with a GET request that carried a question body, which browsers refuse outright; it now sends the POST the service expects whenever a request body is present, which also unblocks any other page that pays a POST endpoint. On top of that, a resumed session no longer shows a real running total next to a stuck "0 answers" count, resumed questions show what each one cost, a shimmering placeholder now stands in for the answer while it is being written, the invoice closes with the Escape key and returns you to where you were, the page keeps a proper top-level heading once the conversation starts, every control has a visible keyboard focus ring, and a checkout that cannot reach the service now says so in plain language instead of quoting the browser. (`/tutor`) `[fix, improvement]`
- **The persona builder stops reporting a model outage as if you had been signed out**: The two routes behind the persona builder (the one that turns your interview answers or a sample of your own writing into a structured persona, and the one that replies to you in that persona's voice) used to hand you whatever status code the model provider returned. If a server-side key expired, the provider answered 401 and so did we, which reads to a browser as an expired session on a request where nothing was wrong with your sign-in. Both now report a provider failure as exactly what it is: a server-side fault, with a plain message and no implication that you need to log back in. Separately, when the platform's daily model-spend ceiling is reached, the builder now says so and tells you when it resets, instead of asking you to retry something that could not have succeeded for the rest of the day. Both routes also now record their model usage against your account, so the spend they generate is visible and capped rather than untracked, and the daily extraction budget now holds across every server instance instead of being counted separately on each one. `[fix, improvement]`
- **The persona extraction and preview endpoints are documented in the API reference**: Both routes have been live and usable for a while (turn a short interview or a sample of someone's writing into a structured voice profile, then audition that profile against a test message), but the only way to learn their request shape was to read the demo page's source. The API reference now covers them properly: every field with its limits, a real request and response for each, the exact meaning of every error status, and the per-user call budgets. The demo at /demos/persona-extract.html remains the fastest way to see them work. (`/docs/api-reference`) `[docs]`
- **The plugin marketplace stops hiding a plugin when you page through it**: Browsing plugins a page at a time could show you the same plugin twice and never show another one at all. The catalogue was sorted by install count and publish date, and the built-in plugins were all published in the same instant with zero installs, so that sort left them tied and the database was free to order the tied rows differently on every request. One plugin therefore landed on two consecutive pages and one fell through the gap. The order is now decided all the way down, so paging through the catalogue returns every plugin exactly once. Searching also takes your text literally: typing a percent sign or an underscore used to act as a database wildcard and match rows it should not. Publishing got stricter at the same time, because a plugin manifest is handed to the model as a tool definition by whoever installs it: a tool name now has to be plain letters, digits, underscores, or hyphens, every tool needs a real description, and a manifest has to fit the same 64KB ceiling that importing one by URL already enforced. And pointing the importer at a repository web page instead of the raw manifest file now says exactly that, rather than showing a raw parser error. (`/marketplace`) `[fix, improvement]`
@@ -75,15 +77,19 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The trading control room now tells you when the agents cannot afford to trade**: The /trading page showed a green "Trading live" badge whenever the worker was up and the launch feed was connected. Both of those can be true while the agents' wallets are too empty to place a single buy, which is exactly what was happening: four of twelve armed wallets were below the minimum entry size and the page said everything was fine. It now reads the fleet verdict the trading worker already publishes, so an underfunded fleet says "Live, wallets underfunded" and one that cannot trade at all says "Out of SOL", each naming the real cause instead of blaming the feed. A new Wallets funded vital shows how many armed wallets can actually place their configured size, how much SOL would refill the rest, and whether the funding wallet can do it automatically or a person has to step in. An agent with no return to report now reads "ROI unavailable" rather than a stray dot. (`/trading`) `[fix, improvement]`
- **The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them**: The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage. (`/trending`) `[fix]`
- **The Tutor’s running tab and end-of-session invoice now show what you actually paid**: The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading "no questions" and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for. (`/tutor`) `[fix]`
+- **The vanity receipt verifier says what went wrong instead of going quiet**: Verifying a provably-fair vanity receipt runs entirely in your browser, so when the cryptography modules could not load (a blocking extension, a captive network, an offline laptop) the Verify button silently did nothing at all. The page now loads that code on demand and, when it cannot, says so plainly and hands you the offline command line check instead. Receipts delivered without a sealed envelope now get the custody check too, proving the key you hold is the one the receipt describes, with no extra key to paste. A share link whose receipt payload arrived damaged now explains that rather than leaving you with an empty form, opening a sealed envelope with the wrong key now tells you which key it wanted, and every control has a visible keyboard focus ring. (`/vanity/verify`) `[fix, improvement]`
- **The vanity receipt verifier stops calling honest receipts fraudulent, and the avatar CLI takes a Solana address**: Two documented commands did not do what their page said. The command-line verifier for a provably-fair vanity address receipt scored the difficulty claim with the retired flat model, the one that treats every Base58 character as equally likely. Every receipt issued since the leading-character correction landed therefore failed its difficulty check and was reported as untrustworthy, even though the in-browser verifier at /vanity/verify passed the same receipt. The verifier now reads the model each receipt names in its own signed difficulty block, exactly as the page and the SDK do, so current receipts verify and older ones keep verifying under the model they were issued under. Separately, the Rig Doctor page showed an avatar-manifest command taking a Solana address as the owner, which the CLI rejected outright: it understood Ethereum addresses and full CAIP-10 identifiers and nothing else. Since Solana is the home chain, a bare Solana address is now accepted and recorded as solana:mainnet-beta. Alongside those, eight tutorial and reference pages were audited against the code they describe: the Vercel self-hosting guide had a stale copy of the config file and pointed at a migrations folder that has moved, the MCP guide listed three placeholder OAuth scopes where the live server publishes twelve real per-capability ones, and the Avatar CLI page pinned a version number that npm has never had. (`/docs/rig-doctor`) `[fix, docs, sdk]`
- **The vanity SDK now uses the payment wallet you hand it, and the in-chat 3D avatar keeps its tuned lighting**: Three fixes in the developer packages. The @three-ws/vanity SDK documented a fetch option on its paid address-grinding lane but silently ignored it, so a developer who passed a payment-enabled fetch got a payment-required error back instead of the keypair they paid for; that option now works, as do a custom API host and key. The avatar MCP server's in-chat 3D viewer had been hand-tuned with softer shadows, brighter exposure and a neutral environment light, but the script that rebuilds it before every release still produced the old flat version, so the next release would have quietly undone the tuning; the script now produces the tuned viewer, and the same settings apply to the fallback view for chat apps that cannot run the interactive one. The tool SDK's quick-start example pointed at an API that does not exist and skipped the wrapper an MCP server needs to return anything at all, so following it produced a tool that answered with nothing; it now runs end to end against a real free three.ws endpoint. `[fix, sdk, docs]`
- **The vault's session controls moved out of browser pop-ups and its model panel became a real modal**: The vault page (/vault) gives every visitor a session key that acts as their buyer identity: it is what pays for a model and what decrypts it in the browser afterwards. Everything you could do with that key used to happen through the browser's own grey pop-up boxes, which offered no way to see the address, no way to copy it, and no way to start over with a fresh one. The session strip now does all of it on the page: copy the address to fund it from anywhere, open an inline amount field to top it up from your wallet with the amount checked before the wallet is even asked, and rotate to a new key behind a two-step confirmation that first spells out what a new key costs you. The panel that opens when you pick a model is now a proper dialog: it says it is checking your purchase status instead of flashing a Buy button it might have to take back, keyboard focus stays inside it, Escape closes it, and closing puts you back on the model you were reading. When listings fail to load, the page now offers a way to try again instead of only stating the failure, and both empty states point at what to do next. (`/vault`) `[improvement, fix]`
- **The Walk page shows the real top walkers again instead of claiming nobody has walked**: The Top walkers board on /walk read "No walks logged yet. Be the first to put down some distance" for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap. (`/walk`) `[fix]`
+- **The Wardrobe's garment forge no longer locks itself after a job expires**: Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting "no such job" answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with "Reconnecting" as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it. (`/wardrobe`) `[fix, improvement]`
+- **The widgets gallery stopped clipping its controls on phones and now recovers from a failed load**: The widgets gallery (/widgets) is where you pick a pre-built chat, voice, or 3D-avatar embed and copy the one line of HTML that drops it into your own page. On a narrow phone screen, each card's preview frame and its Customize panel were wider than the card itself, so the right edge got cut off: the mint field ran past the panel and the Reset button was pushed off-screen entirely, out of reach. Card layout now shrinks to the screen it is on, and the whole page is clean from 320px up. If the showcase list fails to load, the page now says so in plain language and offers a Try again button that reloads it in place, plus a link to the widget docs, instead of leaving a one-line error with no way forward. If the list comes back empty, the gallery explains what it would normally show and points at the Studio rather than showing a blank space. The widget count in the header now reflects the widgets actually loaded in every language, the page has a real top-level heading, the type filters announce which one is active to screen readers, the Preview and Code tabs are wired up as real tabs, and Escape closes the embed-format menu. (`/widgets`) `[fix, improvement]`
- **Three docs pages stop pointing readers at a dead page, a missing section, and a snippet that does nothing**: The Vanity page told you to grind a long address yourself in the browser at /vanity, but that path has never existed and answers 404; the in-browser grinder lives at /vanity-wallet, and both links on the page now go there. In Troubleshooting, the fix for a Quick Look model that opens and instantly closes linked to a model-optimization section that is not on the AR page, so the link dropped you at the top with nothing to read; it now opens the section that actually covers it. The same page told you to add a responsive attribute to size an inline embed, with a snippet that set the width in CSS. Neither half worked: responsive sizing is already on by default, and the element reads the width attribute rather than the computed style, so the documented snippet never produced the 3:4 ratio it promised. The instructions now show the form that does work, and name the two things that switch it off. (`/docs/troubleshooting`) `[fix, docs]`
- **Two tutorials stop shipping code samples that quietly do nothing**: An audit of eight developer tutorials found two whose main code sample looked right and silently failed. The custom-skill weather handler split the weather API's reply on a plus sign, but the temperature field arrives with a leading plus of its own, so every field after the condition landed one slot off and the temperature always came back empty; it also mapped the fahrenheit option to a format code that means feels-like rather than Fahrenheit, so the celsius and fahrenheit paths returned the same units. Both are fixed and the sample was run against the live API in both unit modes. The gesture tutorial's AI lane read an emotion-breakdown field the Granite analysis tool has never returned, so the strength check never passed and the agent never played a single animation; it now reads the score and risk flags the tool actually returns, and grades the gesture across four bands instead of a binary. Separately, twelve tutorial hero buttons pointed at anchors on the docs hub that stopped existing when the hub split into per-topic pages, and now open the real pages; a placeholder URL in the Pump.fun tutorial was being parsed as HTML, which broke a link and injected stray elements into the page; and the self-host guide was corrected throughout, including storage variable names that no longer matched the code, a database step that left most tables uncreated, an audit-logging example importing a function that does not exist, a Cloudflare worker setup for a proxy the platform does not run, and a license claim that described the repository as open source when it is not. (`/tutorials/custom-skill`) `[docs, fix]`
- **Viability now shows skeletons while it reads and says what broke when a read fails**: The Viability page (/viability) reports the two real money loops behind three.ws: $THREE marketplace GMV and take-rate, and guarded agent coin trades with realized P&L. Until now, a slow read left the page as a bare headline with nothing underneath, and a failed read quietly deleted both panels while the page still claimed it had just updated. Both panels now hold their shape with skeletons while the live read is in flight, so the numbers land without the page jumping. If a read fails, that panel says so in plain language, names the reason (offline, rate limited, the status the API returned, or a deploy still rolling out), and offers a Retry that re-runs only that panel, leaving a healthy one untouched. The freshness stamp is honest too: it reports a read in flight, a failed read, or how long ago the figures on screen were actually good. Section titles are now real headings, and the network toggle announces itself correctly to screen readers. (`/viability`) `[improvement, fix]`
- **Voice and vision SDKs ship runnable examples, and the x402 seller SDK reads its Solana sponsor from the environment**: @three-ws/voice and @three-ws/vision-mcp now include example scripts you can run as-is against the live free lanes: the voice one speaks a sentence, animates a face from those exact bytes, and transcribes it back; the vision one probes the lane, writes alt text for an image, and reads the text off it. @three-ws/x402-server used to demand the Solana sponsor account as a code option even though its own error message told you to set X402_FEE_PAYER_SOLANA, so a correctly configured deployment still got missing_fee_payer; it now reads that environment variable when the option is omitted. The VS Code x402 extension's endpoint scaffolder was generating Base-only endpoints and now generates Solana-first ones, matching every paid route on the platform, and it ships with a test suite covering which payment requirement it selects. `[sdk, fix]`
- **Widget analytics can tell you where your visitors are again, and a shared widget link previews correctly everywhere**: The country column in your widget stats has been empty since the platform moved to its current host in July. A visitor's country was read from a header only the old host set, so once it was gone every view was recorded with no country at all and the top-countries panel stayed blank no matter how much traffic a widget got. Country is now read from the headers our current edge provides, and it is checked against the shape of a real two-letter country code before it is stored, so nobody can push junk into your analytics by editing a request. Chat sessions on talking-agent widgets get the same fix. Separately, the oEmbed endpoint that Slack, Discord, WordPress, Ghost and Notion call to unfurl a shared widget link now says plainly when a consumer asks for a format we do not publish, instead of returning JSON labelled as the format that was asked for and leaving the embed broken with nothing to explain why. (`/widgets`) `[fix, improvement]`
+- **World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard**: The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a "Meet the agent in AR" option next to "Begin the encounter", and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970. (`/world-lines`) `[fix, improvement]`
- **Your walk keeps syncing across devices, and a remotely driven avatar reports where it really is**: Four fixes across the walking avatar. Signed-in walkers sync their walk (avatar, environment, camera, position) between devices, and the page saves that snapshot on a half-minute heartbeat, but the endpoint only allowed thirty writes an hour and counted every read against the same budget: about a quarter hour into a walk, syncing quietly stopped, and everyone sharing an office or cafe connection shared one allowance. Writes are now measured per account, sized to how often the page actually saves, and reading your snapshot back costs nothing. When an outside program drives a live walk page through the control API, the page reports its position, heading, motion and scene on every poll; one unexpected value in that report used to discard the whole thing, so the controller's status read could show a stale avatar with nothing to explain it. Each field is now taken on its own merits. A command sent with an invalid control token is refused before its contents are inspected. And the leaderboard now shows an unranked walker with the same handle, profile link and picture as everyone else on the board, always drawn from a single avatar rather than pairing one avatar's name with another's picture. (`/walk`) `[fix]`
## 2026-08-14
diff --git a/data/changelog.json b/data/changelog.json
index 54543d9ad..93c8d773c 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,56 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-15",
+ "title": "World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard",
+ "summary": "The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a \"Meet the agent in AR\" option next to \"Begin the encounter\", and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/world-lines"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Grind-Bounty Market: shared bounty links now open the bounty, and \"Grind this\" grinds that one",
+ "summary": "Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/vanity/bounties"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The Wardrobe's garment forge no longer locks itself after a job expires",
+ "summary": "Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting \"no such job\" answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with \"Reconnecting\" as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/wardrobe"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The pay-as-you-learn tutor can take a payment again",
+ "summary": "Every question on the tutor page died at the \"Confirming price\" step with a raw browser error, so no explanation was ever bought and the checkout never even reached the tutor service. The shared payment library was asking the service for its price with a GET request that carried a question body, which browsers refuse outright; it now sends the POST the service expects whenever a request body is present, which also unblocks any other page that pays a POST endpoint. On top of that, a resumed session no longer shows a real running total next to a stuck \"0 answers\" count, resumed questions show what each one cost, a shimmering placeholder now stands in for the answer while it is being written, the invoice closes with the Escape key and returns you to where you were, the page keeps a proper top-level heading once the conversation starts, every control has a visible keyboard focus ring, and a checkout that cannot reach the service now says so in plain language instead of quoting the browser.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/tutor"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The vanity receipt verifier says what went wrong instead of going quiet",
+ "summary": "Verifying a provably-fair vanity receipt runs entirely in your browser, so when the cryptography modules could not load (a blocking extension, a captive network, an offline laptop) the Verify button silently did nothing at all. The page now loads that code on demand and, when it cannot, says so plainly and hands you the offline command line check instead. Receipts delivered without a sealed envelope now get the custody check too, proving the key you hold is the one the receipt describes, with no extra key to paste. A share link whose receipt payload arrived damaged now explains that rather than leaving you with an empty form, opening a sealed envelope with the wrong key now tells you which key it wanted, and every control has a visible keyboard focus ring.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/vanity/verify"
+ },
{
"date": "2026-08-15",
"title": "The widgets gallery stopped clipping its controls on phones and now recovers from a failed load",
diff --git a/docs/avatar-wardrobe.md b/docs/avatar-wardrobe.md
index f32371d16..5773bcbb2 100644
--- a/docs/avatar-wardrobe.md
+++ b/docs/avatar-wardrobe.md
@@ -113,6 +113,20 @@ measured against the canonical body before publish, so a generated garment
can never be a tile the closet then refuses to wear. Offline proof harness:
`node scripts/verify-garment.mjs <manifest url> [avatar.glb]`.
+Seven minutes is longer than most people keep a tab open, so `/wardrobe` saves
+the job id in `localStorage` under `twx_wardrobe_job` and resumes polling on
+the next visit. That resume is deliberately bounded, because a saved id that
+can never resolve would otherwise leave the generator disabled forever:
+
+- a `404` (or `job_not_found`) is **terminal**, not a blip. The saved id is
+ dropped, the form unlocks, and the page says the job is no longer on the
+ forge. Finished jobs are cleared upstream, so this is the normal end state
+ for a resume that arrives too late;
+- any other poll failure is treated as transient and retried on a longer
+ interval, up to six consecutive failures. After that the form unlocks and
+ the page says the job is still saved and a reload will pick it back up. The
+ id survives, so a genuine outage never destroys a running generation.
+
## Persistence shape
```json
diff --git a/prompts/swarm-100/route-wardrobe.md b/prompts/swarm-100/route-wardrobe.md
deleted file mode 100644
index c3ff61b47..000000000
--- a/prompts/swarm-100/route-wardrobe.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# Route audit: /wardrobe (Wardrobe)
-
-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==='/wardrobe')console.log(JSON.stringify(g,null,2))"
-
-2. Find the serving implementation: grep "/wardrobe" 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/wardrobe
-
-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: /wardrobe ("Wardrobe", section "main").
-Declared purpose: The open garment catalog for 3D avatars: browse every wearable, inspect it in 3D, and generate new pieces from a text prompt. Every piece binds to any humanoid avatar at runtime.
-
-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/wardrobe. 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 /wardrobe: 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-wardrobe.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index 973bca486..637b59911 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T19:14:30.906Z",
+ "generated_at": "2026-08-15T19:26:15.723Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -242,6 +242,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Grind-Bounty Market: shared bounty links now open the bounty, and \"Grind this\" grinds that one",
+ "summary": "Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers.",
+ "link": "/vanity/bounties",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -633,6 +644,17 @@
"infra"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The pay-as-you-learn tutor can take a payment again",
+ "summary": "Every question on the tutor page died at the \"Confirming price\" step with a raw browser error, so no explanation was ever bought and the checkout never even reached the tutor service. The shared payment library was asking the service for its price with a GET request that carried a question body, which browsers refuse outright; it now sends the POST the service expects whenever a request body is present, which also unblocks any other page that pays a POST endpoint. On top of that, a resumed session no longer shows a real running total next to a stuck \"0 answers\" count, resumed questions show what each one cost, a shimmering placeholder now stands in for the answer while it is being written, the invoice closes with the Escape key and returns you to where you were, the page keeps a proper top-level heading once the conversation starts, every control has a visible keyboard focus ring, and a checkout that cannot reach the service now says so in plain language instead of quoting the browser.",
+ "link": "/tutor",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -749,6 +771,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The vanity receipt verifier says what went wrong instead of going quiet",
+ "summary": "Verifying a provably-fair vanity receipt runs entirely in your browser, so when the cryptography modules could not load (a blocking extension, a captive network, an offline laptop) the Verify button silently did nothing at all. The page now loads that code on demand and, when it cannot, says so plainly and hands you the offline command line check instead. Receipts delivered without a sealed envelope now get the custody check too, proving the key you hold is the one the receipt describes, with no extra key to paste. A share link whose receipt payload arrived damaged now explains that rather than leaving you with an empty form, opening a sealed envelope with the wrong key now tells you which key it wanted, and every control has a visible keyboard focus ring.",
+ "link": "/vanity/verify",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -794,6 +827,28 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The Wardrobe's garment forge no longer locks itself after a job expires",
+ "summary": "Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting \"no such job\" answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with \"Reconnecting\" as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it.",
+ "link": "/wardrobe",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The widgets gallery stopped clipping its controls on phones and now recovers from a failed load",
+ "summary": "The widgets gallery (/widgets) is where you pick a pre-built chat, voice, or 3D-avatar embed and copy the one line of HTML that drops it into your own page. On a narrow phone screen, each card's preview frame and its Customize panel were wider than the card itself, so the right edge got cut off: the mint field ran past the panel and the Reset button was pushed off-screen entirely, out of reach. Card layout now shrinks to the screen it is on, and the whole page is clean from 320px up. If the showcase list fails to load, the page now says so in plain language and offers a Try again button that reloads it in place, plus a link to the widget docs, instead of leaving a one-line error with no way forward. If the list comes back empty, the gallery explains what it would normally show and points at the Studio rather than showing a blank space. The widget count in the header now reflects the widgets actually loaded in every language, the page has a real top-level heading, the type filters announce which one is active to screen readers, the Preview and Code tabs are wired up as real tabs, and Escape closes the embed-format menu.",
+ "link": "/widgets",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -849,6 +904,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard",
+ "summary": "The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a \"Meet the agent in AR\" option next to \"Begin the encounter\", and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970.",
+ "link": "/world-lines",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index f9b4c1b52..9275698f9 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -182,6 +182,14 @@
<category>docs</category>
<description>An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations.</description>
</item>
+ <item>
+ <title>Grind-Bounty Market: shared bounty links now open the bounty, and &quot;Grind this&quot; grinds that one</title>
+ <link>https://three.ws/vanity/bounties</link>
+ <guid isPermaLink="false">2026-08-15:Grind-Bounty Market: shared bounty links now open the bounty, and &quot;Grind this&quot; grinds that one</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#&lt;id&gt;), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers.</description>
+ </item>
<item>
<title>Looking up an on-chain agent by its CAIP reference works again</title>
<link>https://three.ws/docs/api-reference</link>
@@ -470,6 +478,14 @@
<category>fix</category>
<description>Two fixes to the server that runs every live world (/play, /walk, /agora, /irl, /play/war, the Living Stages, /ar/studio). Running two copies of the site on one machine used to break the worlds: the second copy gets the next free web port, and the server only accepted connections from the first four, so the world silently refused to join. Outside production it now accepts any connection coming from the same machine, while the live server keeps its exact origin list unchanged. Its README also described six settings when the server reads more than thirty, and listed two web endpoints when it serves seven, so anyone running or deploying it was working from a map that no longer matched the ground; the settings, the endpoints, and how the admin monitor is protected are now written down as they really behave, and the origin rules, the refusal to boot production without a real signing secret, and the closed admin monitor are covered by tests.</description>
</item>
+ <item>
+ <title>The pay-as-you-learn tutor can take a payment again</title>
+ <link>https://three.ws/tutor</link>
+ <guid isPermaLink="false">2026-08-15:The pay-as-you-learn tutor can take a payment again</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Every question on the tutor page died at the &quot;Confirming price&quot; step with a raw browser error, so no explanation was ever bought and the checkout never even reached the tutor service. The shared payment library was asking the service for its price with a GET request that carried a question body, which browsers refuse outright; it now sends the POST the service expects whenever a request body is present, which also unblocks any other page that pays a POST endpoint. On top of that, a resumed session no longer shows a real running total next to a stuck &quot;0 answers&quot; count, resumed questions show what each one cost, a shimmering placeholder now stands in for the answer while it is being written, the invoice closes with the Escape key and returns you to where you were, the page keeps a proper top-level heading once the conversation starts, every control has a visible keyboard focus ring, and a checkout that cannot reach the service now says so in plain language instead of quoting the browser.</description>
+ </item>
<item>
<title>The persona builder stops reporting a model outage as if you had been signed out</title>
<link>https://three.ws/changelog</link>
@@ -558,6 +574,14 @@
<category>fix</category>
<description>The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading &quot;no questions&quot; and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for.</description>
</item>
+ <item>
+ <title>The vanity receipt verifier says what went wrong instead of going quiet</title>
+ <link>https://three.ws/vanity/verify</link>
+ <guid isPermaLink="false">2026-08-15:The vanity receipt verifier says what went wrong instead of going quiet</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Verifying a provably-fair vanity receipt runs entirely in your browser, so when the cryptography modules could not load (a blocking extension, a captive network, an offline laptop) the Verify button silently did nothing at all. The page now loads that code on demand and, when it cannot, says so plainly and hands you the offline command line check instead. Receipts delivered without a sealed envelope now get the custody check too, proving the key you hold is the one the receipt describes, with no extra key to paste. A share link whose receipt payload arrived damaged now explains that rather than leaving you with an empty form, opening a sealed envelope with the wrong key now tells you which key it wanted, and every control has a visible keyboard focus ring.</description>
+ </item>
<item>
<title>The vanity receipt verifier stops calling honest receipts fraudulent, and the avatar CLI takes a Solana address</title>
<link>https://three.ws/docs/rig-doctor</link>
@@ -590,6 +614,22 @@
<category>fix</category>
<description>The Top walkers board on /walk read &quot;No walks logged yet. Be the first to put down some distance&quot; for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap.</description>
</item>
+ <item>
+ <title>The Wardrobe's garment forge no longer locks itself after a job expires</title>
+ <link>https://three.ws/wardrobe</link>
+ <guid isPermaLink="false">2026-08-15:The Wardrobe's garment forge no longer locks itself after a job expires</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting &quot;no such job&quot; answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with &quot;Reconnecting&quot; as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it.</description>
+ </item>
+ <item>
+ <title>The widgets gallery stopped clipping its controls on phones and now recovers from a failed load</title>
+ <link>https://three.ws/widgets</link>
+ <guid isPermaLink="false">2026-08-15:The widgets gallery stopped clipping its controls on phones and now recovers from a failed load</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The widgets gallery (/widgets) is where you pick a pre-built chat, voice, or 3D-avatar embed and copy the one line of HTML that drops it into your own page. On a narrow phone screen, each card's preview frame and its Customize panel were wider than the card itself, so the right edge got cut off: the mint field ran past the panel and the Reset button was pushed off-screen entirely, out of reach. Card layout now shrinks to the screen it is on, and the whole page is clean from 320px up. If the showcase list fails to load, the page now says so in plain language and offers a Try again button that reloads it in place, plus a link to the widget docs, instead of leaving a one-line error with no way forward. If the list comes back empty, the gallery explains what it would normally show and points at the Studio rather than showing a blank space. The widget count in the header now reflects the widgets actually loaded in every language, the page has a real top-level heading, the type filters announce which one is active to screen readers, the Preview and Code tabs are wired up as real tabs, and Escape closes the embed-format menu.</description>
+ </item>
<item>
<title>Three docs pages stop pointing readers at a dead page, a missing section, and a snippet that does nothing</title>
<link>https://three.ws/docs/troubleshooting</link>
@@ -630,6 +670,14 @@
<category>fix</category>
<description>The country column in your widget stats has been empty since the platform moved to its current host in July. A visitor's country was read from a header only the old host set, so once it was gone every view was recorded with no country at all and the top-countries panel stayed blank no matter how much traffic a widget got. Country is now read from the headers our current edge provides, and it is checked against the shape of a real two-letter country code before it is stored, so nobody can push junk into your analytics by editing a request. Chat sessions on talking-agent widgets get the same fix. Separately, the oEmbed endpoint that Slack, Discord, WordPress, Ghost and Notion call to unfurl a shared widget link now says plainly when a consumer asks for a format we do not publish, instead of returning JSON labelled as the format that was asked for and leaving the embed broken with nothing to explain why.</description>
</item>
+ <item>
+ <title>World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard</title>
+ <link>https://three.ws/world-lines</link>
+ <guid isPermaLink="false">2026-08-15:World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a &quot;Meet the agent in AR&quot; option next to &quot;Begin the encounter&quot;, and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970.</description>
+ </item>
<item>
<title>Your walk keeps syncing across devices, and a remotely driven avatar reports where it really is</title>
<link>https://three.ws/walk</link>
diff --git a/public/features.json b/public/features.json
index 89c26320c..8739aeead 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T19:14:30.709Z",
+ "generated_at": "2026-08-15T19:26:15.578Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",