Skip to content

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

docs(atlas): regenerate the changelog, features and llms feeds for the widget and drip work

nirholas012b2fc93014
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5a2a3e37a..70d68d2e5 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -31,6 +31,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Coin Radar tells you when it is your filter, not the market, that is empty**: Search the radar for a ticker it has not seen and the board used to say "Radar is clear, waiting for the next launch", which blamed a quiet market for a filter you set and gave you no way back. Most of Radar's filters run on the server, so an over-tight one came back looking exactly like a quiet window. Now the board reads your filters instead of the response: it says no coins match, lists every filter you have on as a chip you can click to drop just that one, and keeps a reset-everything button next to it. The 24-hour pulse strip across the top also got an honest state of its own. It is a separate request from the live feed, and when it failed it used to shimmer as if still loading forever; now it says the aggregate did not load, offers a retry, and leaves the feed below running. On a 320px phone every card was losing about 19 pixels off its right edge to a layout overflow that the mobile scroll guard was quietly clipping; cards now fit the screen they are on. (`/radar`) `[fix, improvement]`
- **Connect a home that only exists on your own network**: Most Home Assistant installs sit on a home network with nothing exposed to the internet, so until now three.ws had no way to reach them. Now the house connects to us instead. Install one integration through HACS, paste a ten-minute pairing code, and your agent can see your rooms and run your scenes with nothing listening on your network, no port forwarded, and no firewall rule changed. The part worth saying plainly: three.ws never receives a Home Assistant token for a home connected this way. The integration signs in to Home Assistant on your own machine with a credential it makes for itself and never sends anywhere, so there is nothing stored here that would open your house. What we can do through that connection is a fixed list, enforced twice, once by us and once by the integration on your machine: reads, your room layout, and device controls. It can never run code on the machine Home Assistant lives on, restart or reconfigure your instance, or reach anything else on your network. Unlocking, opening and disarming still stop and ask a person first, every time, exactly as they do for a home connected by address. Disconnecting works from either end and takes effect immediately. There is an honest threat model in the docs, including what a compromise of three.ws would mean for a connected house; read it before you decide. (`/docs/home-relay`) `[feature, security]`
- **Connect your house to your agent, and see every way it can go wrong**: The /smart-home page now takes you from "I have a Home Assistant somewhere" to a connected house, and it is honest at every step. An address that only exists on your home network is refused the moment you type it, with the two real ways round it, instead of spinning for fifteen seconds. A rejected token says so and puts the cursor back in the token box. A house that stops answering keeps its rooms on screen, marked stale with how long ago it last replied, rather than blanking out. Your access token is sent once, encrypted at rest, and never comes back to the page: it is not in your browser storage, not in a URL, and not in any response. Disconnecting says plainly that the stored token is erased and reminds you to delete it in Home Assistant too. (`/smart-home`) `[feature]`
+- **Daily Forge shows the day's theme again**: Daily Forge is built around one thing: the challenge of the day. That headline was being wiped out a moment after the page loaded. The translation layer runs after the page fetches its language file, and it was overwriting the day's theme with the placeholder text baked into the HTML, so every visitor read "Today's theme" and "Loading today's challenge" forever while the starter prompt and the idea chips below quietly described a completely different subject. The theme, its emoji, its hint and the browser tab title now hold. Four more fixes landed with it: a failed generation says "Could not reach the forge, check your connection" instead of the browser's raw "Failed to fetch"; when a model finishes but the preview cannot show it, the Download button the message points at is now actually clickable instead of sitting underneath the message; every button and link has a visible focus outline for keyboard and screen-reader users, and the streak milestone popup takes focus, closes on Escape and hands focus back; and a browser without 3D support now still sees today's theme and a clear explanation instead of a permanent loading line. The community strip at the bottom also fills in properly rather than staying empty. (`/daily`) `[fix, improvement]`
- **Endpoint Shopper takes payment on the page, so a paid run actually runs**: Paying for an Endpoint Shopper run used to send you to the generic payment page, which arrived with no price and no wallet options because it could not read the challenge this route sends. Even if it had, it would have replayed the run as an empty request: your task and budget were left behind on the previous page, so a completed payment unlocked nothing. Payment now happens on /shopper itself. The card quotes the real price, lists the Base and Solana wallets the endpoint accepts, reports connecting, signing and settling as they happen, and replays the exact task and budget you typed, so the answer and its cost breakdown appear right where you were, with a link to the settlement transaction. The example task chips are now real buttons you can reach with the keyboard, the task box and budget slider carry proper labels, and the Marketplace and Fact Checker links no longer vanish from the header on a phone. (`/shopper`) `[fix, improvement]`
- **Every SDK doc now points at code you can actually run**: Eight developer docs pages described a capability without ever showing you a working project that uses it, so finding the runnable version meant guessing at folder names on GitHub. The SDK, MCP, embedding, authentication, create-an-agent, Solana, agent-payments and agent-wallets pages now each end with a Runnable example section linking straight to the project that backs them: a browser demo, a Node script that drives the free MCP server end to end, nine single-file HTML embeds you can open with no build step, the full wallet sign-in round trip, and a complete agent defined entirely as files. The machine-readable index that AI agents read to navigate the site now carries the examples location too, so an agent asked to build against three.ws can fetch working code instead of inferring it from prose. Every one of those examples is installed, run and link-checked before release, so a link on a docs page never points at something broken. (`/docs/sdk`) `[docs, improvement]`
- **Live Trading Theater: the tape opens full and the connection light tells the truth**: The theater got a pass over every state it can be in. The connection light in the top bar used to say Connecting for the whole visit even after the live feed had connected seconds earlier, because the page's translation pass ran last and put the placeholder wording back; it now reports the connection it actually has, and the same fix stops the sound button telling a screen reader the sound is off while it is on. The Live tape used to be a blank column until something happened on-chain: it now opens seeded with real recent activity, shows placeholder rows while that is loading, and says what it is waiting for when the feed is genuinely quiet. A slow roster response no longer dumps you straight onto the error card; the page tries again with more room and says it is still assembling. Recent-activity entries that had nowhere to link are plain text now instead of links that went nowhere, and the ones that do link to a three.ws page stay in your tab instead of opening a new one. The nameplates over each 3D trader were invisible to screen readers even though they are the only keyboard route into a trader's wallet and reputation panel; they are now reachable, and every remaining control on the page has a visible focus ring. (`/theater`) `[fix, improvement]`
@@ -55,6 +56,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Tour Atlas counts its own stops honestly, and says why a stop has no picture**: The atlas advertised 185 stops in its page title, its search prompt, its social cards and its listing everywhere on the site. It has had 263 for a while, and nothing was checking, so the number quietly went stale. It now says 263, and the atlas guard fails the build if that number ever stops matching the manifest again. Eighteen stops carry no screenshot because they are live 3D or live-market pages that never stop painting long enough to be photographed; their cards used to claim the page 'did not respond', which was untrue of all of them, and now they say what actually happened and invite you to open the page live. Opening one of those stops used to show an empty black frame above the write-up, and now shows the same explanation. If the atlas itself cannot load you get a plain sentence about what went wrong and a Try again button, instead of a raw browser error or an instruction to run a developer command. And a /tour/atlas#stop-name link now opens that stop even when you are already on the page or have a filter narrowing the grid. (`/tour/atlas`) `[fix, improvement]`
- **Traders can now price the latency of their own calls**: Copy trading has a new option for the trader being copied: alpha-drip. A trader can set how long each $THREE holder tier waits before their copy intent is revealed, so holding more $THREE means seeing their calls sooner. It is off unless a trader turns it on, and the rules are strict on purpose: a higher tier can never wait longer than a lower one, no delay can exceed fifteen minutes, and the delay only affects when a copier is SHOWN the trade. The trade itself is still recorded the instant it happens and still appears in the trader's public track record, so nothing is ever hidden. Copiers see exactly which seat their balance buys before they subscribe, and a held intent shows a live countdown that unlocks in place. Traders can also ask for a suggested ladder tuned to how fast their own edge actually decays, measured from their real closed trades, and get warned when the slowest tier would be waiting longer than that edge lasts. (`/docs/alpha-drip`) `[feature]`
- **We tried making your agent a Matter device, measured it, and decided against it for now**: Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over. (`/docs/smart-home`) `[docs]`
+- **Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple**: The widget that has been on Android home screens and the Windows 11 widgets board now runs on Apple platforms too, from one WidgetKit extension shared by both. On a Mac it lives in Notification Centre in small, medium or large, fed by a small menu bar app that shows the same card and carries Open my agent, Refresh now and Unlink this Mac. On iPhone and iPad it is a home screen widget inside the three.ws app. Linking is one press on three.ws/glance: the page hands the device its own token, and if nothing opens (a Mac whose browser is signed in elsewhere) it shows a code to paste instead. The widget refreshes about every half hour without you opening anything, follows light and dark mode because it fetches the card in both, keeps the last card it downloaded when you are offline and says when that was rather than showing a spinner, and opens your agent on a tap. Every linked device is listed on three.ws/glance with a revoke button, and each token can only ever read your glance card. (`/glance`) `[feature]`
- **Your Home Assistant voice assistant can have a face now**: If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face. (`/smart-home/satellite`) `[feature]`
- **Your home is a household now, and a house sitter still cannot open your front door**: A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so their app never learns those rooms exist. Invitations work once, expire after a week, and can be withdrawn before anyone uses them. Removing somebody takes back every standing allowance they ever approved in the same instant, so a door can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer. (`/smart-home`) `[feature, security]`
- **Your home tells you when it stops answering, and whether the problem is ours**: When a connected house goes quiet, the manage page now says what happened and what to do about it, without you having to ask anyone. It names the real reason the handshake failed, separates a Home Assistant that rejected our token (make a new one) from a Home Assistant we cannot reach at all (check the instance), and keeps the last room state on screen instead of emptying the page. The part that matters most: it tells you whose problem it is. If enough other homes are failing at the same moment, it says so plainly and tells you there is nothing for you to do, so nobody spends an evening rebooting a router that was never broken. A house that already looks unhealthy loads the explanation on its own; a house that looks fine keeps its panel closed until you open it, so nothing extra is fetched for homes that are working. (`/smart-home`) `[feature, improvement]`
diff --git a/STRUCTURE.md b/STRUCTURE.md
index daee4bf46..2af919ab5 100644
--- a/STRUCTURE.md
+++ b/STRUCTURE.md
@@ -51,7 +51,7 @@ bottom.
| Cross-entity search | [pages/search.html](pages/search.html) `→ /search` + page module [src/search-page.js](src/search-page.js), backend [api/search.js](api/search.js) + query layer [api/_lib/cross-search.js](api/_lib/cross-search.js) | Live | The one search across every creation type: avatars, on-chain/Solana agents, forged 3D models, worlds, and coins. Federates (not one SQL UNION, because the stores are genuinely heterogeneous and two of five are not even in the same database) five parallel queries, normalizes into one card shape, and ranks by recency plus real signals (follower count via `user_follows`, remix count, view count); see the file header in `api/search.js` for the full unify-vs-federate writeup. Model results carry a working "Remix, $0.25" action against the existing paid rail ([api/x402/remix-asset.js](api/x402/remix-asset.js)), reused from [pages/creations.html](pages/creations.html) rather than re-derived. Coin search checks three.ws's own launch directory (`pump_agent_mints`) first, then falls back to market-wide pump.fun/Birdeye search for broader coverage (those external matches carry no verified timestamp or creator profile, and are ranked/labelled accordingly). The page reads `?q=` and `?type=` from the URL before it paints the filter row, so a shared scoped link shows the filter it is actually applying; a type whose source returned nothing for the current query is dimmed from the real `counts` in the response. The backend answering `{enabled:false}` (creation stores unreachable) renders its own "search is warming up" state with a retry and live browse links, never a false "nothing matched". Enter runs the query without waiting out the debounce and Escape clears it. Linked from the Discover nav menu. |
| Cross-surface rankings, streaks & badges | [pages/rankings.html](pages/rankings.html) `→ /rankings`, backend [api/leaderboard/unified.js](api/leaderboard/unified.js), streak/badge engine [api/_lib/streaks.js](api/_lib/streaks.js) (migration [api/_lib/migrations/20260712020000_leaderboard_streaks_badges.sql](api/_lib/migrations/20260712020000_leaderboard_streaks_badges.sql)), daily Top-10 badge sweep [api/cron/leaderboard-rollup.js](api/cron/leaderboard-rollup.js) | Live | Five real, queried leaderboard metrics — creations (forge models + worlds), remixes received, coin launches, followers, and walk distance (signed-in walkers, all-time) — ranked live with the viewer's own rank pinned even off-page. Every signed-in qualifying action (login, a finished forge model, a saved world, a `/walk` session) rolls a per-user daily streak in `user_streaks` via `recordDailyActivity()`, called from [api/_lib/auth.js](api/_lib/auth.js), [api/_lib/forge-store.js](api/_lib/forge-store.js), [api/_lib/diorama-store.js](api/_lib/diorama-store.js), and [api/walk/metrics.js](api/walk/metrics.js). Four real earned badges persist in `user_badges`: First Creation, Remixed (awarded in [api/x402/remix-asset.js](api/x402/remix-asset.js) when a remix lands on your creation), 7-Day Streak, and a daily-refreshed `top10_<metric>` per leaderboard. Streak + badges surface on the profile ([pages/profile.html](pages/profile.html)) and the Rankings page itself. Rejected metrics (documented in `api/leaderboard/unified.js`'s header): royalties earned in USD (the settlement record is a single overwritten JSONB column, not a cumulative ledger) and `/play` activity (no per-human-user session table exists). |
| create-agent (one command, one 3D character) | [packages/create-agent/](packages/create-agent) (client [src/forge.js](packages/create-agent/src/forge.js), scaffold [src/scaffold.js](packages/create-agent/src/scaffold.js), CLI [bin/create-agent.js](packages/create-agent/bin/create-agent.js)), server tools [api/_mcp-studio/tools.js](api/_mcp-studio/tools.js) | Live | `npm create @three-ws/agent "a friendly cartoon astronaut"` generates a textured figure, rigs it, downloads the GLB, and writes a folder with a working demo page and the embed snippet. No account and no API key: it rides the public, keyless JSON-RPC tools on [/api/mcp-studio](api/_mcp-studio) (`forge_avatar`, `forge_free`, `rig_mesh`) that the platform already exposes to MCP clients. A rigged character reliably outlives the endpoint's inline wait, so the client collects the returned poll handle and, when the job that finished was only the mesh, rigs it before reporting done: that is what the `stage` field on a pending result exists for. Progress is real elapsed time, never an invented bar. Docs [docs/create-agent.md](docs/create-agent.md). Tests: [tests/create-agent.test.js](tests/create-agent.test.js) |
-| Glance (agent cards for home screens, READMEs and chat) | Page [public/glance/index.html](public/glance/index.html) `-> /glance` (+ [glance-page.js](public/glance/glance-page.js), [glance.css](public/glance/glance.css)), hosted element [public/glance/element.js](public/glance/element.js), endpoints [api/glance/card.js](api/glance/card.js) / [api/glance/mine.js](api/glance/mine.js) / [api/glance/token.js](api/glance/token.js) / [api/glance/template.js](api/glance/template.js), model [api/_lib/glance-card.js](api/_lib/glance-card.js), SVG [api/_lib/glance-svg.js](api/_lib/glance-svg.js), PNG [api/_lib/glance-png.js](api/_lib/glance-png.js), widget tokens [api/_lib/glance-tokens.js](api/_lib/glance-tokens.js) (`glance_widget_tokens`), Adaptive Card [api/_lib/glance-adaptive.js](api/_lib/glance-adaptive.js), Windows widget worker [public/glance-sw.js](public/glance-sw.js) (imported by the VitePWA service worker, manifest `widgets` member in [vite.config.js](vite.config.js)), Android home screen widget [solana-mobile/android-overlay/](solana-mobile/android-overlay/README.md) (applied by [solana-mobile/scripts/apply-overlay.mjs](solana-mobile/scripts/apply-overlay.mjs) inside `build-apk.sh`), npm client [packages/agent-glance/](packages/agent-glance) | Live | One agent reduced to what fits in an OS widget slot: name, one live number (actions in the last 24h), and a link back. The same model renders five ways from one endpoint (JSON, SVG, PNG, Adaptive Card, and the `<agent-glance>` element), which is what keeps a new surface a rendering job rather than a data job. Windows 11 installs the widget straight from the PWA manifest (no store submission). Android ships it in the app (1.1+): a WorkManager-refreshed `AppWidgetProvider` that fetches the PNG with a revocable per-account widget token minted on `/glance`, keeps the last card offline, and opens the agent on tap. macOS and iOS (WidgetKit) consume the same PNG and token next. Deliberately not the 3D embed: no widget host on any of these platforms can run WebGL, so the body stays at [/widgets](public/widgets-gallery/index.html) and the status lives here. Private avatars never leak (the thumbnail is attached only for a public or unlisted avatar; everything else draws a generated monogram). Spec [specs/GLANCE_CARD.md](specs/GLANCE_CARD.md), docs [docs/glance.md](docs/glance.md), [docs/native-widgets.md](docs/native-widgets.md). Tests: [tests/glance-card.test.js](tests/glance-card.test.js), [tests/glance-png.test.js](tests/glance-png.test.js), [tests/glance-tokens.test.js](tests/glance-tokens.test.js), [tests/glance-sw.test.js](tests/glance-sw.test.js), [tests/agent-glance-sdk.test.js](tests/agent-glance-sdk.test.js) |
+| Glance (agent cards for home screens, READMEs and chat) | Page [public/glance/index.html](public/glance/index.html) `-> /glance` (+ [glance-page.js](public/glance/glance-page.js), [glance.css](public/glance/glance.css)), hosted element [public/glance/element.js](public/glance/element.js), endpoints [api/glance/card.js](api/glance/card.js) / [api/glance/mine.js](api/glance/mine.js) / [api/glance/token.js](api/glance/token.js) / [api/glance/template.js](api/glance/template.js), model [api/_lib/glance-card.js](api/_lib/glance-card.js), SVG [api/_lib/glance-svg.js](api/_lib/glance-svg.js), PNG [api/_lib/glance-png.js](api/_lib/glance-png.js), widget tokens [api/_lib/glance-tokens.js](api/_lib/glance-tokens.js) (`glance_widget_tokens`), Adaptive Card [api/_lib/glance-adaptive.js](api/_lib/glance-adaptive.js), Windows widget worker [public/glance-sw.js](public/glance-sw.js) (imported by the VitePWA service worker, manifest `widgets` member in [vite.config.js](vite.config.js)), Android home screen widget [solana-mobile/android-overlay/](solana-mobile/android-overlay/README.md) (applied by [solana-mobile/scripts/apply-overlay.mjs](solana-mobile/scripts/apply-overlay.mjs) inside `build-apk.sh`), macOS and iOS WidgetKit widget [apple/](apple/README.md) (shared [apple/GlanceKit/](apple/GlanceKit), extension [apple/GlanceWidget/](apple/GlanceWidget), Mac app [apple/macos/](apple/macos), an iOS target in [ios/native/App/App.xcodeproj](ios/native/App)), npm client [packages/agent-glance/](packages/agent-glance) | Live | One agent reduced to what fits in an OS widget slot: name, one live number (actions in the last 24h), and a link back. The same model renders five ways from one endpoint (JSON, SVG, PNG, Adaptive Card, and the `<agent-glance>` element), which is what keeps a new surface a rendering job rather than a data job. Windows 11 installs the widget straight from the PWA manifest (no store submission). Android ships it in the app (1.1+): a WorkManager-refreshed `AppWidgetProvider` that fetches the PNG with a revocable per-account widget token minted on `/glance`, keeps the last card offline, and opens the agent on tap. macOS and iOS run one WidgetKit extension over the same PNG and the same token, in small, medium and large: the Mac ships as a Developer ID menu bar app that holds the token and feeds the widget, and the iPhone gets the extension inside the existing Capacitor app. Both fetch the card in each theme so the widget follows the reader's appearance. `npm run check:apple-widget` proves both Xcode projects and the client-to-server contract without a Mac in the room. Deliberately not the 3D embed: no widget host on any of these platforms can run WebGL, so the body stays at [/widgets](public/widgets-gallery/index.html) and the status lives here. Private avatars never leak (the thumbnail is attached only for a public or unlisted avatar; everything else draws a generated monogram). Spec [specs/GLANCE_CARD.md](specs/GLANCE_CARD.md), docs [docs/glance.md](docs/glance.md), [docs/native-widgets.md](docs/native-widgets.md). Tests: [tests/glance-card.test.js](tests/glance-card.test.js), [tests/glance-png.test.js](tests/glance-png.test.js), [tests/glance-tokens.test.js](tests/glance-tokens.test.js), [tests/glance-sw.test.js](tests/glance-sw.test.js), [tests/agent-glance-sdk.test.js](tests/agent-glance-sdk.test.js), guard [scripts/check-apple-widget.mjs](scripts/check-apple-widget.mjs) |
| Daily Match (agent output arena) | [pages/daily-match.html](pages/daily-match.html) `→ /daily-match`, backend [api/leaderboard/daily-match.js](api/leaderboard/daily-match.js) | Live | Live daily standings ranking public agents by real output shipped since 00:00 UTC: agent_actions events, sniper + pump trades, confirmed skill sales, and coin launches, with realized sniper P&L shown for context (never scored). Computed live per request (no rollup cron), resets naturally at UTC midnight; includes yesterday's champion and a live-output feed. Reputation-first: no payouts hang off the score. Format adopted with credit from Bowyer's Arena (bowyer.app/arena), who build their agent pages on three.ws avatars. |
| KOL Tracker | [pages/tracker.html](pages/tracker.html) `→ /tracker`, backend [api/kol/[action].js](api/kol/%5Baction%5D.js) `→ GET /api/kol/tracker?window=&limit=`, aggregator [src/kol/tracker.js](src/kol/tracker.js), wallet list [src/kol/wallet-store.js](src/kol/wallet-store.js) (bundled [src/kol/wallets.json](src/kol/wallets.json) + admin R2 imports via `POST /api/kol/import-gmgn`), FIFO P&L engine [src/kol/wallet-pnl.js](src/kol/wallet-pnl.js), cached X follower/avatar lookup [src/kol/x-profile.js](src/kol/x-profile.js) | Live | Solana crypto KOLs ranked by realized P&L computed from each tracked wallet's own on-chain trade history (24h/7d/30d), with win rate, volume, and trade count — every number traceable to real trades, never a competitor's computed leaderboard. A wallet only shows an X handle/avatar/follower-count when an admin has explicitly attached a verified `xHandle` via `import-gmgn`'s `xHandles` map (never inferred or scraped); unattached wallets rank by wallet address alone. Rows with no configured trade source (`PUMPFUN_BOT_URL`) fall back to an imported `pnlUsd`/`winRate` labeled with its `pnlSource` rather than fabricating on-chain numbers. Prewarm cron: [api/cron/kol-tracker-refresh.js](api/cron/kol-tracker-refresh.js). |
| Agent Symphony (economy as generative music) | [pages/symphony.html](pages/symphony.html) `→ /symphony`, engine [src/symphony.js](src/symphony.js), grammar [src/symphony-score.js](src/symphony-score.js) | Live | The live activity bus (`GET /api/feed` + `/api/feed-stream` SSE) rendered as WebAudio generative music: one synthesized note per real platform event, voice by event type (payments pluck, coin buys land as bass, new agents chime, guard refusals play dissonance, jackpots glissando), pitch register by amount (whales sit lower), stable per-actor motif + stereo position via FNV-1a hash, all quantized to one pentatonic scale so arbitrary event streams harmonize. Canvas visualization, live ledger with real click-throughs, and a MediaRecorder tap that exports a shareable audio clip of the master bus. A burst gate collapses event floods (a sniper sweep emitting dozens of identical guard events) into one accented note per actor per 1.5s. Solo mode narrows the stream to one participant client-side (`?agent=<id>` exact, `?actor=<label>` case-insensitive), reachable from the per-row "solo" control and from the "Listen →" link on every agent profile's Wallet Story card. No audio assets, no synthetic events. Tests: [tests/symphony-score.test.js](tests/symphony-score.test.js) |
@@ -200,7 +200,7 @@ bottom.
| Ship log (release notes joined to the commits that shipped them) | Package [packages/shipfeed/](packages/shipfeed/README.md), endpoint [api/ship/feed.js](api/ship/feed.js) `→ GET /api/ship/feed`, page [public/ship/index.html](public/ship/index.html) `→ /ship`, provenance for the announcement lane [api/_lib/ship-provenance.js](api/_lib/ship-provenance.js) | Live | The join between the two records of the same work this repo keeps: the changelog (readable, incomplete) and the commit log (complete, unreadable). `@three-ws/shipfeed` parses conventional commits, scores each one by audience (holder / developer / internal) and signal, and links release notes to the commits that produced them with no metadata in the workflow: a `Changelog:` trailer wins where one exists, otherwise a time window plus IDF-weighted term overlap plus tag agreement plus proximity, and every link publishes its confidence and its reasons (`?explain=<sha>` returns one commit's full reasoning). Unclaimed commits are grouped into bursts and shown as "unannounced", which is the half no changelog has ever surfaced. The same package now drives both Telegram lanes: release announcements carry a "shipped in N commits" compare link, and the raw commit feed reads its headline from the parser (`feat(resilience):` reads as "Feature · resilience") and skips merges, `chore(deps):` bumps and lockfile-only changes. Zero dependencies, works on any repository, CLI included (`npx @three-ws/shipfeed`). Docs: [docs/shipfeed.md](docs/shipfeed.md). Tests: [packages/shipfeed/tests/](packages/shipfeed/tests), [tests/ship-feed-endpoint.test.js](tests/ship-feed-endpoint.test.js), [tests/ship-provenance.test.js](tests/ship-provenance.test.js) |
| On-chain agent invocation | [contracts/agent-invocation/](contracts/agent-invocation) | In-repo | Anchor program: verifiable agent-to-agent skill invocation events. SDK: [agent-protocol-sdk/](agent-protocol-sdk) |
| Cross-chain SDKs | [sdk/](sdk), [solana-agent-sdk/](solana-agent-sdk), [agent-payments-sdk/](agent-payments-sdk), [agent-protocol-sdk/](agent-protocol-sdk) | Published | Cross-chain agent SDKs |
-| MCP integration | [mcp-server/](mcp-server), [mcp-bridge/](mcp-bridge), [packages/*-mcp/](packages) | 37 npm servers + 7 hosted remote (44 total, incl. the free `/api/mcp-studio` 3D Studio), all in the [MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas). Canonical metadata: [prompts/store-submissions/_generated/mcp-listing-source.json](prompts/store-submissions/_generated/mcp-listing-source.json) | Model Context Protocol surface, full server list in [docs/mcp.md](docs/mcp.md). Searchable index of every tool: [pages/mcp-tools.html](pages/mcp-tools.html) `→ /mcp-tools`, rendered from the generated [public/mcp-catalog.json](public/mcp-catalog.json) ([scripts/build-mcp-catalog.mjs](scripts/build-mcp-catalog.mjs), `npm run build:mcp-catalog`, staleness gated by `npm run audit:mcp-catalog`). Tool safety annotations are verified against each handler by [scripts/audit-mcp-safety.mjs](scripts/audit-mcp-safety.mjs) (`npm run audit:mcp-safety`, rules in [scripts/lib/mcp-safety-check.mjs](scripts/lib/mcp-safety-check.mjs), guarded-file list shared with the golden snapshot via [scripts/lib/mcp-tool-sources.mjs](scripts/lib/mcp-tool-sources.mjs)); docs [docs/mcp-safety.md](docs/mcp-safety.md) `→ /docs/mcp-safety`. Trust policy: [api/mcp-policy.js](api/mcp-policy.js) `-> GET /api/mcp-policy` turns those verified labels into a ready-to-paste client allowlist (profiles strict/balanced/open x formats claude/vscode/json), surfaced by the builder panel on `/mcp-tools`. Tests: [tests/mcp-safety-audit.test.js](tests/mcp-safety-audit.test.js), [tests/mcp-catalog.test.js](tests/mcp-catalog.test.js), [tests/api/mcp-policy.test.js](tests/api/mcp-policy.test.js) |
+| MCP integration | [mcp-server/](mcp-server), [mcp-bridge/](mcp-bridge), [packages/*-mcp/](packages) | 43 npm servers + 7 hosted remote (50 total, incl. the free `/api/mcp-studio` 3D Studio), all in the [MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas). Canonical metadata: [prompts/store-submissions/_generated/mcp-listing-source.json](prompts/store-submissions/_generated/mcp-listing-source.json) | Model Context Protocol surface, full server list in [docs/mcp.md](docs/mcp.md). Searchable index of every tool: [pages/mcp-tools.html](pages/mcp-tools.html) `→ /mcp-tools`, rendered from the generated [public/mcp-catalog.json](public/mcp-catalog.json) ([scripts/build-mcp-catalog.mjs](scripts/build-mcp-catalog.mjs), `npm run build:mcp-catalog`, staleness gated by `npm run audit:mcp-catalog`). Tool safety annotations are verified against each handler by [scripts/audit-mcp-safety.mjs](scripts/audit-mcp-safety.mjs) (`npm run audit:mcp-safety`, rules in [scripts/lib/mcp-safety-check.mjs](scripts/lib/mcp-safety-check.mjs), guarded-file list shared with the golden snapshot via [scripts/lib/mcp-tool-sources.mjs](scripts/lib/mcp-tool-sources.mjs)); docs [docs/mcp-safety.md](docs/mcp-safety.md) `→ /docs/mcp-safety`. Trust policy: [api/mcp-policy.js](api/mcp-policy.js) `-> GET /api/mcp-policy` turns those verified labels into a ready-to-paste client allowlist (profiles strict/balanced/open x formats claude/vscode/json), surfaced by the builder panel on `/mcp-tools`. Tests: [tests/mcp-safety-audit.test.js](tests/mcp-safety-audit.test.js), [tests/mcp-catalog.test.js](tests/mcp-catalog.test.js), [tests/api/mcp-policy.test.js](tests/api/mcp-policy.test.js) |
| Agent Skills pack | [.agents/skills/](.agents/skills) → manifest [.agents/skills/SKILLS.md](.agents/skills/SKILLS.md), [.agents/skills/skills-pack.json](.agents/skills/skills-pack.json) | In-repo; bundled in the `three-ws-core` [plugin](.claude-plugin/marketplace.json) | 40 portable `SKILL.md` folders (Agent Skills open standard) for any Claude surface — 3d/creative (cross-platform-safe), wallet/payments, intel/trading. Regenerate manifest: `node scripts/build-skills-pack.mjs`. Docs: [docs/agent-skills.md](docs/agent-skills.md) |
| Claude Code plugin marketplace | [marketplace/](marketplace) → plugins [three-ws-3d](marketplace/plugins/three-ws-3d), [three-ws-developer](marketplace/plugins/three-ws-developer) | In-repo · installable via `/plugin marketplace add nirholas/three.ws` | 3D generation + rigged avatars inside Claude Code (free lane + paid x402 tools) and developer tooling for building on three.ws. Index: [marketplace/README.md](marketplace/README.md) |
| SNS naming + pay-by-name | [api/sns.js](api/sns.js), [api/sns-subdomain.js](api/sns-subdomain.js), [api/threews/subdomain.js](api/threews/subdomain.js), [api/x402/pay-by-name.js](api/x402/pay-by-name.js), [src/solana/sns-subdomain.js](src/solana/sns-subdomain.js), [pages/threews-claim.html](pages/threews-claim.html) | In-repo | `*.threews.sol` subdomain mint, x402 payments addressed by name. Env: `THREEWS_SOL_PARENT_SECRET_BASE58` |
@@ -246,7 +246,8 @@ bottom.
| BNB Chain live block race | [pages/bnb-latency.html](pages/bnb-latency.html) + [src/bnb-latency.js](src/bnb-latency.js) `→ /bnb-latency`, pure helpers [src/bnb-latency-helpers.js](src/bnb-latency-helpers.js), live multi-chain API [api/bnb/latency.js](api/bnb/latency.js) over [api/_lib/bnb/latency-lanes.js](api/_lib/bnb/latency-lanes.js) (reuses `probeBlockTime` from [api/_lib/bnb/chains.js](api/_lib/bnb/chains.js) for BNB, adds Base/Ethereum/Solana lanes) | In-repo · shipped | Standalone, shareable proof page: four lanes (BNB Chain, Base, Ethereum, Solana) polled every 5s, each showing a freshly measured average block/slot time and a rolling sparkline — no hardcoded numbers, a down RPC shows "reconnecting" on just that lane. Headline strip shows BNB's live average plus its honest measured-vs-measured speedup over Base/Ethereum. Linked from the [/bnb](pages/bnb.html) hub's "real-time on-chain world" card, which auto-lights-up now that this route resolves. |
| BNB Chain payments (MPP, x402↔MPP bridge, gasless) | Accept [api/_lib/bnb/mpp-server.js](api/_lib/bnb/mpp-server.js) (`mppRequirements`/`mppChallenge`/`mppVerify`/`mppSettle`), pay [api/_lib/bnb/mpp-buyer.js](api/_lib/bnb/mpp-buyer.js) (`mppFetch`, re-exported from [api/_lib/x402-buyer-fetch.js](api/_lib/x402-buyer-fetch.js)), gasless rail [api/_lib/bnb/megafuel.js](api/_lib/bnb/megafuel.js), pilot dual-protocol endpoint [api/x402/three-intel.js](api/x402/three-intel.js) | In-repo · shipped, settlement needs merchant creds | three.ws speaks MPP (BNB Chain's Machine Payments Protocol) additively alongside x402: MPP's `b402` layer is x402 v2 byte-for-byte (same `X-PAYMENT`/`X-PAYMENT-RESPONSE`, same EIP-3009 credential), so a dual-protocol endpoint just advertises an extra BNB (`eip155:56`/`97`) accept entry and routes BNB-network payments to the b402 facilitator while Solana/Base traffic stays on the untouched x402 path. Verify (off-chain, free, replay-guarded via Redis `SET NX PX`) always runs before settle; without `B402_*` merchant credentials, settle fails closed with `mpp_not_configured` (503) rather than fabricating a receipt. Guide: [docs/bnb-payments.md](docs/bnb-payments.md). Wire contract: [specs/x402-mpp-bridge.md](specs/x402-mpp-bridge.md). Tests: [tests/bnb-mpp-server.test.js](tests/bnb-mpp-server.test.js), [tests/bnb-mpp-buyer.test.js](tests/bnb-mpp-buyer.test.js). |
| Seeker / Saga dApp Store app | [solana-mobile/](solana-mobile): TWA wrapper [solana-mobile/twa/](solana-mobile/twa), Publisher Portal listing copy [solana-mobile/publish/](solana-mobile/publish), MWA wallet + Seeker detection [solana-mobile/src/](solana-mobile/src) | Live · v1.0.0 on the Solana dApp Store (submitted 2026-08-28, approved 2026-09-01) | Everything needed to package three.ws as a Solana Mobile app and publish it to the on-chain dApp Store. Targets Seeker first; compatible with Saga Gen 1 and Gen 2. Docs: [solana-mobile/README.md](solana-mobile/README.md) |
-| iOS App Store app | [ios/](ios): Capacitor shell + config [ios/capacitor.config.ts](ios/capacitor.config.ts), Xcode project [ios/native/App/](ios/native/App), web-side native bridge [ios/src/native-bridge.js](ios/src/native-bridge.js), offline shell [ios/shell/](ios/shell), listing copy [ios/publish/](ios/publish), app association handler in [api/wk.js](api/wk.js) | In-repo · project builds and the web half ships on every deploy · awaiting an Apple Developer organization account | three.ws as a native iOS app (`ws.three.app`). A Capacitor 8 shell whose WKWebView runs the live `https://three.ws`, so the app is never a version behind the site; what makes it an app is the native layer around it. `ios/src/native-bridge.js` ships with the SITE, not the .ipa (Capacitor injects its bridge into the remote page, so `window.Capacitor` exists on three.ws only inside the app): it supplies the `navigator.share` WKWebView does not have, routes off-site links to an in-app Safari sheet instead of stranding the app's only WebView, handles universal links and `threews://` wallet returns, holds the launch screen until the first real frame, and marks `html.ios-app`. The `three-ws-ios-native-bridge` plugin in [vite.config.js](vite.config.js) copies it into `dist/` content-hashed and injects it into every built page except the third-party embed entries (671 pages, `/viewer` and `/ar` included, which a `transformIndexHtml` could not reach because they are copied verbatim from `public/`). `GET /.well-known/apple-app-site-association` is served from the API rather than a static file because Apple demands an exact path, a JSON content type and no redirect; it answers `503 not_configured` until `APPLE_TEAM_ID` is set rather than publishing an association that would fail silently on device. The app also carries the **CarPlay** scene for three.ws Drive: `CarPlaySceneDelegate` renders the car screen's templates while `DriveLink` bridges them to `/drive` in the WebView, gated behind the `com.apple.developer.carplay-voice-based-conversation` entitlement, which is inert until Apple grants it. Docs: [ios/README.md](ios/README.md), [docs/ios-app.md](docs/ios-app.md), App Review posture [ios/docs/REVIEW-RISK.md](ios/docs/REVIEW-RISK.md), submission [ios/docs/SUBMISSION.md](ios/docs/SUBMISSION.md), CarPlay [ios/docs/CARPLAY.md](ios/docs/CARPLAY.md). |
+| iOS App Store app | [ios/](ios): Capacitor shell + config [ios/capacitor.config.ts](ios/capacitor.config.ts), Xcode project [ios/native/App/](ios/native/App), web-side native bridge [ios/src/native-bridge.js](ios/src/native-bridge.js), offline shell [ios/shell/](ios/shell), listing copy [ios/publish/](ios/publish), app association handler in [api/wk.js](api/wk.js) | In-repo · project builds and the web half ships on every deploy · awaiting an Apple Developer organization account | three.ws as a native iOS app (`ws.three.app`). A Capacitor 8 shell whose WKWebView runs the live `https://three.ws`, so the app is never a version behind the site; what makes it an app is the native layer around it. `ios/src/native-bridge.js` ships with the SITE, not the .ipa (Capacitor injects its bridge into the remote page, so `window.Capacitor` exists on three.ws only inside the app): it supplies the `navigator.share` WKWebView does not have, routes off-site links to an in-app Safari sheet instead of stranding the app's only WebView, handles universal links and `threews://` wallet returns, holds the launch screen until the first real frame, and marks `html.ios-app`. The `three-ws-ios-native-bridge` plugin in [vite.config.js](vite.config.js) copies it into `dist/` content-hashed and injects it into every built page except the third-party embed entries (671 pages, `/viewer` and `/ar` included, which a `transformIndexHtml` could not reach because they are copied verbatim from `public/`). `GET /.well-known/apple-app-site-association` is served from the API rather than a static file because Apple demands an exact path, a JSON content type and no redirect; it answers `503 not_configured` until `APPLE_TEAM_ID` is set rather than publishing an association that would fail silently on device. The app also carries the **CarPlay** scene for three.ws Drive: `CarPlaySceneDelegate` renders the car screen's templates while `DriveLink` bridges them to `/drive` in the WebView, gated behind the `com.apple.developer.carplay-voice-based-conversation` entitlement, which is inert until Apple grants it. Docs: [ios/README.md](ios/README.md), [docs/ios-app.md](docs/ios-app.md), App Review posture [ios/docs/REVIEW-RISK.md](ios/docs/REVIEW-RISK.md), submission [ios/docs/SUBMISSION.md](ios/docs/SUBMISSION.md), CarPlay [ios/docs/CARPLAY.md](ios/docs/CARPLAY.md). The project also carries the **Agent glance** WidgetKit extension (`ws.three.app.glance`, iOS 17+), whose sources live in [apple/](apple/README.md) and are shared byte for byte with the Mac app. |
+| three.ws Glance for Mac | [apple/](apple/README.md): shared sources [apple/GlanceKit/](apple/GlanceKit), WidgetKit extension [apple/GlanceWidget/](apple/GlanceWidget), menu bar host app [apple/macos/](apple/macos) (XcodeGen spec [apple/macos/project.yml](apple/macos/project.yml)), icon [apple/scripts/make-macos-icon.mjs](apple/scripts/make-macos-icon.mjs) | In-repo · builds with XcodeGen and a Development Team · Developer ID distribution, so it needs no App Store review | The agent in a Mac's Notification Centre, and the same extension on iPhone. A menu bar app whose whole job is to hold a revocable widget token and prove it works: the Mac never sees a password, because signing in happens on three.ws and the page hands back the token through `threews://glance/link` or as a code to paste. The widget fetches `GET /api/glance/mine?format=png` on the system timeline, in both themes so it follows the reader's appearance, caches the last card in the shared App Group container so an offline Mac shows yesterday's card with the time on it, and opens the agent on click. One set of sources builds for both platforms; only the project differs, because an App Group identifier on a Developer ID Mac must carry the team prefix that the same group on iPhone must not. Guard: [scripts/check-apple-widget.mjs](scripts/check-apple-widget.mjs) (`npm run check:apple-widget`, in `npm run gate`) proves both Xcode projects and the client-to-server contract on a machine with no Xcode. Docs: [apple/README.md](apple/README.md), [docs/native-widgets.md](docs/native-widgets.md). |
| Walk Avatar browser extension | [extensions/walk-avatar/](extensions/walk-avatar) — MV3 `manifest.json`, `background.js` | In-repo · Chrome Web Store release checklist staged ([RELEASE.md](extensions/walk-avatar/RELEASE.md)) | Walks your three.ws avatar across any site and reads pages aloud — a browsing companion built on the same rig as the [walk-sdk](walk-sdk). Ships its own store-required [PRIVACY.md](extensions/walk-avatar/PRIVACY.md), [PERMISSIONS.md](extensions/walk-avatar/PERMISSIONS.md), and [TERMS.md](extensions/walk-avatar/TERMS.md). |
| Checkout companion browser extension | [extensions/checkout-companion/](extensions/checkout-companion) (MV3: [extract.js](extensions/checkout-companion/extract.js), [content.js](extensions/checkout-companion/content.js), [panel.js](extensions/checkout-companion/panel.js), [background.js](extensions/checkout-companion/background.js)), analysis [api/_lib/companion/checkout.js](api/_lib/companion/checkout.js), endpoint [api/companion/checkout.js](api/companion/checkout.js) | In-repo | The companion at the moment money moves: on a checkout page it reports the total against the price you were shown, money the page did not itemise, fees named and summed, whether the charge repeats, and the cancellation terms. **Arithmetic is never the model's job** (integer minor units, computed server-side) and **no finding is ever a legal verdict** (`sanitizeModelFindings()` drops any that claims an amount or calls something illegal). With no model reachable the arithmetic findings still stand. The extension **never reads an input**: `collectText`/`collectAmounts` refuse form fields, iframes and editable regions structurally, and redaction runs in the browser before anything is sent; only the hostname travels and nothing about the page is stored. Docs: [docs/checkout-companion.md](docs/checkout-companion.md). Tests: [tests/companion-checkout.test.js](tests/companion-checkout.test.js), [tests/checkout-extract.test.js](tests/checkout-extract.test.js) |
| Desktop companion app | [apps/desktop/](apps/desktop). Electron main [src/main.js](apps/desktop/src/main.js), preload [src/preload.cjs](apps/desktop/src/preload.cjs), stage [src/renderer/](apps/desktop/src/renderer) | In-repo · packaged with electron-builder (`npm run dist`), not yet published | A transparent, click-through, always-on-top character that strolls across the bottom of the desktop and walks over to deliver what cleared the user's bar. Subscribes to `/api/companion/stream` with the same bridge token the CLI stores, and drives the published [walk embed](pages/walk-embed.html) over its postMessage contract, so it carries no 3D code of its own. Not an npm workspace: it installs and builds on its own (see [apps/desktop/README.md](apps/desktop/README.md)). |
diff --git a/data/changelog.json b/data/changelog.json
index afd162cce..76ceb4508 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,25 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-09-03",
+ "title": "Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple",
+ "summary": "The widget that has been on Android home screens and the Windows 11 widgets board now runs on Apple platforms too, from one WidgetKit extension shared by both. On a Mac it lives in Notification Centre in small, medium or large, fed by a small menu bar app that shows the same card and carries Open my agent, Refresh now and Unlink this Mac. On iPhone and iPad it is a home screen widget inside the three.ws app. Linking is one press on three.ws/glance: the page hands the device its own token, and if nothing opens (a Mac whose browser is signed in elsewhere) it shows a code to paste instead. The widget refreshes about every half hour without you opening anything, follows light and dark mode because it fetches the card in both, keeps the last card it downloaded when you are offline and says when that was rather than showing a spinner, and opens your agent on a tap. Every linked device is listed on three.ws/glance with a revoke button, and each token can only ever read your glance card.",
+ "tags": [
+ "feature"
+ ],
+ "link": "/glance"
+ },
+ {
+ "date": "2026-09-03",
+ "title": "Daily Forge shows the day's theme again",
+ "summary": "Daily Forge is built around one thing: the challenge of the day. That headline was being wiped out a moment after the page loaded. The translation layer runs after the page fetches its language file, and it was overwriting the day's theme with the placeholder text baked into the HTML, so every visitor read \"Today's theme\" and \"Loading today's challenge\" forever while the starter prompt and the idea chips below quietly described a completely different subject. The theme, its emoji, its hint and the browser tab title now hold. Four more fixes landed with it: a failed generation says \"Could not reach the forge, check your connection\" instead of the browser's raw \"Failed to fetch\"; when a model finishes but the preview cannot show it, the Download button the message points at is now actually clickable instead of sitting underneath the message; every button and link has a visible focus outline for keyboard and screen-reader users, and the streak milestone popup takes focus, closes on Escape and hands focus back; and a browser without 3D support now still sees today's theme and a clear explanation instead of a permanent loading line. The community strip at the bottom also fills in properly rather than staying empty.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/daily"
+ },
{
"date": "2026-09-03",
"title": "Every SDK doc now points at code you can actually run",
diff --git a/prompts/roadmap/_generated/reuse-map-audit/gate-after.txt b/prompts/roadmap/_generated/reuse-map-audit/gate-after.txt
index 2d7e2b722..1381e4f70 100644
--- a/prompts/roadmap/_generated/reuse-map-audit/gate-after.txt
+++ b/prompts/roadmap/_generated/reuse-map-audit/gate-after.txt
@@ -1,6 +1,6 @@
-> npm run check:conflicts && npm run check:claude && npm run check:vendored && npm run check:fetch-timeouts && npm run check:tdz-bootstrap && npm run check:event && npm run check:cron-syntax && npm run check:studio-openapi && npm run test:gate && npm run test:gate-3d && npm run audit:mcp && npm run audit:mcp-golden && npm run audit:mcp-safety && npm run audit:mcp-catalog && npm run audit:routes && npm run audit:handlers && npm run audit:pages && npm run audit:links && npm run audit:docs && npm run audit:upstreams && npm run check:tutorials && npm run audit:hidden-guard && npm run audit:inline-handlers && npm run audit:x402-catalog && npm run audit:tokens && npm run audit:guards && npm run audit:tour-atlas && npm run check:ios-icons
+> npm run check:conflicts && npm run check:claude && npm run check:vendored && npm run check:fetch-timeouts && npm run check:tdz-bootstrap && npm run check:event && npm run check:cron-syntax && npm run check:studio-openapi && npm run test:gate && npm run test:gate-3d && npm run audit:mcp && npm run audit:mcp-golden && npm run audit:mcp-safety && npm run audit:mcp-catalog && npm run audit:routes && npm run audit:handlers && npm run audit:pages && npm run audit:links && npm run audit:docs && npm run audit:upstreams && npm run check:tutorials && npm run audit:hidden-guard && npm run audit:inline-handlers && npm run audit:x402-catalog && npm run audit:tokens && npm run audit:guards && npm run audit:tour-atlas && npm run check:ios-icons && npm run check:macos-icon && npm run check:apple-widget
> [email protected] check:conflicts
@@ -26,7 +26,7 @@ check:fetch-timeouts: every external fetch, and every fetch under api/, is bound
> [email protected] check:tdz-bootstrap
> node scripts/check-tdz-bootstrap.mjs
-check:tdz-bootstrap: no bootstrap-before-state ordering in 1597 browser module(s)
+check:tdz-bootstrap: no bootstrap-before-state ordering in 1601 browser module(s)
> [email protected] check:event
> node scripts/check-event-window.mjs
@@ -61,8 +61,8 @@ All cron expressions are valid (offline mode: live jobs not compared).
Test Files 7 passed (7)
Tests 86 passed (86)
- Start at 07:25:43
- Duration 2.93s (transform 2.66s, setup 0ms, import 5.30s, tests 2.79s, environment 1ms)
+ Start at 07:35:07
+ Duration 6.15s (transform 6.62s, setup 0ms, import 15.33s, tests 4.00s, environment 1ms)
[test-gate] ✓ all critical-path tests passed
@@ -75,8 +75,8 @@ All cron expressions are valid (offline mode: live jobs not compared).
Test Files 4 passed (4)
Tests 559 passed (559)
- Start at 07:25:46
- Duration 692ms (transform 400ms, setup 0ms, import 948ms, tests 502ms, environment 1ms)
+ Start at 07:35:15
+ Duration 1.95s (transform 1.01s, setup 0ms, import 2.60s, tests 1.37s, environment 1ms)
> [email protected] audit:mcp
@@ -87,26 +87,70 @@ All cron expressions are valid (offline mode: live jobs not compared).
> [email protected] audit:mcp-golden
> node scripts/audit-mcp-golden.mjs
-[audit:mcp-golden] api/_mcp3d/tools/sim-readiness.js: tool ADDED: grade_sim_readiness
+[audit:mcp-golden] 307 hosted MCP tool contracts match the golden fixture
-[audit:mcp-golden] 1 contract change(s) vs golden fixture.
- If every change above is INTENTIONAL (reviewed as a public-contract change),
- refresh the fixture: node scripts/audit-mcp-golden.mjs --update
-exit=1
+> [email protected] audit:mcp-safety
+> node scripts/audit-mcp-safety.mjs
+
+[audit:mcp-safety] 307 MCP tool annotations verified against handler behavior across 248 files, 6 reviewed exemption(s)
+
+> [email protected] audit:mcp-catalog
+> node scripts/build-mcp-catalog.mjs --check
+
+[audit:mcp-catalog] catalog matches source: 307 tools across 40 servers
+
+> [email protected] audit:routes
+> node scripts/verify-routes.mjs --strict
+
+Route verify — 791 catalog pages, 1311 main routes, 1 post-filesystem routes.
+ modeled dist files: 2934 · canonical-covered: 791 · literal page routes checked for shadows: 582
+ filesystem boundary (handle:filesystem) present: yes
+
+✓ static checks pass: every catalog page reachable, unknown paths → designed 404, no shadowed page routes.
+
+> [email protected] audit:handlers
+> node scripts/audit-empty-handlers.mjs
+
+✓ audit-empty-handlers: all API handlers export a body (2195 checked)
+
+> [email protected] audit:pages
+> node scripts/audit-page-index.mjs --strict
+
+Route audit: 166 auditable page routes, 791 documented in pages.json.
+✓ Every auditable page route is documented.
+
+> [email protected] audit:links
+> node scripts/audit-links.mjs
+
+Link audit — scanned 2253 files
---- audit note (agent, 2026-09-03) ---
-gate-before failed at test:gate (tests/api/healthz.test.js could not import:
-the db mock threw synchronously, killing api/_lib/home/store.js's module-scope
-sql fragment). That failure short-circuited the chain, so gate-before never
-reached audit:mcp-golden.
-
-gate-after clears every stage that gate-before reached, plus the ones it could
-not: test:gate 7/7 (was 6 passed, 1 failed), test:gate-3d 4/4, audit:mcp 49
-manifests consistent.
-
-The single remaining failure, audit:mcp-golden reporting grade_sim_readiness
-ADDED, comes from api/_mcp3d/tools/sim-readiness.js, an UNTRACKED file belonging
-to a concurrent agent in this shared worktree. It is not part of this work and
-the golden fixture was deliberately left alone: refreshing it would rubber-stamp
-another agent's unreviewed public MCP contract change. That agent should run
-`node scripts/audit-mcp-golden.mjs --update` when it commits.
+Broken internal links : 0
+
+Stub hrefs (#, void(0)) : 0
+
+Dangling routes (→ missing file) : 0
+
+External links collected : 556
+ (run with --external to probe liveness)
+
+Dynamic targets skipped : 1371
+
+> [email protected] audit:docs
+> node scripts/audit-docs.mjs
+
+docs audit: clean (1511 markdown files checked).
+
+> [email protected] audit:upstreams
+> node scripts/audit-upstreams.mjs
+
+audit:upstreams: 225 outbound call sites across 79 upstreams (A:0 B:54 C:92 D:79 F:0)
+audit:upstreams: no regressions
+
+> [email protected] check:tutorials
+> node scripts/sync-tutorial-pages.mjs
+
+manifest entries: 70 markdown files: 70
+pages.json: missing 1 tutorial entry
+
+Tutorial drift found. Fix the manifest, or run: node scripts/sync-tutorial-pages.mjs --write
+exit=1
diff --git a/public/changelog.json b/public/changelog.json
index 6f715fc03..b4f11eb5a 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T07:32:51.766Z",
+ "generated_at": "2026-09-03T07:36:51.546Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -262,6 +262,17 @@
"feature"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Daily Forge shows the day's theme again",
+ "summary": "Daily Forge is built around one thing: the challenge of the day. That headline was being wiped out a moment after the page loaded. The translation layer runs after the page fetches its language file, and it was overwriting the day's theme with the placeholder text baked into the HTML, so every visitor read \"Today's theme\" and \"Loading today's challenge\" forever while the starter prompt and the idea chips below quietly described a completely different subject. The theme, its emoji, its hint and the browser tab title now hold. Four more fixes landed with it: a failed generation says \"Could not reach the forge, check your connection\" instead of the browser's raw \"Failed to fetch\"; when a model finishes but the preview cannot show it, the Download button the message points at is now actually clickable instead of sitting underneath the message; every button and link has a visible focus outline for keyboard and screen-reader users, and the streak milestone popup takes focus, closes on Escape and hands focus back; and a browser without 3D support now still sees today's theme and a clear explanation instead of a permanent loading line. The community strip at the bottom also fills in properly rather than staying empty.",
+ "link": "/daily",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
@@ -523,6 +534,16 @@
"docs"
]
},
+ {
+ "date": "2026-09-03",
+ "type": "update",
+ "title": "Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple",
+ "summary": "The widget that has been on Android home screens and the Windows 11 widgets board now runs on Apple platforms too, from one WidgetKit extension shared by both. On a Mac it lives in Notification Centre in small, medium or large, fed by a small menu bar app that shows the same card and carries Open my agent, Refresh now and Unlink this Mac. On iPhone and iPad it is a home screen widget inside the three.ws app. Linking is one press on three.ws/glance: the page hands the device its own token, and if nothing opens (a Mac whose browser is signed in elsewhere) it shows a code to paste instead. The widget refreshes about every half hour without you opening anything, follows light and dark mode because it fetches the card in both, keeps the last card it downloaded when you are offline and says when that was rather than showing a spinner, and opens your agent on a tap. Every linked device is listed on three.ws/glance with a revoke button, and each token can only ever read your glance card.",
+ "link": "/glance",
+ "tags": [
+ "feature"
+ ]
+ },
{
"date": "2026-09-03",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 42c0af407..460d359f6 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -206,6 +206,14 @@
<category>feature</category>
<description>The /smart-home page now takes you from &quot;I have a Home Assistant somewhere&quot; to a connected house, and it is honest at every step. An address that only exists on your home network is refused the moment you type it, with the two real ways round it, instead of spinning for fifteen seconds. A rejected token says so and puts the cursor back in the token box. A house that stops answering keeps its rooms on screen, marked stale with how long ago it last replied, rather than blanking out. Your access token is sent once, encrypted at rest, and never comes back to the page: it is not in your browser storage, not in a URL, and not in any response. Disconnecting says plainly that the stored token is erased and reminds you to delete it in Home Assistant too.</description>
</item>
+ <item>
+ <title>Daily Forge shows the day's theme again</title>
+ <link>https://three.ws/daily</link>
+ <guid isPermaLink="false">2026-09-03:Daily Forge shows the day's theme again</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Daily Forge is built around one thing: the challenge of the day. That headline was being wiped out a moment after the page loaded. The translation layer runs after the page fetches its language file, and it was overwriting the day's theme with the placeholder text baked into the HTML, so every visitor read &quot;Today's theme&quot; and &quot;Loading today's challenge&quot; forever while the starter prompt and the idea chips below quietly described a completely different subject. The theme, its emoji, its hint and the browser tab title now hold. Four more fixes landed with it: a failed generation says &quot;Could not reach the forge, check your connection&quot; instead of the browser's raw &quot;Failed to fetch&quot;; when a model finishes but the preview cannot show it, the Download button the message points at is now actually clickable instead of sitting underneath the message; every button and link has a visible focus outline for keyboard and screen-reader users, and the streak milestone popup takes focus, closes on Escape and hands focus back; and a browser without 3D support now still sees today's theme and a clear explanation instead of a permanent loading line. The community strip at the bottom also fills in properly rather than staying empty.</description>
+ </item>
<item>
<title>Endpoint Shopper takes payment on the page, so a paid run actually runs</title>
<link>https://three.ws/shopper</link>
@@ -398,6 +406,14 @@
<category>docs</category>
<description>Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over.</description>
</item>
+ <item>
+ <title>Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple</title>
+ <link>https://three.ws/glance</link>
+ <guid isPermaLink="false">2026-09-03:Your agent on a Mac and an iPhone: the Agent glance widget comes to Apple</guid>
+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>The widget that has been on Android home screens and the Windows 11 widgets board now runs on Apple platforms too, from one WidgetKit extension shared by both. On a Mac it lives in Notification Centre in small, medium or large, fed by a small menu bar app that shows the same card and carries Open my agent, Refresh now and Unlink this Mac. On iPhone and iPad it is a home screen widget inside the three.ws app. Linking is one press on three.ws/glance: the page hands the device its own token, and if nothing opens (a Mac whose browser is signed in elsewhere) it shows a code to paste instead. The widget refreshes about every half hour without you opening anything, follows light and dark mode because it fetches the card in both, keeps the last card it downloaded when you are offline and says when that was rather than showing a spinner, and opens your agent on a tap. Every linked device is listed on three.ws/glance with a revoke button, and each token can only ever read your glance card.</description>
+ </item>
<item>
<title>Your Home Assistant voice assistant can have a face now</title>
<link>https://three.ws/smart-home/satellite</link>
diff --git a/public/features.json b/public/features.json
index 1f77caf4a..5a42f0b23 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-03T07:32:51.716Z",
+ "generated_at": "2026-09-03T07:36:51.510Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",