Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(guards): register the live Windows widget probe so it is findable from the registry
nirholasdc285df25261
diff --git a/data/guards.json b/data/guards.jsonindex d65fbd6b0..8d1426f9e 100644--- a/data/guards.json+++ b/data/guards.json@@ -839,9 +839,12 @@"id": "check-windows-widget","script": "scripts/check-windows-widget.mjs","npm": "check:windows-widget",+ "npmAliases": [+ "check:windows-widget:live"+ ],"title": "The Windows 11 glance widget still satisfies the board's contract",- "protects": "The widgets member in vite.config.js, the glance service worker, the two glance endpoints and the Adaptive Card all agree with each other: every field the board requires is present, the declared icons and screenshots exist at the sizes claimed, the worker handles all six board lifecycle events, fetches the card rather than handing the host its URL, registers the refresh interval the manifest advertises, and the card expands in the board's own templating engine for every state with no unbound expressions and no dead button targets.",- "why": "The widgets board is the one surface nothing in this repository can open: it needs Windows 11, Edge, and the PWA installed. A broken slot renders as nothing at all rather than as an error, so every defect here is silent twice over, invisible locally and invisible to the user. Four have already reached that state while every other check stayed green: the worker passing the host a template URL where the card belonged, no periodic sync ever registered, a slot pinned before the worker activated staying empty, and a card written with JavaScript array paths that the board's expression engine refuses to parse. That last one is why this runs the real engine instead of reading the template with our own idea of a path: `${stats.0.label}` resolves in JavaScript and is a syntax error in Adaptive Expression Language, and the engine throws away the whole card rather than skipping the one binding, so a single dotted index empties the widget.",+ "protects": "The widgets member in vite.config.js, the glance service worker, the two glance endpoints and the Adaptive Card all agree with each other: every field the board requires is present, the declared icons and screenshots exist at the sizes claimed, the worker handles all six board lifecycle events, fetches the card rather than handing the host its URL, registers the refresh interval the manifest advertises, and the card expands in the board's own templating engine for every state with no unbound expressions and no dead button targets. The `:live` alias asks the same questions of a deployed origin instead of this disk: that the served manifest declares the widget this tree does, that the served worker is byte-identical to public/glance-sw.js, that the picker assets are really served as images, and that the Adaptive Card the board would fetch expands in that engine when bound with the deployed worker's own payload builder.",+ "why": "The widgets board is the one surface nothing in this repository can open: it needs Windows 11, Edge, and the PWA installed. A broken slot renders as nothing at all rather than as an error, so every defect here is silent twice over, invisible locally and invisible to the user. Four have already reached that state while every other check stayed green: the worker passing the host a template URL where the card belonged, no periodic sync ever registered, a slot pinned before the worker activated staying empty, and a card written with JavaScript array paths that the board's expression engine refuses to parse. That last one is why this runs the real engine instead of reading the template with our own idea of a path: `${stats.0.label}` resolves in JavaScript and is a syntax error in Adaptive Expression Language, and the engine throws away the whole card rather than skipping the one binding, so a single dotted index empties the widget. A fifth class stands behind those four, and it is what the `:live` alias exists for: a fix that is green in this tree and absent from the deploy. On 2026-09-09 every check on this disk passed while production served the unparseable card, so the widget stayed broken for exactly as long as nobody thought to ask the deployed origin. Offline agreement is not evidence that a pinned slot draws; only the served bytes are.","stages": ["gate"],diff --git a/docs/guards.md b/docs/guards.mdindex 36994b2ea..339ffa1a8 100644--- a/docs/guards.md+++ b/docs/guards.md@@ -114,6 +114,7 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| macOS app icon | `npm run check:macos-icon` | The ten committed Mac icon sizes and their Contents.json are exactly what the current brand mark produces. || Apple glance widget | `npm run check:apple-widget` | Both Xcode projects that build the Agent glance widget are consistent, every shared Swift source belongs to the targets that need it, and the Swift client still agrees with `api/glance/mine.js` on the endpoint, the headers, the states, the sizes and the token shape. || Windows glance widget | `npm run check:windows-widget` | The widgets member in `vite.config.js`, the glance service worker, the two glance endpoints and the Adaptive Card all agree: every field the board requires is present, the declared icons and screenshots exist at the sizes claimed, the worker handles all six board lifecycle events and registers the advertised refresh, and the card expands in the board's own templating engine with no unbound expressions and no dead button targets. |+| Windows glance widget, as deployed | `npm run check:windows-widget:live` | The same contract against what an origin is really serving: the manifest it declares, the worker bytes it returns, the picker assets it serves, and whether the Adaptive Card the board would fetch expands in that engine when bound with the deployed worker's own payload builder. Everything above it passes on a commit that has not shipped, which is how production served a card that drew nothing while this tree was green. Needs network, so it runs on demand, after a deploy. |### Routing and pagesdiff --git a/prompts/finish/916-roadmap-native-widgets.md b/prompts/finish/916-roadmap-native-widgets.mdindex fee3847a1..c008f6e2f 100644--- a/prompts/finish/916-roadmap-native-widgets.md+++ b/prompts/finish/916-roadmap-native-widgets.md@@ -8,6 +8,11 @@ commit `880bdcef8` (2026-09-08 18:57Z) and the fix landed in `fe05babf6`(2026-09-09 05:41Z). That is now a one-command fact rather than a guess, via`npm run check:windows-widget:live` (added 2026-09-09), which binds the deployedcard with the deployed worker in the board's own engine and currently exits 1.+Re-verified 2026-09-09 19:44Z against commit `880bdcef8` (revision 00420): the+11 offline checks and the 15 Apple checks pass, and the live probe's 5 findings+are all the one undeployed card. That probe is now a registered guard+(`data/guards.json`, `docs/guards.md`, `/guards`) rather than a command only+this file mentions.**This file stays because two Definition of done lines cannot be closed from thismachine** (one needs a Windows 11 machine, one needs an Apple Developer account),and the campaign's rule is to leave a work order in place until every line of itdiff --git a/prompts/finish/_context/production-100-00-INDEX.md b/prompts/finish/_context/production-100-00-INDEX.mdindex 06497bd4e..308c20d9f 100644--- a/prompts/finish/_context/production-100-00-INDEX.md+++ b/prompts/finish/_context/production-100-00-INDEX.md@@ -95,7 +95,7 @@ run in parallel, H waits on owner gates, I is anytime, J is the parallel swarm.| Creation consolidation (retired 2026-09-02) | Redirects and the save fix shipped. Its residue (Studio wardrobe, the `/embed` retirement and the `/start` decision) is unowned by any file; re-open a numbered order under this prefix if it is picked up. || Parametric avatar editor | Done 2026-09-03: 306 sliders, server-side proportion bake, free-sculpt brush, `specs/PARAMETRIC_AVATAR.md`. || Developer resources (order retired; owner step open) | Agent side shipped: `npm run export:satellites` stages the public examples repo offline. What remains is OWNER-ACTIONS row 16 (create the org and repo, then push), and the cross-links after it. |-| [../roadmap/native-widgets.md](../916-roadmap-native-widgets.md) | All four tasks built. The card endpoint, the Android widget and the Windows manifest are live in production (re-verified 2026-09-04, including the Apple hand-off); task 4's WidgetKit extension, Mac app and iOS target are in `apple/` and guarded by `npm run check:apple-widget`. What is left is not code: signing and shipping the two Apple binaries needs row 17, and an in-board Windows check needs a Windows 11 machine. One caveat: 2026-09-04 fixed three defects in the Windows service worker (the Adaptive Card was never fetched, the refresh was never registered, a slot pinned before activation stayed empty) and 2026-09-09 fixed a fourth in the card itself (a dotted array index the board's expression engine refuses, which empties the whole widget), so run that board check only against a deploy carrying both. The worker fix is live; the card fix is not. `npm run check:windows-widget:live` decides that in one command against any origin, and it exits 1 against production as of 2026-09-09. |+| [../roadmap/native-widgets.md](../916-roadmap-native-widgets.md) | All four tasks built. The card endpoint, the Android widget and the Windows manifest are live in production (re-verified 2026-09-04, including the Apple hand-off); task 4's WidgetKit extension, Mac app and iOS target are in `apple/` and guarded by `npm run check:apple-widget`. What is left is not code: signing and shipping the two Apple binaries needs row 17, and an in-board Windows check needs a Windows 11 machine. One caveat: 2026-09-04 fixed three defects in the Windows service worker (the Adaptive Card was never fetched, the refresh was never registered, a slot pinned before activation stayed empty) and 2026-09-09 fixed a fourth in the card itself (a dotted array index the board's expression engine refuses, which empties the whole widget), so run that board check only against a deploy carrying both. The worker fix is live; the card fix is not. `npm run check:windows-widget:live` decides that in one command against any origin, and it exits 1 against production as of 2026-09-09 (re-verified 19:44Z against commit `880bdcef8`, revision 00420: 5 findings, all of them the one undeployed card, while the 11 offline checks and the 15 Apple checks pass). That probe is now a registered guard (`data/guards.json`, `docs/guards.md`, `/guards`) rather than a command only this pack mentions. || [../gcp-credits/05-catalog-animation-seeding.md](../904-gcp-credits-05-catalog-animation-seeding.md) | Partial: the catalog seed runs at scale (56,898 avatars); the generated motion library has 0 clips. || Materialize (retired 2026-09-02) | Shipped: the print engine, quote and catalog, checkout on both lanes, fulfillment adapters and the operator console, on-chain certificates, the fabrication gate, docs and `specs/PRINT_PIPELINE.md`. Evidence in [materialize-PROGRESS.md](materialize-PROGRESS.md). || Simulation readiness (retired 2026-09-03) | Shipped: all 8 build tasks. Versioned grader, applied schema and store, the free `grade_sim_readiness` MCP tool and `GET /api/sim-readiness` over one shared handler, grading on the forge write path, the signed `simReadiness` field in provenance v2 (v1 credentials still verify), the badge and details panel on `/m/:id` and `/viewer`, and `docs/sim-readiness.md`. |diff --git a/prompts/finish/_context/roadmap-00-README.md b/prompts/finish/_context/roadmap-00-README.mdindex c976c78db..cb6163df4 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. |+| [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. |### Strategy and reference (read, do not execute)diff --git a/public/guards.json b/public/guards.jsonindex d65fbd6b0..8d1426f9e 100644--- a/public/guards.json+++ b/public/guards.json@@ -839,9 +839,12 @@"id": "check-windows-widget","script": "scripts/check-windows-widget.mjs","npm": "check:windows-widget",+ "npmAliases": [+ "check:windows-widget:live"+ ],"title": "The Windows 11 glance widget still satisfies the board's contract",- "protects": "The widgets member in vite.config.js, the glance service worker, the two glance endpoints and the Adaptive Card all agree with each other: every field the board requires is present, the declared icons and screenshots exist at the sizes claimed, the worker handles all six board lifecycle events, fetches the card rather than handing the host its URL, registers the refresh interval the manifest advertises, and the card expands in the board's own templating engine for every state with no unbound expressions and no dead button targets.",- "why": "The widgets board is the one surface nothing in this repository can open: it needs Windows 11, Edge, and the PWA installed. A broken slot renders as nothing at all rather than as an error, so every defect here is silent twice over, invisible locally and invisible to the user. Four have already reached that state while every other check stayed green: the worker passing the host a template URL where the card belonged, no periodic sync ever registered, a slot pinned before the worker activated staying empty, and a card written with JavaScript array paths that the board's expression engine refuses to parse. That last one is why this runs the real engine instead of reading the template with our own idea of a path: `${stats.0.label}` resolves in JavaScript and is a syntax error in Adaptive Expression Language, and the engine throws away the whole card rather than skipping the one binding, so a single dotted index empties the widget.",+ "protects": "The widgets member in vite.config.js, the glance service worker, the two glance endpoints and the Adaptive Card all agree with each other: every field the board requires is present, the declared icons and screenshots exist at the sizes claimed, the worker handles all six board lifecycle events, fetches the card rather than handing the host its URL, registers the refresh interval the manifest advertises, and the card expands in the board's own templating engine for every state with no unbound expressions and no dead button targets. The `:live` alias asks the same questions of a deployed origin instead of this disk: that the served manifest declares the widget this tree does, that the served worker is byte-identical to public/glance-sw.js, that the picker assets are really served as images, and that the Adaptive Card the board would fetch expands in that engine when bound with the deployed worker's own payload builder.",+ "why": "The widgets board is the one surface nothing in this repository can open: it needs Windows 11, Edge, and the PWA installed. A broken slot renders as nothing at all rather than as an error, so every defect here is silent twice over, invisible locally and invisible to the user. Four have already reached that state while every other check stayed green: the worker passing the host a template URL where the card belonged, no periodic sync ever registered, a slot pinned before the worker activated staying empty, and a card written with JavaScript array paths that the board's expression engine refuses to parse. That last one is why this runs the real engine instead of reading the template with our own idea of a path: `${stats.0.label}` resolves in JavaScript and is a syntax error in Adaptive Expression Language, and the engine throws away the whole card rather than skipping the one binding, so a single dotted index empties the widget. A fifth class stands behind those four, and it is what the `:live` alias exists for: a fix that is green in this tree and absent from the deploy. On 2026-09-09 every check on this disk passed while production served the unparseable card, so the widget stayed broken for exactly as long as nobody thought to ask the deployed origin. Offline agreement is not evidence that a pinned slot draws; only the served bytes are.","stages": ["gate"],