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(widgets): the Windows board check is unblocked, its live guard now passes against production

nirholas898011696bd2
diff --git a/prompts/finish/916-roadmap-native-widgets.md b/prompts/finish/916-roadmap-native-widgets.md
index c008f6e2f..96b05a566 100644
--- a/prompts/finish/916-roadmap-native-widgets.md
+++ b/prompts/finish/916-roadmap-native-widgets.md
@@ -51,11 +51,16 @@ Neither line is code, and neither can be closed from this machine.
with the signed-in account's real card, refreshes, and that its click targets
land on the right routes. Owner, or anyone with a Windows 11 machine.
- **Run it against a deploy that carries 2026-09-09's card fix**, and do not
- spend the trip before then: `npm run check:windows-widget:live` answers that
- in one command, and today it exits 1 with `the deployed Adaptive Card differs
- from api/_lib/glance-adaptive.js`. When it goes green, the deploy carries the
- fix and the board check is worth a human's time. Everything about this line
+ **This precondition is now MET, re-measured 2026-09-10.** The guard exists so
+ nobody spends the trip on a stale origin, and it has gone green:
+ `npm run check:windows-widget:live` now passes all 16 checks against
+ `https://three.ws`, including `the deployed Adaptive Card is the one this tree
+ generates`, `the deployed worker is byte-identical to public/glance-sw.js` and
+ `the deployed card binds the live response and all 3 states in the board's
+ engine`. It exited 1 as recently as 2026-09-09 with `the deployed Adaptive Card
+ differs from api/_lib/glance-adaptive.js`; a deploy has since carried the card
+ fix. **So the board check is worth a human's time now.** Re-run the one command
+ before travelling anyway, since a later deploy could regress it. Everything about this line
that can be checked without a board now is, mechanically: 11 offline checks
in `npm run gate`, plus 5 more against the deployed origin. What is left for
the human is genuinely only "a person sees the pixels".
diff --git a/prompts/finish/_context/roadmap-00-README.md b/prompts/finish/_context/roadmap-00-README.md
index cb6163df4..dcdeb062d 100644
--- a/prompts/finish/_context/roadmap-00-README.md
+++ b/prompts/finish/_context/roadmap-00-README.md
@@ -88,7 +88,7 @@ retired; they remain readable in git history
|---|---|---|
| [generation-suite.md](../009-roadmap-generation-suite.md) | Meshy and Tripo class parity, and production truth for every generation endpoint | Open. Step 0 and tasks 1 and 2 are done (2026-09-03): the truth table was rebuilt from live probes, and every row is green except the undeployed talking-avatar lane. That sweep found the default free image lane failing 44 of 49 generations for 12 hours while every status surface read green; it is restored and hardened, and `trellis_selfhost` now has a live health probe. Tasks 3 to 8 (pipeline tools in `/forge`, preview then refine, export formats, PBR controls, job webhooks, community gallery) are untouched. |
| [developer-resources-repos.md](roadmap-developer-resources-repos.md) | The public examples satellite repo and its one-way export | Done, retired 2026-09-03. `npm run export:satellites` stages 72 files and passes all four smoke stages; the docs, `llms.txt` and `llms-full.txt` cross-links are live. Only the owner-gated publish remains (create the `three-ws` org, run the printed push), tracked as row 16 of [production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md). |
-| [native-widgets.md](../916-roadmap-native-widgets.md) | Native widgets on the Android, Windows, macOS and iOS home screens | Built, all four surfaces. Android and Windows are live in production; the Apple sources are in `apple/`. Open only on what code cannot do: an Apple Developer account to sign the two binaries (owner action 17) and a Windows 11 machine for the in-board check, which wants a deploy carrying 2026-09-09's Adaptive Card fix. Whether a given origin carries it is no longer a guess: `npm run check:windows-widget:live` binds the deployed card with the deployed worker in the board's own engine, and it exits 1 against production today. It is registered in `data/guards.json` and `docs/guards.md` as of 2026-09-09, so the next agent finds it from the guard registry instead of from this pack. |
+| [native-widgets.md](../916-roadmap-native-widgets.md) | Native widgets on the Android, Windows, macOS and iOS home screens | Built, all four surfaces. Android and Windows are live in production; the Apple sources are in `apple/`. Open only on what code cannot do: an Apple Developer account to sign the two binaries (owner action 17) and a Windows 11 machine for the in-board check, which wants a deploy carrying 2026-09-09's Adaptive Card fix. Whether a given origin carries it is no longer a guess: `npm run check:windows-widget:live` binds the deployed card with the deployed worker in the board's own engine. **It went green against production on 2026-09-10**, all 16 checks including the deployed card, worker and state bindings, so the Windows half is now waiting only on a human with a Windows 11 machine rather than on a deploy. It is registered in `data/guards.json` and `docs/guards.md` as of 2026-09-09, so the next agent finds it from the guard registry instead of from this pack. |
### Strategy and reference (read, do not execute)