Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(capabilities): keep the row action and the section header usable on a phone
nirholas1e7d080c7bcc
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 18a8bf7e2..185c43edd 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,17 +10,21 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Docs · The $THREE thesis** (`/docs/three-thesis`): The long-form case for $THREE: what three.ws is, every utility and sink the token has, how platform revenue routes into buybacks, where it trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself.- **Docs · The First 19 Weeks** (`/docs/the-first-19-weeks`): The founding three.ws roundup: a week-by-week record of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch, partnership, announcement, and where $THREE fits.- **Billing & Passes names your creators, keeps its retry buttons live, and the dashboard fits a phone screen**: On /dashboard/billing, creator subscriptions now show the creator's name (linked to their profile), the real renewal or end date, a colour-coded status, and the plan price with its interval, instead of a raw account id. When the passes or subscriptions feed cannot be reached, the Retry button now actually reloads that section. Across every dashboard page, the top bar no longer forces the layout wider than a 320px phone screen, so nothing is clipped off the right edge. (`/dashboard/billing`) `[fix, improvement]`+- **Capabilities stops reporting an empty dashboard when the API is the thing that failed**: The Capabilities command center used to ask the API once per agent for launcher and market-maker data, which on a real roster tripped the rate limiter mid-load. The failed calls were silently discarded and the page rendered a confident all-zero dashboard for an account that had launchers, coins and live markets. It now reads each capability for the whole account in a single call, so the request count no longer grows with your roster, and any lane that does fail says so in place with a working Retry instead of showing a zero. The 30-second refresh also stops resetting the tab you were reading and no longer replaces a Launch Now or Claim button while its request is still in flight, and on a phone the row action stays pinned in view instead of scrolling off the right edge. (`/dashboard/capabilities`) `[fix, improvement]`- **Compare reads correctly on a phone and stops mislabelling gains and losses**: The side-by-side coin comparison had three problems worth fixing. Percentage rows rendered every number the same neutral colour, so a loss looked like a gain unless it happened to be the row winner, and the winning cell was painted green even when it was a 37% drawdown; gains are now green, losses red, and the row winner is marked by weight and a tint that reads on either. The performance overlay gained date labels along its bottom edge, and on a phone it now draws at the width of the screen instead of shrinking a desktop-sized chart to a third of its height with unreadable text. Switching range fast could also leave a year of history drawn under a 7-day label; the chart now ignores a slow answer that a newer range has already replaced. (`/compare`) `[fix, improvement]`- **Connect X no longer dead-ends when X sign-in is switched off**: Seeding an agent's memory from X starts by connecting your X account, and on a deployment where X sign-in is not switched on every Connect X button led to a page of raw error text with no way back. Those buttons now say X connections are not enabled and why, in the agent editor's Social tab and the avatar editor's X panel as well as in Settings, and following an old connect link lands you back on the page you started from with the reason stated instead of stranding you. Nothing about consent, seeding, or revocation changes. (`/settings`) `[fix]`- **Creator Gallery cards stay put while you scroll, and the leaderboards show they are loading**: On /creations, the 3D preview on every gallery card and leaderboard row was accidentally accepting drag input, so a card could be flung out of frame and a swipe over one scrolled nothing on a phone instead of moving the feed. The previews now spin on their own and hand the drag back to the page. The trending and top-creator columns also render shimmer rows while they load instead of sitting blank, the browse tally no longer shows a stale number over a loading grid, and keyboard focus on the search field is now clearly outlined. (`/creations`) `[fix, improvement]`- **Credits shows your $THREE discount tier, and no longer goes blank when it cannot load**: The Credits page had a hole where its error state should be: if the balance request failed, every panel disappeared and the page ended below the heading with nothing on it. There is now a designed card that says what happened, links to platform status, and retries in one click, and a dropped connection reads as a real sentence instead of the browser's "Failed to fetch". The page also finally states the thing it promises: a pill showing the $THREE tier you are actually charged at, with the discount you are getting or how much more $THREE reaches the next tier. On a 320px phone the whole layout used to be a hundred pixels wider than the screen with the right edge silently cut off, so nothing over there was reachable; the page now fits, and the history table scrolls inside its own box. Smaller fixes throughout: every button and field has a visible keyboard focus ring, the deposit address has a copy button, the $THREE unit price shows real decimals instead of rounding to $0.00, the amount field and the history controls stay translated when you switch asset or load another page, and the price list dropped the dashes from its labels. (`/credits`) `[fix, improvement]`- **Crew HQ keeps its 3D room standing, and crew links now open where they point**: Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's "Failed to fetch". (`/crews`) `[fix, improvement]`+- **Dashboard Account fits a phone screen, and it stops claiming you own no .sol domains when it could not check**: On a 320px phone every card on the account page ran past the right edge of the screen, which put Sign out, the AI provider key fields, Link wallet, and the quick links out of reach with no way to scroll to them; the cards now fit and every control is reachable. The SNS panel used to answer a resolver outage with "No primary .sol domains found", telling you to go register a domain you may already own. It now says plainly that the lookup failed and offers a retry, and when only some of your wallets could be checked it says how many were missed instead of quietly counting them as empty. The panel also refreshes itself when you link, disconnect, or re-prioritise a wallet, rather than sitting on a stale answer until you reload. The delegation table says how many agents it is showing out of your total instead of silently listing the first eight, and the page finally carries a search description of what it holds: profile, wallets, domains, delegation, provider keys, and the audit trail. (`/dashboard/account`) `[fix, improvement]`- **Dashboard Analytics fits a phone screen and its failure page can actually reload**: On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare failure page showed a Reload button that did nothing when tapped, so it now reloads, and it explains what happened in plain language with a link to support instead of only printing a developer error string. A malformed response from one of the services behind the page no longer blanks the whole dashboard: the panel that depends on it degrades on its own and the rest still draws. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance. (`/dashboard/analytics`) `[fix, improvement]`- **Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme**: Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more. (`/create/prompt`) `[fix, improvement]`- **Text-to-3D no longer hangs when the concept painter stalls**: Every text-to-3D generation starts by painting a concept image, and that step tried its image providers one after another with no overall time limit. When the first provider stalled, a request could sit for two and a half minutes before answering, and anything with a shorter patience (ChatGPT, agent clients) simply saw nothing. The painter now works to one shared budget: a slow provider hands off with real time left for the next one, and if the whole chain runs out you get a quick, honest retry-in-a-moment answer instead of a hang. Image-to-3D was never affected. (`/forge`) `[fix]`+- **The Data API console keeps working when one of its services is down, and its corpus numbers are now live**: The developer console at Dashboard > Data API is fed by three separate services, and any one of them failing used to take the whole page down: a pricing outage left a single error card where the pass status, the API key table, the quickstarts, and the endpoint list should have been, and a pass-status hiccup left a loading shimmer that never resolved. Each card now fails on its own with an explanation and a retry, and everything else stays usable. Status messages appear next to the control that produced them, so a key rotation error no longer lands in the pricing card several screens away. The copyable quickstarts stopped pasting a shortened version of your key into commands that could only ever be rejected; they now carry a clearly marked placeholder, or the real key in the moment it is minted. Copy buttons say so honestly when the browser refuses the clipboard instead of claiming success. The article and publisher-feed counts are read from the archive itself rather than typed into the page, so they no longer drift, and the tables and code blocks can be scrolled with the keyboard. (`/dashboard/data-api`) `[fix, improvement]`- **The First 19 Weeks: everything shipped since day one, week by week**: The First 19 Weeks, the founding three.ws roundup, walks every week from the first commit on April 14 to today: what launched, what was announced, which partnerships landed, and where $THREE fits, with the totals (commits, changelog entries, pages, packages, MCP servers, listings) up front. It is written for the timeline, so no tables, and ships with a screenshot kit of the live surfaces. (`/docs/the-first-19-weeks`) `[docs]`- **The first-contribution guide now hands you real open work, and the docs sidebar can find it**: The 15-minute contributor guide walked through adding MikuMikuDance rig support as its example, but that support had already shipped, so anyone following it literally would have re-done merged work and been told a bone was unmapped when it was not. It now shows the MMD change as the finished reference, exactly as it landed with its tests, and points you at two rig conventions that are genuinely still open, each with the bones that fail today. The community, triage, and first-contribution pages also appear in the docs sidebar under Guides instead of being reachable only from the README, and the triage page now explains every label the repo actually uses. (`/docs/first-contribution`) `[docs, fix]`- **The full $THREE thesis is now a single document**: A long-form research thesis on $THREE now lives in the docs: what three.ws is, every way the token is used (hold-to-access tiers, plan and pass discounts, marketplace and labor escrow, game cosmetics, gated embeds, deploy-fee waivers), how platform revenue is routed into buybacks, where the token trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself, each claim sourced to the code. (`/three-token`) `[docs]`+- **The market tools now clear the WCAG AA contrast floor**: An accessibility sweep of the compare page found four places where text did not have enough contrast against what sat behind it. The selected time-range button, the rank badge, and the heatmap's view switcher all put white on a blue too light to read; they now use a blue and a text colour chosen to clear the standard in both the light and the dark theme. The comparison table's green was too pale on a white background, the coin column headings were painted in their chart-line colour (worst of all for the amber series), and the Getting started pill's counter borrowed a colour meant for light backgrounds while sitting on a dark one. Every one of those is fixed, and the column headings keep their tie to the chart through a coloured rule under each symbol. (`/compare`) `[fix, improvement]`- **three.ws crossed 100 stars on GitHub**: The open-source repo behind three.ws passed 100 GitHub stars: 9,508 commits from 21 contributors, 101 npm packages under @three-ws, 72 MCP servers in the official registry, 4,519 x402 endpoints with 110,416 on-chain settlements, and 3,000 validator attestations on Solana. Thank you for building with us. `[docs]`## 2026-08-24diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 4fcd36ae7..ada92a1f5 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -185,6 +185,7 @@ bottom.| Economy wallet registry + rotation | schema [api/_lib/migrations/20260819010000_economy_wallet_registry.sql](api/_lib/migrations/20260819010000_economy_wallet_registry.sql), operator script [scripts/economy-wallets.mjs](scripts/economy-wallets.mjs) (`npm run economy:wallets`), runbook [docs/ops/economy-wallet-rotation.md](docs/ops/economy-wallet-rotation.md) | Live | A durable log of every wallet each economy role has ever held, with lineage between them. [api/_lib/solana-signers.js](api/_lib/solana-signers.js) says what the economy uses now; rotating a signer overwrote an env var and the previous address survived nowhere, so reconciling an old settle meant guessing on-chain. `economy_wallet_registry` keeps one active wallet per role (enforced by a partial unique index, so a half-finished rotation cannot be left behind) plus the full retired history. Generates fresh vanity-prefixed keypairs, writes the secret to a 0600 file outside the repo, and prints the funding and cutover steps; it never stores secret material and never installs a key into production itself. || Earned autonomy (sniper fleet) | tier engine [api/_lib/sniper-autonomy.js](api/_lib/sniper-autonomy.js), tier-scaled optimizer [api/_lib/sniper-optimizer.js](api/_lib/sniper-optimizer.js) + cron [api/cron/sniper-optimize.js](api/cron/sniper-optimize.js), tier-weighted portfolio layer [scripts/sniper-evolve.mjs](scripts/sniper-evolve.mjs) + cron [api/cron/sniper-evolve.js](api/cron/sniper-evolve.js), judge knowledge pack [workers/agent-sniper/judge-knowledge.js](workers/agent-sniper/judge-knowledge.js) → [workers/agent-sniper/llm-judge.js](workers/agent-sniper/llm-judge.js), board [api/sniper/experiments.js](api/sniper/experiments.js) + [src/sniper-experiments.js](src/sniper-experiments.js) `→ /sniper/experiments` | Live | A trading arm's own realized record decides how much rope it gets, recomputed every optimizer run: `probation → standard → trusted → autonomous`. The tier scales how far and how fast the optimizer may move a knob, which fields it may touch at all (trusted unlocks the entry universe, the LLM confidence bar, and the take-initials ladder), how much of the fixed fleet budget the evolution loop concentrates on the arm, and how much real evidence the LLM judge is handed before it rules (base rate, learned signal weights, the arm's own record, the realized win-rate table, the model's own calibration). Decided on realized net P&L and average edge, never win rate, so a 36%-hit-rate arm that actually makes money earns room while a 60%-hit-rate arm that loses money does not. Symmetric: an arm that stops paying loses its tier on the next pass. No tier can reach a safety rail (firewall, Mayhem exclusion, price impact, concurrency, loss cap, fleet ceiling) and a bounded stop-loss survives every tier. Tests: [tests/sniper-autonomy.test.js](tests/sniper-autonomy.test.js), [tests/sniper-optimizer.test.js](tests/sniper-optimizer.test.js), [tests/sniper-judge-knowledge.test.js](tests/sniper-judge-knowledge.test.js). See [docs/sniper-autonomy.md](docs/sniper-autonomy.md) || Fleet stall diagnosis (why an arm is not trading) | policy [api/_lib/sniper-stall.js](api/_lib/sniper-stall.js), funding invariant [api/_lib/agent-funding-policy.js](api/_lib/agent-funding-policy.js), operational floor `MIN_OPERATIONAL_WALLET_SOL` in [api/_lib/agent-trade-guards.js](api/_lib/agent-trade-guards.js), board field on [api/sniper/experiments.js](api/sniper/experiments.js) + [src/sniper-experiments.js](src/sniper-experiments.js) `→ /sniper/experiments`, ops page [workers/agent-sniper/alerts.js](workers/agent-sniper/alerts.js) | Live | An armed arm can evaluate every launch and still never buy, because a skipped evaluation writes no row: four arms sat dead for a week behind a bare `0`. Each armed strategy now reports a `stall` code the executor actually enforces (`wallet_dry`, `mcap_band_unreachable`, `mcap_band_tight`, `strict_model_offline`, `size_over_budget`, `kill_switch`, `no_qualifying_launch`), and the two arithmetic deadlocks behind them are gone: an entry clamps to the day's remaining budget instead of sitting out when size drifted above the cap, and the reclaim that pulls idle SOL back to the treasury can no longer take a trading wallet below one complete trade or below the level the auto-funder will instantly restore (the two crons were ping-ponging 0.24 SOL six times in 15 minutes). Tests: [tests/sniper-stall.test.js](tests/sniper-stall.test.js), [tests/economy-sweepback.test.js](tests/economy-sweepback.test.js). See [docs/trading-experiment.md](docs/trading-experiment.md), [docs/economy-master.md](docs/economy-master.md) |+| Capabilities command center | page [pages/dashboard-next/capabilities.html](pages/dashboard-next/capabilities.html) `→ /dashboard/capabilities`, client [src/dashboard-next/pages/capabilities.js](src/dashboard-next/pages/capabilities.js), feeds [api/sniper/status.js](api/sniper/status.js), [api/sniper/strategy.js](api/sniper/strategy.js), [api/agent/launcher.js](api/agent/launcher.js), [api/agent/market-maker.js](api/agent/market-maker.js) | Live | One screen for all four autonomous capabilities across every agent the signed-in user owns: Alpha Hunt smart-money strategies, the scheduled pump.fun Coin Launcher (with a Launch Now trigger the worker picks up within 60s), Creator Auto-Claim fee harvesting (with a per-coin Claim action), and the Jito-executed Market Maker. Reads the whole account in four requests via the `all=1` mode on both agent endpoints, refreshed every 30s; a lane that fails renders an in-place error with a working Retry rather than a zero, and the refresh preserves the open tab, scroll position, and any action still in flight. || Autonomous trading experiment | policy [scripts/trading-experiment-setup.mjs](scripts/trading-experiment-setup.mjs), laddered exit [workers/agent-sniper/exit-logic.js](workers/agent-sniper/exit-logic.js) (`decideLadderedExit`), no-Mayhem gate [workers/agent-sniper/mayhem-gate.js](workers/agent-sniper/mayhem-gate.js), journal [workers/agent-sniper/journal.js](workers/agent-sniper/journal.js) → [api/sniper/journal.js](api/sniper/journal.js) | In-repo | One agent, ~10 SOL, newer pump.fun launches ($10k–$100k mcap, no Mayhem). Take-initials-at-2× laddered exit keeps a moon bag (never a 100% exit up), hard stop-loss underneath. Every decision journaled with its reasoning. UI-funded, simulate-first. See [docs/trading-experiment.md](docs/trading-experiment.md) || Wallet Portfolio (any-address viewer) | aggregation [api/_lib/portfolio-overview.js](api/_lib/portfolio-overview.js) (pure, tested in [tests/portfolio-overview.test.js](tests/portfolio-overview.test.js)), endpoint [api/crypto/portfolio.js](api/crypto/portfolio.js) `→ /api/crypto/portfolio`, page [pages/portfolio.html](pages/portfolio.html) + [src/portfolio.js](src/portfolio.js) + [src/portfolio.css](src/portfolio.css) `→ /portfolio` | Live | Live portfolio for any Solana or Ethereum wallet: total value, 24h move with stated coverage, stable/major/token split, top-asset allocation donut, holdings table with dust folding. Solana fully keyless (Helius DAS or public RPC + Jupiter Lite + DexScreener); EVM needs ALCHEMY_API_KEY and 503s honestly without it. Docs: [docs/portfolio.md](docs/portfolio.md). Wiring test: [tests/portfolio-page.test.js](tests/portfolio-page.test.js) || Airdrop Checker (any-address eligibility) | scanner [api/_lib/wallet-activity.js](api/_lib/wallet-activity.js), evaluator [api/_lib/airdrop-eligibility.js](api/_lib/airdrop-eligibility.js) (pure, tested in [tests/airdrop-eligibility.test.js](tests/airdrop-eligibility.test.js)), registry [data/airdrops.json](data/airdrops.json), endpoint [api/crypto/airdrops.js](api/crypto/airdrops.js) `→ /api/crypto/airdrops`, page [pages/airdrops.html](pages/airdrops.html) + [src/airdrops.js](src/airdrops.js) + [src/airdrops.css](src/airdrops.css) `→ /airdrops` | Live | Scores any wallet's REAL on-chain activity against tracked airdrop criteria: Solana keyless (signature scan over the rotating RPC chain + balance-layer token diversity), EVM via Etherscan V2 behind ETHERSCAN_API_KEY. Unmeasurable fields report as unknown and never count as met; protocol-specific steps are unscored manual to-dos; capped scans flag totals as minimums. Cross-links with /portfolio and shares its recent-wallet list. Docs: [docs/airdrops.md](docs/airdrops.md). Wiring test: [tests/airdrops-page.test.js](tests/airdrops-page.test.js) |diff --git a/prompts/swarm-100/route-dashboard-capabilities.md b/prompts/swarm-100/route-dashboard-capabilities.mddeleted file mode 100644index 19546de92..000000000--- a/prompts/swarm-100/route-dashboard-capabilities.md+++ /dev/null@@ -1,119 +0,0 @@-# Route audit: /dashboard/capabilities (Capabilities: Alpha Hunt, Launcher, Auto-Claim & Market Maker)--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==='/dashboard/capabilities')console.log(JSON.stringify(g,null,2))"--2. Find the serving implementation: grep "/dashboard/capabilities" 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/dashboard/capabilities--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: /dashboard/capabilities ("Capabilities: Alpha Hunt, Launcher, Auto-Claim & Market Maker", section "crypto").-Declared purpose: Live command center for all 4 autonomous agent capabilities: Alpha Hunt smart-money scoring, autonomous Coin Launcher on schedule, Creator Auto-Claim for fee harvesting, and Market Maker with Jito execution.--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/dashboard/capabilities. 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 /dashboard/capabilities: 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-dashboard-capabilities.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.diff --git a/public/changelog.json b/public/changelog.jsonindex 7cb1d5c74..d07f1a4e2 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-25T17:51:37.666Z",+ "generated_at": "2026-08-25T18:12:14.260Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -47,6 +47,17 @@"improvement"]},+ {+ "date": "2026-08-25",+ "type": "update",+ "title": "Capabilities stops reporting an empty dashboard when the API is the thing that failed",+ "summary": "The Capabilities command center used to ask the API once per agent for launcher and market-maker data, which on a real roster tripped the rate limiter mid-load. The failed calls were silently discarded and the page rendered a confident all-zero dashboard for an account that had launchers, coins and live markets. It now reads each capability for the whole account in a single call, so the request count no longer grows with your roster, and any lane that does fail says so in place with a working Retry instead of showing a zero. The 30-second refresh also stops resetting the tab you were reading and no longer replaces a Launch Now or Claim button while its request is still in flight, and on a phone the row action stays pinned in view instead of scrolling off the right edge.",+ "link": "/dashboard/capabilities",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-25","type": "update",@@ -101,6 +112,17 @@"improvement"]},+ {+ "date": "2026-08-25",+ "type": "update",+ "title": "Dashboard Account fits a phone screen, and it stops claiming you own no .sol domains when it could not check",+ "summary": "On a 320px phone every card on the account page ran past the right edge of the screen, which put Sign out, the AI provider key fields, Link wallet, and the quick links out of reach with no way to scroll to them; the cards now fit and every control is reachable. The SNS panel used to answer a resolver outage with \"No primary .sol domains found\", telling you to go register a domain you may already own. It now says plainly that the lookup failed and offers a retry, and when only some of your wallets could be checked it says how many were missed instead of quietly counting them as empty. The panel also refreshes itself when you link, disconnect, or re-prioritise a wallet, rather than sitting on a stale answer until you reload. The delegation table says how many agents it is showing out of your total instead of silently listing the first eight, and the page finally carries a search description of what it holds: profile, wallets, domains, delegation, provider keys, and the audit trail.",+ "link": "/dashboard/account",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-25","type": "update",@@ -133,6 +155,17 @@"fix"]},+ {+ "date": "2026-08-25",+ "type": "update",+ "title": "The Data API console keeps working when one of its services is down, and its corpus numbers are now live",+ "summary": "The developer console at Dashboard > Data API is fed by three separate services, and any one of them failing used to take the whole page down: a pricing outage left a single error card where the pass status, the API key table, the quickstarts, and the endpoint list should have been, and a pass-status hiccup left a loading shimmer that never resolved. Each card now fails on its own with an explanation and a retry, and everything else stays usable. Status messages appear next to the control that produced them, so a key rotation error no longer lands in the pricing card several screens away. The copyable quickstarts stopped pasting a shortened version of your key into commands that could only ever be rejected; they now carry a clearly marked placeholder, or the real key in the moment it is minted. Copy buttons say so honestly when the browser refuses the clipboard instead of claiming success. The article and publisher-feed counts are read from the archive itself rather than typed into the page, so they no longer drift, and the tables and code blocks can be scrolled with the keyboard.",+ "link": "/dashboard/data-api",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-25","type": "update",@@ -164,6 +197,17 @@"docs"]},+ {+ "date": "2026-08-25",+ "type": "update",+ "title": "The market tools now clear the WCAG AA contrast floor",+ "summary": "An accessibility sweep of the compare page found four places where text did not have enough contrast against what sat behind it. The selected time-range button, the rank badge, and the heatmap's view switcher all put white on a blue too light to read; they now use a blue and a text colour chosen to clear the standard in both the light and the dark theme. The comparison table's green was too pale on a white background, the coin column headings were painted in their chart-line colour (worst of all for the amber series), and the Getting started pill's counter borrowed a colour meant for light backgrounds while sitting on a dark one. Every one of those is fixed, and the column headings keep their tie to the chart through a coloured rule under each symbol.",+ "link": "/compare",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-25","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 7b5355f96..87af1aa5e 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -38,6 +38,14 @@<category>fix</category><description>On /dashboard/billing, creator subscriptions now show the creator's name (linked to their profile), the real renewal or end date, a colour-coded status, and the plan price with its interval, instead of a raw account id. When the passes or subscriptions feed cannot be reached, the Retry button now actually reloads that section. Across every dashboard page, the top bar no longer forces the layout wider than a 320px phone screen, so nothing is clipped off the right edge.</description></item>+ <item>+ <title>Capabilities stops reporting an empty dashboard when the API is the thing that failed</title>+ <link>https://three.ws/dashboard/capabilities</link>+ <guid isPermaLink="false">2026-08-25:Capabilities stops reporting an empty dashboard when the API is the thing that failed</guid>+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The Capabilities command center used to ask the API once per agent for launcher and market-maker data, which on a real roster tripped the rate limiter mid-load. The failed calls were silently discarded and the page rendered a confident all-zero dashboard for an account that had launchers, coins and live markets. It now reads each capability for the whole account in a single call, so the request count no longer grows with your roster, and any lane that does fail says so in place with a working Retry instead of showing a zero. The 30-second refresh also stops resetting the tab you were reading and no longer replaces a Launch Now or Claim button while its request is still in flight, and on a phone the row action stays pinned in view instead of scrolling off the right edge.</description>+ </item><item><title>Compare reads correctly on a phone and stops mislabelling gains and losses</title><link>https://three.ws/compare</link>@@ -78,6 +86,14 @@<category>fix</category><description>Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's "Failed to fetch".</description></item>+ <item>+ <title>Dashboard Account fits a phone screen, and it stops claiming you own no .sol domains when it could not check</title>+ <link>https://three.ws/dashboard/account</link>+ <guid isPermaLink="false">2026-08-25:Dashboard Account fits a phone screen, and it stops claiming you own no .sol domains when it could not check</guid>+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>On a 320px phone every card on the account page ran past the right edge of the screen, which put Sign out, the AI provider key fields, Link wallet, and the quick links out of reach with no way to scroll to them; the cards now fit and every control is reachable. The SNS panel used to answer a resolver outage with "No primary .sol domains found", telling you to go register a domain you may already own. It now says plainly that the lookup failed and offers a retry, and when only some of your wallets could be checked it says how many were missed instead of quietly counting them as empty. The panel also refreshes itself when you link, disconnect, or re-prioritise a wallet, rather than sitting on a stale answer until you reload. The delegation table says how many agents it is showing out of your total instead of silently listing the first eight, and the page finally carries a search description of what it holds: profile, wallets, domains, delegation, provider keys, and the audit trail.</description>+ </item><item><title>Dashboard Analytics fits a phone screen and its failure page can actually reload</title><link>https://three.ws/dashboard/analytics</link>@@ -102,6 +118,14 @@<category>fix</category><description>Every text-to-3D generation starts by painting a concept image, and that step tried its image providers one after another with no overall time limit. When the first provider stalled, a request could sit for two and a half minutes before answering, and anything with a shorter patience (ChatGPT, agent clients) simply saw nothing. The painter now works to one shared budget: a slow provider hands off with real time left for the next one, and if the whole chain runs out you get a quick, honest retry-in-a-moment answer instead of a hang. Image-to-3D was never affected.</description></item>+ <item>+ <title>The Data API console keeps working when one of its services is down, and its corpus numbers are now live</title>+ <link>https://three.ws/dashboard/data-api</link>+ <guid isPermaLink="false">2026-08-25:The Data API console keeps working when one of its services is down, and its corpus numbers are now live</guid>+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The developer console at Dashboard > Data API is fed by three separate services, and any one of them failing used to take the whole page down: a pricing outage left a single error card where the pass status, the API key table, the quickstarts, and the endpoint list should have been, and a pass-status hiccup left a loading shimmer that never resolved. Each card now fails on its own with an explanation and a retry, and everything else stays usable. Status messages appear next to the control that produced them, so a key rotation error no longer lands in the pricing card several screens away. The copyable quickstarts stopped pasting a shortened version of your key into commands that could only ever be rejected; they now carry a clearly marked placeholder, or the real key in the moment it is minted. Copy buttons say so honestly when the browser refuses the clipboard instead of claiming success. The article and publisher-feed counts are read from the archive itself rather than typed into the page, so they no longer drift, and the tables and code blocks can be scrolled with the keyboard.</description>+ </item><item><title>The First 19 Weeks: everything shipped since day one, week by week</title><link>https://three.ws/docs/the-first-19-weeks</link>@@ -126,6 +150,14 @@<category>docs</category><description>A long-form research thesis on $THREE now lives in the docs: what three.ws is, every way the token is used (hold-to-access tiers, plan and pass discounts, marketplace and labor escrow, game cosmetics, gated embeds, deploy-fee waivers), how platform revenue is routed into buybacks, where the token trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself, each claim sourced to the code.</description></item>+ <item>+ <title>The market tools now clear the WCAG AA contrast floor</title>+ <link>https://three.ws/compare</link>+ <guid isPermaLink="false">2026-08-25:The market tools now clear the WCAG AA contrast floor</guid>+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>An accessibility sweep of the compare page found four places where text did not have enough contrast against what sat behind it. The selected time-range button, the rank badge, and the heatmap's view switcher all put white on a blue too light to read; they now use a blue and a text colour chosen to clear the standard in both the light and the dark theme. The comparison table's green was too pale on a white background, the coin column headings were painted in their chart-line colour (worst of all for the amber series), and the Getting started pill's counter borrowed a colour meant for light backgrounds while sitting on a dark one. Every one of those is fixed, and the column headings keep their tie to the chart through a coloured rule under each symbol.</description>+ </item><item><title>three.ws crossed 100 stars on GitHub</title><link>https://three.ws/changelog</link>diff --git a/public/features.json b/public/features.jsonindex 5b2bd06d1..efb360f0f 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-25T17:51:37.612Z",+ "generated_at": "2026-08-25T18:12:14.151Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/src/dashboard-next/pages/capabilities.js b/src/dashboard-next/pages/capabilities.jsindex 5935c477c..72a8711d2 100644--- a/src/dashboard-next/pages/capabilities.js+++ b/src/dashboard-next/pages/capabilities.js@@ -120,6 +120,27 @@ const STYLE = `<style>.cp-scroll { overflow-x: auto; -webkit-overflow-scrolling: touch; }.cp-scroll:focus-visible { outline: 2px solid var(--nxt-accent); outline-offset: -2px; }+/* Below 640px the section header's badge and link squeeze the title into a+ four-line column. Stack instead: title gets the full width, controls sit+ under it on one row. */+@media (max-width: 640px) {+ .cp-head { flex-direction: column; align-items: stretch; gap: 10px; padding: 12px 14px; }+ .cp-head-actions { display: flex; align-items: center; gap: 8px; }+ .cp-kpi { padding: 10px 14px; }+}++/* On a phone the table still scrolls sideways, but the row's primary action+ must not scroll out of reach with it: pin the action column to the right+ edge so Launch Now / Claim are always one tap away. */+@media (max-width: 640px) {+ .cp-table th.cp-act, .cp-table td.cp-act {+ position: sticky; right: 0; z-index: 1;+ background: var(--nxt-panel);+ box-shadow: -8px 0 8px -8px rgba(0,0,0,.55);+ }+ .cp-table tr:hover td.cp-act { background: var(--nxt-bg-2); }+}+/* Keyboard focus rings on every interactive element */.cp-tab:focus-visible,.cp-btn:focus-visible,@@ -260,6 +281,9 @@ function failureText(err) {if (err?.status === 429) return 'Rate limited. The data below is not available right now.';if (err?.status === 401 || err?.status === 403) return 'Your session no longer covers this data. Sign in again to load it.';if (err?.status >= 500) return 'The API returned an error. This is on our side, not yours.';+ // A fetch that never reached a server has no status, and its raw message is+ // browser-speak ("Failed to fetch"). Say something the reader can act on.+ if (err?.status == null) return 'No response from the network. Check your connection, then retry.';return err?.message || 'Could not reach the API.';}@@ -426,7 +450,7 @@ function renderAlphaHunt(strategies, err) {<div class="cp-head-sub">Smart-money signal scoring — buys when quality signals converge</div></div></div>- <div style="display:flex;align-items:center;gap:8px">+ <div class="cp-head-actions"><span class="cp-badge ${badgeClass}">${badgeLabel}</span><a class="cp-link" href="/dashboard/sniper">Configure ↗</a></div>@@ -510,7 +534,7 @@ function renderLauncher(configs, coins, err) {<div class="cp-head-sub">Autonomous pump.fun launches on schedule</div></div></div>- <div style="display:flex;align-items:center;gap:8px">+ <div class="cp-head-actions"><span class="cp-badge ${badgeClass}">${badgeLabel}</span>${soleAgentId ? `<a class="cp-link" href="/agents/${esc(soleAgentId)}/edit#section-launcher">Configure ↗</a>` : '<a class="cp-link" href="/dashboard/agents">Agents ↗</a>'}</div>@@ -538,7 +562,7 @@ function renderLauncher(configs, coins, err) {<th scope="col" class="hide-sm">Interval</th><th scope="col" class="r">Launches</th><th scope="col" class="r">Next Launch</th>- <th scope="col" class="r">Action</th>+ <th scope="col" class="r cp-act">Action</th></tr></thead><tbody>@@ -548,7 +572,7 @@ function renderLauncher(configs, coins, err) {<td class="hide-sm cp-muted">${c.interval_hours != null ? `Every ${c.interval_hours}h` : 'Manual'}</td><td class="r">${c.launches_count || 0}${c.max_launches ? ` / ${c.max_launches}` : ''}</td><td class="r cp-muted">${c.next_launch_at ? relTime(c.next_launch_at) : c.enabled ? 'Ready' : '—'}</td>- <td class="r">+ <td class="r cp-act">${c.enabled ? `<button type="button" class="cp-btn cp-btn-go" data-launch-now data-agent-id="${esc(c.agent_id)}" data-config-id="${esc(c.id)}" data-network="${esc(c.network || 'mainnet')}" aria-label="Launch $${esc(c.symbol || 'coin')} now">Launch Now</button>` : '<span class="cp-muted">—</span>'}</td></tr>`).join('')}@@ -618,7 +642,7 @@ function renderAutoClaim(coins, err) {<div class="cp-head-sub">Auto-harvests creator fees when coins run — runs every 5 min</div></div></div>- <div style="display:flex;align-items:center;gap:8px">+ <div class="cp-head-actions"><span class="cp-badge ${badgeClass}">${badgeLabel}</span></div></div>@@ -640,7 +664,7 @@ function renderAutoClaim(coins, err) {<th scope="col" class="r">Claimable</th><th scope="col" class="r">Total Claimed</th><th scope="col" class="r hide-sm">Last Checked</th>- <th scope="col" class="r">Action</th>+ <th scope="col" class="r cp-act">Action</th></tr></thead><tbody>@@ -654,7 +678,7 @@ function renderAutoClaim(coins, err) {<td class="r cp-mono ${claimSol > 0 ? 'cp-pos' : 'cp-muted'}">${fmtSolAbs(claimSol)}</td><td class="r cp-mono">${fmtSolAbs(earnedSol)}</td><td class="r hide-sm cp-muted">${c.last_fee_check_at ? relTime(c.last_fee_check_at) : 'Never'}</td>- <td class="r">+ <td class="r cp-act">${canClaim && claimSol > 0 ? `<button type="button" class="cp-btn cp-btn-claim" data-claim-now data-agent-id="${esc(c.agent_id)}" data-mint="${esc(c.mint)}" data-network="${esc(c.network || 'mainnet')}" aria-label="Claim ${fmtSolAbs(claimSol)} from $${esc(c.symbol || 'coin')}">Claim ${fmtSolAbs(claimSol)}</button>` : '<span class="cp-muted">Below threshold</span>'}</td></tr>`;@@ -689,7 +713,7 @@ function renderMarketMaker(configs, trades, err) {<div class="cp-head-sub">Range-based liquidity with Jito-accelerated execution</div></div></div>- <div style="display:flex;align-items:center;gap:8px">+ <div class="cp-head-actions"><span class="cp-badge ${err ? 'warning' : active.length ? 'live' : 'off'}">${err ? 'Unavailable' : active.length ? `${active.length} Active` : 'Inactive'}</span></div></div>diff --git a/tests/agent-capability-config-ids.test.js b/tests/agent-capability-config-ids.test.jsindex 1339d83f1..897f23c7c 100644--- a/tests/agent-capability-config-ids.test.js+++ b/tests/agent-capability-config-ids.test.js@@ -175,3 +175,62 @@ describe('/api/agent/market-maker id validation', () => {expect(sqlMock.mock.calls[1].slice(1)).not.toContain('not-a-cluster');});});++// The Capabilities command center reads every capability for the whole account+// at once. Before `all=1` it asked once per agent, which on a real roster spent+// more of the per-IP budget than the bucket held: the overflow came back 429,+// the page discarded it, and an account with launchers and live markets was+// shown a confident row of zeros. These pin the account-wide contract.+describe('account-wide reads (all=1)', () => {+ it('answers the launcher for every owned agent in two queries, with no agentId', async () => {+ sqlQueue = [+ [{ id: CONFIG, agent_id: AGENT, agent_name: 'Roster Agent', agent_image: null }],+ [{ mint: THREE_MINT, agent_id: AGENT, agent_name: 'Roster Agent', agent_image: null }],+ ];+ const res = mkRes();+ await launcher(mkReq({ url: '/api/agent/launcher?all=1' }), res);+ expect(res.statusCode).toBe(200);+ const body = parse(res);+ expect(body.scope).toBe('all');+ expect(body.configs).toHaveLength(1);+ expect(body.coins).toHaveLength(1);+ // Rows carry the owning agent inline so the caller needs no second lookup.+ expect(body.configs[0].agent_name).toBe('Roster Agent');+ // Two queries total: no per-agent ownership round trip.+ expect(sqlMock).toHaveBeenCalledTimes(2);+ });++ it('answers the market maker for every owned agent in two queries, with no agentId', async () => {+ sqlQueue = [+ [{ id: CONFIG, agent_id: AGENT, agent_name: 'Roster Agent', agent_image: null }],+ [{ id: 'trade-1', agent_id: AGENT, side: 'buy', agent_name: 'Roster Agent', agent_image: null }],+ ];+ const res = mkRes();+ await marketMaker(mkReq({ url: '/api/agent/market-maker?all=1' }), res);+ expect(res.statusCode).toBe(200);+ const body = parse(res);+ expect(body.scope).toBe('all');+ expect(body.configs).toHaveLength(1);+ expect(body.recent_trades).toHaveLength(1);+ expect(body.recent_trades[0].agent_name).toBe('Roster Agent');+ expect(sqlMock).toHaveBeenCalledTimes(2);+ });++ it('still demands an agentId when all is absent or not truthy', async () => {+ for (const url of ['/api/agent/launcher', '/api/agent/launcher?all=0', '/api/agent/launcher?all=maybe']) {+ sqlMock.mockClear();+ const res = mkRes();+ await launcher(mkReq({ url }), res);+ expect(res.statusCode).toBe(400);+ expect(parse(res).error).toBe('missing_agent_id');+ expect(sqlMock).not.toHaveBeenCalled();+ }+ for (const url of ['/api/agent/market-maker', '/api/agent/market-maker?all=0']) {+ sqlMock.mockClear();+ const res = mkRes();+ await marketMaker(mkReq({ url }), res);+ expect(res.statusCode).toBe(400);+ expect(sqlMock).not.toHaveBeenCalled();+ }+ });+});