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): publish the avatar quota entry and land the forge-nim page follow-up
nirholased30e74a4fd6
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex d7df87cd8..dc5cde33d 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -13,7 +13,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Avatar Studio survives an accessory outage, and tells you when it is putting a hat on**: The studio at /avatar-studio was audited end to end in a real browser: loading the base body, all six tabs, the colour swatches, the sculpt sliders, the motion library, undo and redo, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that a single failed request for the accessory catalogue took the entire studio down. The hats, glasses and earrings lists come from one file, and if that file did not load, the page replaced everything with a Retry screen, throwing away the 3D avatar it had already finished loading. Colours, sculpting, animation and saving need nothing from that catalogue, so they all now keep working, and only the three accessory tabs show a message explaining what is missing, with a Retry button that reloads just the catalogue. The Save, Reset, Randomise and Undo buttons were also on screen but not yet connected until that same request finished, so pressing them early did nothing at all and the tab strip sat empty; they are live from the first paint now. Putting on a hat downloads and fits a 3D model, which takes a few seconds, and until now the studio gave no sign it was working: the tile click looked ignored, and a hat that failed to download failed in complete silence. Every accessory change now shows what it is doing and says so plainly if it could not finish. Randomise no longer lists an accessory you are not actually wearing when its model fails to load. Pressing Undo then Redo quickly could leave the avatar and the list of what it is wearing disagreeing with each other; each step now settles correctly. Spinners also finally stop for people who have asked their device to reduce motion. (`/avatar-studio`) `[fix, improvement]`- **Blockchain TVL by Chain is readable again, and its numbers can be copied**: The cross-chain leaderboard at /chains was audited end to end in a real browser: the live DeFiLlama board, the sortable columns, the row links out to each chain's page, and the loading, empty and error states, at phone, tablet and desktop widths. The page had briefly stopped working entirely. Its row-click helpers were declared twice in the same file, which is a syntax error, so the script never ran and the table sat on its grey loading bars forever. That is fixed and covered by a browser test so it cannot come back. Two real defects came out of the same pass. Every row navigated on any click, so dragging across a cell to copy a chain's TVL threw the selection away and opened that chain's page instead; a figure or a name can now be selected and copied, while a plain click still opens the chain. And the page wrapped the site navigation in a second page banner, leaving screen readers with two overlapping banner landmarks to pick between. The share bar beside each chain also stopped reading its percentage aloud a second time, since the dominance column right next to it already says it. (`/chains`) `[fix, improvement]`- **Building an agent no longer throws you out to the login page, and the wizard answers the keyboard**: The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console. (`/create-agent`) `[fix, improvement]`-- **Building an agent no longer throws you out to the login page, and the wizard answers the keyboard**: The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console. (`/create-agent`) `[fix, improvement]`- **Chat stops hiding two nav links, and says something useful when a reply fails**: The chat at /chat was audited end to end in a real browser: loading it cold, sending a message on the free built-in lane and getting a reply back, following every link in the header and footer, and the empty, loading, error and populated states at phone, tablet and desktop widths. The header was covering itself: the centred site links sat on top of the wallet controls, so Features and Docs were partly hidden and could not be clicked at any desktop width, and between tablet and laptop widths there was no way to reach those links at all. The links now sit in the row with everything else, and below the width where they fit they move into the menu. The footer had been shipping a mangled copyright line (a leftover encoding accident that printed stray characters where the copyright symbol belongs). When a reply could not be sent, the thread printed the browser's own words, Failed to fetch; it now says what happened, that nothing was sent, and how to retry, in a message styled as an error rather than as a quieter reply. A rate-limited reply used to say Try again in 79445s; it now says the wait in hours or minutes and, when the free daily allowance is the thing that ran out, points at adding your own provider key. Icon-only buttons across the header and each message (share, model settings, copy, edit, regenerate, delete) now carry names for screen readers, and the page title and description finally describe the page. (`/chat`) `[fix, improvement]`- **Choreographer share links are readable again, and the studio fits a phone**: The gesture composer at /choreograph was audited end to end in a real browser: loading a starter routine, adding and reordering beats, retiming and repointing a step, previewing the whole performance on a live avatar, scrubbing the timeline, sharing a link, and saving to a real agent, at phone, tablet and desktop widths. Copy share link used to hand you a link with the routine name escaped twice, so a routine called The pitch travelled as The%2520pitch: it worked, but it looked broken, and it invited people to tidy it up and break it for real. Links now carry the routine as you can read it, and every link shared before today still opens. A routine whose name ended in the loop marker came back from a link under the wrong name and looping when it should not. On a 320 pixel phone, opening either of the two code panels pushed the whole page sideways; the code block now scrolls on its own instead. Pressing the transport a second time while the first play was still loading its clips said Pause but started a second load; it now stops the one in progress, and deleting the last beat mid-load can no longer bring an avatar back onto a stage the routine has left. Signed-out visitors also no longer see a failed request in the browser console on first paint. (`/choreograph`) `[fix, improvement]`- **Clip Director shows real traders again, and can no longer print a number the trade never made**: The Clip Director page told every visitor that no agent had ever closed a trade. Its trader picker asked the leaderboard for the highest-ranked agents and then kept only the ones with a closed round-trip, and because the ranking score has nothing to do with having closed trades, the nine agents that qualified all sat below the cut. The picker now asks the leaderboard for exactly what it needs, so those nine traders and their real closed positions are back on the page. The bigger repair is underneath: the card copy is written by a language model, and one of the providers answered a real +1.89x win with an invented loss on a different coin, complete with a celebrating avatar, next to the on-chain link proving otherwise. Every generated card is now checked against the trade it describes before it ships, so a ticker or a figure that is not in the round-trip gets the card thrown away and rewritten from the position itself, and a stop-out can never be celebrated. Also on the page: a shared /clip-director?agent_id= link now opens that trader even when they are outside the ranking, the Try again buttons retry the step that actually failed instead of doing nothing, each card's call to action is a real link, and the copy button copies on browsers that block the clipboard API instead of telling you to press a key. (`/clip-director`) `[fix, improvement]`@@ -28,12 +27,14 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Every Crypto Converter result now has its own link you can share**: The converter promised a shareable result and never had one: the address bar stayed on /converter no matter what you picked, so there was no way to hand someone a rate. Now the page reads and writes its own URL. Pick BTC to EUR and type an amount and the address becomes /converter?from=bitcoin&to=EUR&amount=3, a new Copy link button puts that on your clipboard, and opening the link restores both sides and the amount exactly. Alongside that: the asset picker is fully keyboard-driven (arrow keys move the highlight, Enter picks, Escape closes and returns focus to the button you came from), the amount field says what it wants when you type something it cannot use instead of showing a silent dash, a coin whose price failed to load says price unavailable rather than a bare dash, the four quick presets light up when they match what you are looking at and stay disabled until live rates arrive, and the whole widget fits a 320px phone screen, where the currency buttons used to be pushed off the right edge and the picker off the left. (`/converter`) `[feature, improvement, fix]`- **My Collection loads visibly, keeps its counts, and never mangles an agent's name**: The collection page had a loading state nobody could see: the shimmer placeholders were drawn inside a container the page kept hidden until the data had already arrived, so a slow connection got a blank stretch of nothing instead. The tabs, the placeholders and the counts now appear from the first frame. The counts next to Skills and Subscriptions used to vanish at random, because the page's own translation pass could overwrite the tab label a split second after the number was written into it; the count now lives in its own slot and survives. A skill published by an agent whose name contains a quotation mark or an angle bracket rendered as broken markup rather than as the name, and a publisher who earned a vanity wallet address had it shown as an ordinary one, because the card was reading a field the collection endpoint does not return. Both are fixed, so tipping a creator from your collection now shows the wallet they actually have. Empty states are centred under the tabs instead of squeezed into the first column, both of them now point you at the marketplace, the Retry button on a failed load is a real button rather than a raw grey box, and the whole page is keyboard-navigable: arrow keys move between tabs, Home and End jump to the ends, and every link and button shows a clear focus ring. (`/collection`) `[fix, improvement]`- **Pausing a skill bundle is no longer permanent, and every tooltip fits on a phone**: The bundle builder at /bundles was audited end to end in a real browser: signing in, picking priced skills, the price panel and its backtest, publishing, the published list, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that Deactivate was a one-way door. It hid the bundle from buyers, which is correct, but it also removed it from the only page that could put it back, so a misclick permanently retired a bundle you had just priced. The button is now called Pause, a paused bundle stays on the page dimmed and clearly marked, and a Reactivate button puts it back on sale. Buyers still never see a paused bundle: the public list is unchanged, and paused ones are returned only to a signed-in owner of that agent. The small question-mark tooltips that explain every number on the page were also cut off at the edge of a phone screen, so four of the seven explanations were partly unreadable at 320 pixels wide; they now shift to stay on screen at any width. The sum of the parts and the suggested price were cramped into a broken-looking two-line squeeze on a narrow screen and now stack cleanly. Finally, a pricing error raised by one agent no longer sits on screen after you switch to another agent, where it read as a verdict on an agent it had never looked at. (`/bundles`) `[fix, improvement]`+- **Selfie to Avatar tells you your library is full before it spends ninety seconds building**: Five fixes to Selfie to Avatar. If your avatar library was already at the limit for your plan, nothing noticed until the very end: you waited out the full reconstruction, and then the page said the 3D engine had hit a snag and told you to try again. It was not an engine problem, trying again could never work, and every attempt spent another ninety seconds of generation to land in the same place. Your library is now checked the moment you press the button, so a full one is refused immediately with the actual reason and what to do about it, and a build that fills the last slot while it is running ends with that same plain explanation instead of the engine message. The page also stopped losing its own error messages: the Build button floats above the page, so tapping it from higher up left the explanation somewhere below the fold while the button quietly reset itself, which read as nothing having happened. Errors now scroll into view. On the finished-avatar screen, Learn how to embed pointed at a page that did not exist and answered 404; it now opens the embedding guide. And on a narrow phone the Photoreal and Stylized choices were squeezed into two columns barely wide enough for one word per line, so they now stack and can be read. (`/create/selfie`) `[fix, improvement]`- **Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down**: The /create/video page turns one of your avatars plus an audio clip into a lip-synced video, and it was driven end to end in a real browser: every state, every button, every width. The worst finding was invisible from the page. The reference frame the GPU worker renders from was being taken from whatever the browser had handy, which for an avatar with no thumbnail meant its 3D model file. The worker saved that as the reference photo and then failed on it minutes later, after the wait had already been spent. The page now sends only the avatar, and the server resolves a real image for it: the stored thumbnail, or a fresh portrait render when there is none. Second, the GPU renderer is a separate service, and when it is not running the only signal was a failure after you had already picked a file and uploaded it. The page now asks first and, if the lane is down, says so at the top, keeps Generate switched off, and points at the Avatar Studio and prompt-to-avatar in the meantime. The rest is the ordinary polish an audit turns up: a failed avatar list used to look identical to owning no avatars, so it sent people off to create one they already had, and now it says what broke and offers a retry; having no avatars yet gets a real empty state with a link to make one; the Generate button always explains what it is still waiting for and, once audio is in, how many clips of video that audio is worth; the clip you picked can be played back with its length and size before you spend a generation on it; a render job that goes unreachable now says so after thirty seconds instead of spinning for twenty minutes; and after a spent free trial the button under the error no longer stayed stuck on Upgrade plan for every later error. Avatar thumbnails are real buttons with visible focus rings, the two form fields have proper labels, and the second animated avatar that the site companion used to drop onto this page no longer loads over the one you are working on. (`/create/video`) `[fix, improvement]`- **The avatar SDK bundle we ship is now built from the code we deploy**: The <agent-3d> runtime that sites load from three.ws is a single bundled file, and the production build never rebuilt it. It was copied from whatever the build machine happened to have on disk, which could be days older than the code being deployed, so a fix to the avatar element could ship everywhere else on the site and quietly not reach the SDK. The deploy now rebuilds that bundle from the same commit as the rest of the release, every time. Nothing to change on your side: existing embeds keep working and simply pick up the current runtime. (`/avatar-sdk`) `[fix, sdk, infra]`- **The Character Library counts its own characters, and fills the screen while it does**: The library page had been advertising 106 rigged characters since launch. There are 107 on the shelf today, and there will be more tomorrow, so the number is no longer typed into the headline, the page description or the share card: the page asks the library how many it has and prints the answer under the hero. The grid also stopped wasting a third of a desktop screen. A layout rule left the page shrink-to-fitting to about two thirds of the window, so a wide monitor showed three columns where five fit; it now uses the full width it was designed for. Every character card previously carried a hidden second tab stop that announced the same name as the card itself, which made keyboard browsing twice as long as it needed to be, and thumbnails could not be dragged out of alignment by an accidental swipe anymore because the preview no longer pretends to be an interactive 3D control. The search box has a visible focus ring again instead of a one pixel border shift, and when the library cannot be reached the page now says what actually went wrong rather than reverting to a generic sentence a moment later. (`/character-library`) `[fix, improvement]`- **The Characters gallery pages past the first screen, and stops fighting dark mode**: The character gallery at /characters was audited end to end in a real browser: loading the feed, both sort orders, search, Load more, following a card through to its character page, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that the Top sort was quietly broken. Sorting by most-chatted read the right first screen, but pressing Load more asked the server to continue from the wrong place, so the feed ended after eight characters out of more than two thousand. It now pages all the way through, in order. The page also ignored the site theme: it painted a fixed light-blue background under the dark header no matter what you had chosen, which is now fixed in both directions, and wallet addresses on the cards were nearly invisible on a light background everywhere they appear on the site. The gallery filled only a narrow strip down the middle of a desktop screen and now uses the full width, up to four cards across. If the feed failed to load you got one line of grey text and no way to retry; there is now a proper message with a Try again button, a failed Load more keeps the characters you already had, and searching for something with no matches offers to clear the search rather than leaving you at a dead end. Pressing Top while the first screen was still loading used to light up the button and change nothing, so you were left reading New results under a Top heading. The search box had no label for screen readers, the sort buttons never showed which was selected, and neither they nor Load more showed a focus outline for anyone navigating by keyboard. Keyboard users can also now skip the header and land in the gallery. Finally, the feed itself is several times faster to answer on a cold request, because it no longer counts every conversation of every published character just to show you twenty-four of them. (`/characters`) `[fix, improvement]`- **The Community page's live activity feed renders as readable rows again**: The activity list on the Community page was building each row as a link wrapped around another link, which no browser can parse: every entry was torn into three stray fragments, so the creator, the item and its thumbnail landed on separate lines with gaps between them and the whole list was unreadable. Rows are now single, valid entries again: click anywhere on one to open the creation, or click the creator's name to open their profile. If the feed cannot load, or returns something the page cannot read, you get a clear message and a Try again button instead of skeleton placeholders that never resolve. The page also follows the light and dark theme switch now instead of staying black on a light canvas, and the newsletter section finally has the signup field its text promises, rather than sending you hunting for the one in the footer. (`/community`) `[fix, improvement]`- **The Concierge page stops cutting itself off on a phone, and its install tabs work from the keyboard**: Three fixes to the Concierge landing page. On a narrow phone screen the whole page was being sized against the longest line of the install snippet, which pushed the column roughly twice as wide as the screen; because the site clips sideways overflow, the right-hand half of every headline, paragraph and button was simply cut off with no way to scroll to it. The column now fits the screen and the code snippet scrolls inside its own box, the way it already did on a laptop. The four install tabs (one tag, web component, npm, imperative) announced themselves to a screen reader as tabs but were not wired to the panels they open and ignored the arrow keys; they now move with Left, Right, Home and End, and each tab is properly tied to its snippet. Copy buttons also say which snippet they copy, and if the browser blocks the clipboard the snippet is selected for you so Ctrl+C still works. Finally, the passive "Have you tried" suggestion card could land on top of the live concierge demo in the corner; it now stacks clear of it. (`/concierge`) `[fix, improvement]`+- **The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it**: Two ways the front door for creating could strand you are gone. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says "Coming soon" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image. (`/create`) `[fix, improvement]`- **The Pole Club leaderboard now ranks the dancers who are actually on the poles**: The club's leaderboard was reading names out of the payout registry instead of off the stage, so it listed four dancers under names matching none of the three at the poles, every one of them sitting at zero. It now names each dancer exactly as her pole card does, drops entries for dancers who are not in tonight's lineup and have never been tipped, and says what a quiet board actually means: the 24h and 1h views tell you the club has been quiet rather than claiming nobody has ever tipped, which was never true while the all-time board was full. Keyboard and screen-reader visitors get the rest of the pass: the page carries one real heading instead of five competing ones, Skip to stage now lands you on the stage, and the controls belonging to the walk-in (the agent picker, the Enter the club prompt) no longer sit invisibly in the tab order once you are inside the room. (`/club`) `[fix, improvement]`- **The security agent in the world no longer opens its scanner in your face**: zauth, the security agent standing in the town plaza, used to throw its RepoScan panel over the screen the moment you walked within a few metres of it, interrupting whatever you were doing and hiding the world behind a modal you never asked for. Walking up now only gets you the agent's line and the usual E prompt above its head. The scanner opens when you choose to open it: press E, click the agent, or click its nameplate. Nothing else changed about the scan itself, and the price is still fetched live from zauth in the background as you approach, so the panel shows the real cost the instant it opens instead of a loading shimmer. (`/play`) `[fix, improvement]`- **The viewer's backdrop picker stops vanishing while you read it, and sharing no longer posts "Meet Agent"**: Five fixes to the 3D model viewer at /app. Opening the Backdrop picker and taking a few seconds to read the six choices used to make the picker fade out from under the cursor: the viewer hides its controls after five seconds of stillness, and the picker was not on the list of surfaces that keep them awake, so an open picker went invisible and unclickable while still counting as open. It now stays put until you choose a backdrop or close it, and the controls resume fading once it is shut. Typing in the animation search while the clips were still loading stacked a second, contradictory message under the first, so the panel read "Loading clips" and "No clips matching" at the same time, and clearing the box left behind the nonsense line "No clips matching" with nothing in the quotes; the search now stays quiet until there are clips to search. Sharing the viewer to X, Farcaster or Telegram published "Meet Agent", an internal placeholder name, for anyone who had not loaded an agent of their own, and now uses the generic line instead. The page also shipped a sign-in panel and a welcome card that its own stylesheet blanked unconditionally, four links nobody could ever reach, and the preview card shown when the page is shared described the platform instead of the viewer. The avatar gallery behind the Avatar button is now announced to screen readers as a named dialog. (`/app`) `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex 0a05022ab..4aafff66f 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,26 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-08-17",+ "title": "The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it",+ "summary": "Two ways the front door for creating could strand you are gone. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says \"Coming soon\" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/create"+ },+ {+ "date": "2026-08-17",+ "title": "Selfie to Avatar tells you your library is full before it spends ninety seconds building",+ "summary": "Five fixes to Selfie to Avatar. If your avatar library was already at the limit for your plan, nothing noticed until the very end: you waited out the full reconstruction, and then the page said the 3D engine had hit a snag and told you to try again. It was not an engine problem, trying again could never work, and every attempt spent another ninety seconds of generation to land in the same place. Your library is now checked the moment you press the button, so a full one is refused immediately with the actual reason and what to do about it, and a build that fills the last slot while it is running ends with that same plain explanation instead of the engine message. The page also stopped losing its own error messages: the Build button floats above the page, so tapping it from higher up left the explanation somewhere below the fold while the button quietly reset itself, which read as nothing having happened. Errors now scroll into view. On the finished-avatar screen, Learn how to embed pointed at a page that did not exist and answered 404; it now opens the embedding guide. And on a narrow phone the Photoreal and Stylized choices were squeezed into two columns barely wide enough for one word per line, so they now stack and can be read.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/create/selfie"+ },{"date": "2026-08-17","title": "Trial Conversions: the Buy button lands on the right skill, and Edit pricing stops going nowhere",@@ -24344,16 +24364,6 @@"improvement"],"link": "/create/video"- },- {- "date": "2026-08-17",- "title": "Building an agent no longer throws you out to the login page, and the wizard answers the keyboard",- "summary": "The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console.",- "tags": [- "fix",- "improvement"- ],- "link": "/create-agent"}]}diff --git a/pages/forge-nim.html b/pages/forge-nim.htmlindex 1757a986d..de7e18e41 100644--- a/pages/forge-nim.html+++ b/pages/forge-nim.html@@ -902,6 +902,7 @@// disabled and the stage explains how to point it at a NIM instead.hasEndpoint: false,healthSeq: 0,+ stage: 'idle',};// ── Health ────────────────────────────────────────────────────@@ -928,13 +929,22 @@}if (seq !== state.healthSeq) return;- state.hasEndpoint = Boolean(override) || Boolean(d.configured);- if (!d.configured && !override) {+ // A rejected override answers from the env instead of the box, and says so+ // via `reason` with no masked baseUrl echoed back. Treat it as no endpoint+ // rather than letting the composer promise a POST that can only 400.+ const overrideRejected = Boolean(override) && !d.baseUrl;+ state.hasEndpoint = overrideRejected ? Boolean(d.configured) : Boolean(override) || Boolean(d.configured);++ if (overrideRejected) {+ setStatus('down', 'Endpoint rejected');+ } else if (!d.configured && !override) {setStatus('off', 'No NIM wired');} else if (d.reachable) {setStatus('live', override ? 'Endpoint ready' : 'NIM ready');} else {- setStatus('down', override ? 'Endpoint unreachable' : 'NIM unreachable');+ // A NIM behind a gateway may refuse /v1/health/ready yet serve /v1/infer,+ // so unreachable warns without locking the composer.+ setStatus('down', override ? 'Ready check failed' : 'NIM unreachable');}applyEndpointState();}@@ -1043,12 +1053,34 @@els.prompt.addEventListener('input', updateGenerateEnabled);function updateGenerateEnabled() {- const ready =+ const hasInput =state.mode === 'image' ? Boolean(state.imageDataUri) : els.prompt.value.trim().length >= 3;- els.generate.disabled = !ready;+ els.generate.disabled = !hasInput || !state.hasEndpoint;+ els.generate.title = state.hasEndpoint+ ? ''+ : 'No NIM endpoint yet. Add one under "NIM endpoint & wire contract".';}updateGenerateEnabled();+ // ── Endpoint override ─────────────────────────────────────────+ // Typing a base URL re-probes THAT box, so the pill and the composer describe+ // the endpoint the next POST will actually hit, not the deployment default.+ let baseUrlTimer = null;+ function scheduleHealth() {+ clearTimeout(baseUrlTimer);+ baseUrlTimer = setTimeout(() => checkHealth(els.baseUrl.value), 600);+ }+ els.baseUrl.addEventListener('input', scheduleHealth);+ els.baseUrl.addEventListener('change', () => {+ clearTimeout(baseUrlTimer);+ checkHealth(els.baseUrl.value);+ });+ els.setEndpoint.addEventListener('click', () => {+ els.advanced.open = true;+ els.baseUrl.focus();+ els.baseUrl.scrollIntoView({ block: 'center', behavior: 'smooth' });+ });+// ── Samples ───────────────────────────────────────────────────els.sampleRow.addEventListener('click', (e) => {const btn = e.target.closest('button[data-sample]');@@ -1067,7 +1099,15 @@els.stateError.classList.toggle('show', name === 'error');els.stateUnconfigured.classList.toggle('show', name === 'unconfigured');els.viewer.style.display = name === 'result' ? 'block' : 'none';- if (name !== 'result') els.resultBar.classList.add('is-hidden');+ if (name !== 'result') {+ els.resultBar.classList.add('is-hidden');+ els.download.hidden = true;+ }+ }+ // "Back to start" always lands on the state that is actually true right now:+ // the idle prompt when an endpoint exists, the setup card when none does.+ function showRest() {+ showState(state.hasEndpoint ? 'idle' : 'unconfigured');}function showError(title, msg) {els.errorTitle.textContent = title;@@ -1106,11 +1146,20 @@e.preventDefault();generate();});- els.errorRetry.addEventListener('click', generate);+ els.errorRetry.addEventListener('click', () => {+ // Retrying with no endpoint would fail identically, so send the user to the+ // one action that can fix it instead of replaying the same 503.+ if (!state.hasEndpoint) {+ showState('unconfigured');+ els.setEndpoint.focus();+ return;+ }+ generate();+ });els.cancel.addEventListener('click', () => {state.abort?.abort();stopTimers();- showState('idle');+ showRest();});async function generate() {@@ -1141,7 +1190,10 @@});const d = await r.json().catch(() => ({}));if (!r.ok || !d.ok) {- throw new Error(d.message || d.error || `Request failed (${r.status})`);+ // The API's boundary errors carry the human sentence in+ // `error_description`; `error` is only the machine code, so reading it+ // first showed the user a bare `nim_unconfigured` instead of the reason.+ throw new Error(d.error_description || d.message || d.error || `Request failed (${r.status})`);}renderResult(d);} catch (err) {@@ -1164,6 +1216,7 @@state.objectUrl = URL.createObjectURL(blob);els.viewer.src = state.objectUrl;els.download.href = state.objectUrl;+ els.download.hidden = false;showState('result');const kb = (d.bytes / 1024).toFixed(0);@@ -1196,7 +1249,7 @@});setMode('image');- checkHealth();+ checkHealth(els.baseUrl.value);</script><!-- Runtime i18n: detects locale, swaps annotated copy, mounts <lang-switcher>. --><script type="module" src="/i18n.js"></script>diff --git a/public/changelog.json b/public/changelog.jsonindex e604ff781..098231289 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T04:47:06.239Z",+ "generated_at": "2026-08-17T04:49:46.210Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -81,17 +81,6 @@"improvement"]},- {- "date": "2026-08-17",- "type": "update",- "title": "Building an agent no longer throws you out to the login page, and the wizard answers the keyboard",- "summary": "The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console.",- "link": "/create-agent",- "tags": [- "fix",- "improvement"- ]- },{"date": "2026-08-17","type": "update",@@ -246,6 +235,17 @@"improvement"]},+ {+ "date": "2026-08-17",+ "type": "update",+ "title": "Selfie to Avatar tells you your library is full before it spends ninety seconds building",+ "summary": "Five fixes to Selfie to Avatar. If your avatar library was already at the limit for your plan, nothing noticed until the very end: you waited out the full reconstruction, and then the page said the 3D engine had hit a snag and told you to try again. It was not an engine problem, trying again could never work, and every attempt spent another ninety seconds of generation to land in the same place. Your library is now checked the moment you press the button, so a full one is refused immediately with the actual reason and what to do about it, and a build that fills the last slot while it is running ends with that same plain explanation instead of the engine message. The page also stopped losing its own error messages: the Build button floats above the page, so tapping it from higher up left the explanation somewhere below the fold while the button quietly reset itself, which read as nothing having happened. Errors now scroll into view. On the finished-avatar screen, Learn how to embed pointed at a page that did not exist and answered 404; it now opens the embedding guide. And on a narrow phone the Photoreal and Stylized choices were squeezed into two columns barely wide enough for one word per line, so they now stack and can be read.",+ "link": "/create/selfie",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-17","type": "update",@@ -313,6 +313,17 @@"improvement"]},+ {+ "date": "2026-08-17",+ "type": "update",+ "title": "The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it",+ "summary": "Two ways the front door for creating could strand you are gone. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says \"Coming soon\" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image.",+ "link": "/create",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-17","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 23a3a7c3f..310923a6d 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -62,14 +62,6 @@<category>fix</category><description>The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console.</description></item>- <item>- <title>Building an agent no longer throws you out to the login page, and the wizard answers the keyboard</title>- <link>https://three.ws/create-agent</link>- <guid isPermaLink="false">2026-08-17:Building an agent no longer throws you out to the login page, and the wizard answers the keyboard</guid>- <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>- <category>fix</category>- <description>The six-step agent builder at /create-agent was audited end to end in a real browser: naming an agent, generating a whole spec from one sentence, choosing a body from the starter library, the skills and personality steps, the voice step, and the review screen, plus the loading, empty and error states at phone, tablet and desktop widths. The worst finding was that the wizard broke its own promise. It is built so anyone can construct an entire agent before making an account, and sign in only at the final step where the agent gets its wallet. But opening the My avatars tab without an account threw the visitor straight out to the login page, mid-build, with no warning and no explanation, because that tab asked for avatars you can only have if you are signed in. It now recognises a visitor who has no account, says so in the tab, and points at the Starter library and Upload tabs, which both work without one, alongside a Sign in button that saves the build first so nothing is lost either way. The step markers across the top of the wizard could only be used with a mouse. They are the only way back to an earlier step from the review screen, so anyone working by keyboard reached the end of the flow with no way to correct anything; they are now real buttons that take focus, show a focus ring, and respond to Enter and Space, with the completed steps marked as such for screen readers. The four tabs on the body step also announced themselves as tabs without ever telling a screen reader which panel each one opens, and left the arrow keys dead; the arrow keys, Home and End now move between them the way tabs are meant to work. Finally, a first-time visitor generating an agent from a description no longer sees a failed request in the browser console.</description>- </item><item><title>Chat stops hiding two nav links, and says something useful when a reply fails</title><link>https://three.ws/chat</link>@@ -182,6 +174,14 @@<category>fix</category><description>The bundle builder at /bundles was audited end to end in a real browser: signing in, picking priced skills, the price panel and its backtest, publishing, the published list, and the loading, empty and error states, at phone, tablet and desktop widths. The worst finding was that Deactivate was a one-way door. It hid the bundle from buyers, which is correct, but it also removed it from the only page that could put it back, so a misclick permanently retired a bundle you had just priced. The button is now called Pause, a paused bundle stays on the page dimmed and clearly marked, and a Reactivate button puts it back on sale. Buyers still never see a paused bundle: the public list is unchanged, and paused ones are returned only to a signed-in owner of that agent. The small question-mark tooltips that explain every number on the page were also cut off at the edge of a phone screen, so four of the seven explanations were partly unreadable at 320 pixels wide; they now shift to stay on screen at any width. The sum of the parts and the suggested price were cramped into a broken-looking two-line squeeze on a narrow screen and now stack cleanly. Finally, a pricing error raised by one agent no longer sits on screen after you switch to another agent, where it read as a verdict on an agent it had never looked at.</description></item>+ <item>+ <title>Selfie to Avatar tells you your library is full before it spends ninety seconds building</title>+ <link>https://three.ws/create/selfie</link>+ <guid isPermaLink="false">2026-08-17:Selfie to Avatar tells you your library is full before it spends ninety seconds building</guid>+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Five fixes to Selfie to Avatar. If your avatar library was already at the limit for your plan, nothing noticed until the very end: you waited out the full reconstruction, and then the page said the 3D engine had hit a snag and told you to try again. It was not an engine problem, trying again could never work, and every attempt spent another ninety seconds of generation to land in the same place. Your library is now checked the moment you press the button, so a full one is refused immediately with the actual reason and what to do about it, and a build that fills the last slot while it is running ends with that same plain explanation instead of the engine message. The page also stopped losing its own error messages: the Build button floats above the page, so tapping it from higher up left the explanation somewhere below the fold while the button quietly reset itself, which read as nothing having happened. Errors now scroll into view. On the finished-avatar screen, Learn how to embed pointed at a page that did not exist and answered 404; it now opens the embedding guide. And on a narrow phone the Photoreal and Stylized choices were squeezed into two columns barely wide enough for one word per line, so they now stack and can be read.</description>+ </item><item><title>Talking Avatar Video stops handing the renderer a 3D file where a photo belongs, and says up front when the GPU lane is down</title><link>https://three.ws/create/video</link>@@ -230,6 +230,14 @@<category>fix</category><description>Three fixes to the Concierge landing page. On a narrow phone screen the whole page was being sized against the longest line of the install snippet, which pushed the column roughly twice as wide as the screen; because the site clips sideways overflow, the right-hand half of every headline, paragraph and button was simply cut off with no way to scroll to it. The column now fits the screen and the code snippet scrolls inside its own box, the way it already did on a laptop. The four install tabs (one tag, web component, npm, imperative) announced themselves to a screen reader as tabs but were not wired to the panels they open and ignored the arrow keys; they now move with Left, Right, Home and End, and each tab is properly tied to its snippet. Copy buttons also say which snippet they copy, and if the browser blocks the clipboard the snippet is selected for you so Ctrl+C still works. Finally, the passive "Have you tried" suggestion card could land on top of the live concierge demo in the corner; it now stacks clear of it.</description></item>+ <item>+ <title>The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it</title>+ <link>https://three.ws/create</link>+ <guid isPermaLink="false">2026-08-17:The Create page no longer black-screens when the sign-in check stalls, and a broken remix link no longer kills every button on it</guid>+ <pubDate>Mon, 17 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Two ways the front door for creating could strand you are gone. The page opens behind a full-screen loading screen while it checks whether you are signed in; if that check got no answer at all (a stalled connection rather than a refused one) the screen stayed black forever and the page read as dead. It now hands the page back after a short wait and treats you as signed out, which costs at most one extra trip through sign-in. Separately, opening a remix link for an avatar that had been deleted or made private used to show a message for four seconds and then leave you on a page where not one of the eight creation cards did anything: the remix ran before the buttons were wired and gave up without wiring them. The cards are live first now, and a failed remix explains itself in a panel that stays put, with a button to try again and a button to move on. Also: the talking-avatar-video card now says "Coming soon" on the card itself instead of only dimming, answers the keyboard the same way it answers a mouse, and stops calling itself unavailable when the check simply could not reach us (it asks again when you click). A saved avatar whose thumbnail has been deleted falls back to a silhouette instead of a broken image.</description>+ </item><item><title>The Pole Club leaderboard now ranks the dancers who are actually on the poles</title><link>https://three.ws/club</link>diff --git a/public/features.json b/public/features.jsonindex f1ca0d88d..7cf4d1eec 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-17T04:47:06.058Z",+ "generated_at": "2026-08-17T04:49:46.030Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/src/economy-lab.css b/src/economy-lab.cssindex 842b45c48..e0cf15a26 100644--- a/src/economy-lab.css+++ b/src/economy-lab.css@@ -308,7 +308,8 @@display: flex;align-items: center;justify-content: space-between;- gap: 0.75rem;+ flex-wrap: wrap;+ gap: 0.5rem 0.75rem;margin-bottom: 1rem;}.el-panel-head h2 { font-size: 1rem; font-weight: 650; }@@ -515,7 +516,9 @@/* ── Chart ─────────────────────────────────────────────────────────────── */.el-panel-chart { min-width: 0; }-.el-legend { display: flex; gap: 0.85rem; font-size: 0.76rem; color: var(--el-muted); }+/* Wraps rather than running off the panel: at 320px the three series names do+ not fit on one line beside the heading, and the last one was clipped. */+.el-legend { display: flex; flex-wrap: wrap; gap: 0.4rem 0.85rem; font-size: 0.76rem; color: var(--el-muted); }.el-legend-item { display: inline-flex; align-items: center; gap: 0.35rem; }.el-legend-item::before {content: '';diff --git a/src/economy-lab.js b/src/economy-lab.jsindex 7c1ef891f..cf6e32a7f 100644--- a/src/economy-lab.js+++ b/src/economy-lab.js@@ -489,8 +489,10 @@ function drawChart(series, knobs) {const padL = narrow ? 42 : 58;const padR = narrow ? 34 : 52;- const padT = 16;- const padB = 28;+ // Room above the plot for the axis unit captions, which used to be drawn+ // inside it and landed straight on top of the first gridline label.+ const padT = 26;+ const padB = 30;const w = cssW - padL - padR;const h = cssH - padT - padB;if (w <= 0 || h <= 0 || !series.length) return;@@ -501,11 +503,14 @@ function drawChart(series, knobs) {const yBal = (v) => padT + h - (v / maxBal) * h;const yCount = (v) => padT + h - (v / maxCount) * h;- // Grid+ // Grid. Tick precision is derived from the range being plotted: a fee wallet+ // holding 0.0023 SOL rendered every one of its five gridlines as "0.002" or+ // "0.001" at a fixed three decimals, which is an axis that cannot be read.ctx.strokeStyle = line;ctx.lineWidth = 1;ctx.font = '11px ui-sans-serif, system-ui, sans-serif';ctx.fillStyle = faint;+ const solDigits = axisSolDigits(maxBal);for (let g = 0; g <= 4; g++) {const yy = padT + (h / 4) * g;ctx.beginPath();@@ -513,25 +518,38 @@ function drawChart(series, knobs) {ctx.lineTo(padL + w, yy);ctx.stroke();ctx.textAlign = 'right';- ctx.fillText(`${fmtSol(maxBal * (1 - g / 4), 3)}`, padL - 8, yy + 4);+ ctx.fillText(fmtSol(maxBal * (1 - g / 4), solDigits), padL - 8, yy + 4);ctx.textAlign = 'left';ctx.fillText(fmtInt(maxCount * (1 - g / 4)), padL + w + 8, yy + 4);}- // UTC midnight markers+ // Axis captions, in the gutter above the plot so they cannot sit on a tick.+ ctx.fillStyle = faint;+ ctx.textAlign = 'left';+ ctx.fillText('SOL', 6, 13);+ ctx.textAlign = 'right';+ ctx.fillText('settles/h', cssW - 6, 13);++ // UTC midnight markers. Labelled in the bottom gutter: inside the plot the+ // caption landed on top of the columns it was meant to annotate.const startHour = seed?.meter?.utc_hour ?? 0;ctx.save();ctx.setLineDash([2, 4]);ctx.strokeStyle = faint;+ let lastMarkerX = -Infinity;for (let i = 0; i < series.length; i++) {if ((startHour + i) % 24 !== 0 || i === 0) continue;ctx.beginPath();ctx.moveTo(x(i), padT);ctx.lineTo(x(i), padT + h);ctx.stroke();+ // Skip a caption that would collide with the previous one: a 14-day+ // horizon on a phone puts midnights 15px apart.+ if (x(i) - lastMarkerX < 46) continue;+ lastMarkerX = x(i);ctx.fillStyle = faint;ctx.textAlign = 'center';- ctx.fillText('00 UTC', x(i), padT + 10);+ ctx.fillText('00 UTC', x(i), padT + h + 15);}ctx.restore();@@ -564,9 +582,19 @@ function drawChart(series, knobs) {ctx.lineTo(padL + w, yBal(knobs.floorLamports));ctx.stroke();ctx.restore();+ // The label rides on a chip of the panel background. Bare text sat directly+ // on the refusal columns, which is precisely the case where the floor line+ // matters most and was least readable.+ const floorY = yBal(knobs.floorLamports);+ const floorLabel = 'hard floor';+ const labelW = ctx.measureText(floorLabel).width;+ const above = floorY - padT > 16;+ const chipY = above ? floorY - 15 : floorY + 3;+ ctx.fillStyle = col('--el-surface-2', '#111420');+ ctx.fillRect(padL + 3, chipY, labelW + 8, 13);ctx.fillStyle = danger;ctx.textAlign = 'left';- ctx.fillText('hard floor', padL + 4, yBal(knobs.floorLamports) - 5);+ ctx.fillText(floorLabel, padL + 7, chipY + 10);// Balance area + linectx.beginPath();@@ -590,13 +618,20 @@ function drawChart(series, knobs) {ctx.strokeStyle = info;ctx.lineWidth = 2;ctx.stroke();+}- // Axis labels- ctx.fillStyle = faint;- ctx.textAlign = 'left';- ctx.fillText('SOL', 6, padT + 10);- ctx.textAlign = 'right';- ctx.fillText('settles/h', cssW - 6, padT + 10);+// Decimals an axis tick needs for five gridlines over `maxLamports` to read as+// five different numbers. A rail's balance spans nine orders of magnitude+// between a funded wallet and a starved one, so a fixed precision is wrong at+// one end or the other.+function axisSolDigits(maxLamports) {+ const span = Math.abs(Number(maxLamports) || 0) / LAMPORTS_PER_SOL;+ if (span >= 10) return 1;+ if (span >= 1) return 2;+ if (span >= 0.1) return 3;+ if (span >= 0.01) return 4;+ if (span >= 0.001) return 5;+ return 6;}function hexWithAlpha(color, alpha) {