Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(guards): register the two gate steps the registry never listed, and stop a slash pointer reading as a rotted guard
nirholasd7b6e22cfe09
diff --git a/data/guards.json b/data/guards.jsonindex 60406fc4b..d65fbd6b0 100644--- a/data/guards.json+++ b/data/guards.json@@ -857,6 +857,58 @@"expect": "is declared but"}},+ {+ "id": "check-home-matrix",+ "script": "scripts/home-version-matrix.mjs",+ "npm": "check:home-matrix",+ "title": "The published Home Assistant support table is the one that was measured",+ "protects": "The version table in docs/smart-home.md is exactly what the last real matrix run wrote into docs/ops/home-version-matrix.json: the same releases, the same roles and install shares, and the same per-capability result for connect, registries, stream and call.",+ "why": "The home lane's correctness depends on a third party's monthly release, and the table is the only place we tell anyone which Home Assistant versions we support. The measurement is expensive (four containers, thirteen gigabytes, pulled and destroyed one at a time), so it is deliberately not run on every gate; what the gate can afford is proving that the cheap, published half still agrees with the expensive, measured half. Without that, the table decays into a claim: a run whose JSON landed but whose doc edit did not, or a doc edited by hand to say what someone hoped, both read as a supported version to every reader and to us.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "kind": "mutation",+ "summary": "The measured matrix says one thing and the published table another.",+ "violation": {+ "json": [+ {+ "file": "docs/ops/home-version-matrix.json",+ "pointer": "results.0.tag",+ "set": "1999.1"+ }+ ]+ },+ "expect": "is stale"+ }+ },+ {+ "id": "i18n-home",+ "script": "scripts/i18n-home-keys.mjs",+ "npm": "i18n:home",+ "title": "Every string the connected home speaks has a catalog key",+ "protects": "Each `t()` and `plural()` call site under the home lane resolves to a key in public/locales/en.json whose English source value is byte-identical to the fallback written in the code, and no source value smuggles a template expression into a translatable string.",+ "why": "The HTML extractor reads `data-i18n` annotations, which covers the lane's page shells and misses the house itself: the rooms, the devices, the refusals, the confirmation and every spoken announcement are assembled in JS from live data and carry no markup to annotate. A new string added there is simply English forever in all 84 locales, and nothing complains, because the fallback argument renders perfectly. Drift is the quieter half: edit the English in the code and the catalog keeps serving the old sentence to every translated locale, so the product says two different things depending on the reader's language. The template-expression refusal guards a worse outcome, a user's own room or device name baked into a source string and machine-translated on the next run.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "kind": "mutation",+ "summary": "The catalog's English keeps a sentence the code no longer says.",+ "violation": {+ "json": [+ {+ "file": "public/locales/en.json",+ "pointer": "home_scene.act_close",+ "set": "Shut"+ }+ ]+ },+ "expect": "drift:"+ }+ },{"id": "check-awesome","script": "scripts/build-awesome.mjs",diff --git a/docs/guards.md b/docs/guards.mdindex 7a7cff6be..36994b2ea 100644--- a/docs/guards.md+++ b/docs/guards.md@@ -137,6 +137,8 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| Documentation integrity | `npm run audit:docs` | No dead relative link, no command naming a missing script, no package without a README. || Upstream resilience ratchet | `npm run audit:upstreams` | No new call to a third-party service without a deadline, and no existing one quietly getting weaker. || Tutorial reachability | `npm run check:tutorials` | Every tutorial appears in the library manifest, has its markdown on disk, and is registered in `data/pages.json`. |+| Home lane translation keys | `npm run i18n:home` | Every string the connected home speaks from JS has a key in `public/locales/en.json` whose English matches the code exactly, and no source value bakes a user's own room or device name into a translatable sentence. |+| Home Assistant support table | `npm run check:home-matrix` | The version table in [smart-home.md](smart-home.md) is exactly what the last real matrix run measured, so a supported release is a measurement rather than a claim. || Runnable doc samples | `npm run check:runnable-docs` | Every sample a reader can press Run on still returns what the doc says it returns. || Doc figures | `npm run check:doc-media` | Every figure a doc points at was really captured, still matches its recipe, and carries alt text. || Announcement packs | `npm run check:announce` | Every announcement pack ships captured media with alt text, a post inside X's real weighted limit, an opening no other pack reuses, and no reference to a crypto project other than $THREE. |diff --git a/docs/ops/guard-wiring.md b/docs/ops/guard-wiring.mdindex bf8b8225a..03c1ad655 100644--- a/docs/ops/guard-wiring.md+++ b/docs/ops/guard-wiring.md@@ -97,6 +97,7 @@ in both the registry and the runbook.| `audit:route-shadowing` | `GET /api/agents/vitals`, documented in `docs/agent-vitals.md` and announced in the changelog, resolved to `api/agents/[id].js` instead of its own handler | Explicit `vercel.json` rule above the `/api/agents/([^/]+)` catch-all || `check:doc-media` | 30 problems: `scene-studio` never captured, and 29 `usedBy` claims naming docs that embedded no figure at all | Captured `scene-studio`; embedded all 20 figures with their alt text and captions in the 27 docs that claimed them || `check:runnable-docs` | 8 documented curl samples no longer answered as documented | 7 declared their real contract (`<!-- runnable: 401 ... -->` for the two session-gated calls, `404`/`400` for the five illustrative ids and placeholders). The eighth is a deploy lag, below. |+| `check:windows-widget:live` | The same Windows widget contract against what three.ws is really serving: the deployed manifest, the worker bytes, the picker assets, and whether the deployed Adaptive Card expands in the board's engine | 1 | 4.1s | **manual (post-deploy).** Its 5 findings are one defect: production serves a card whose expressions the board's own engine refuses (`Invalid expression format`), so every pinned slot draws empty. The card in this tree expands cleanly, so the fix ships with the next deploy; re-run after it. |## Still unwired, with the reasondiff --git a/public/guards.json b/public/guards.jsonindex 60406fc4b..d65fbd6b0 100644--- a/public/guards.json+++ b/public/guards.json@@ -857,6 +857,58 @@"expect": "is declared but"}},+ {+ "id": "check-home-matrix",+ "script": "scripts/home-version-matrix.mjs",+ "npm": "check:home-matrix",+ "title": "The published Home Assistant support table is the one that was measured",+ "protects": "The version table in docs/smart-home.md is exactly what the last real matrix run wrote into docs/ops/home-version-matrix.json: the same releases, the same roles and install shares, and the same per-capability result for connect, registries, stream and call.",+ "why": "The home lane's correctness depends on a third party's monthly release, and the table is the only place we tell anyone which Home Assistant versions we support. The measurement is expensive (four containers, thirteen gigabytes, pulled and destroyed one at a time), so it is deliberately not run on every gate; what the gate can afford is proving that the cheap, published half still agrees with the expensive, measured half. Without that, the table decays into a claim: a run whose JSON landed but whose doc edit did not, or a doc edited by hand to say what someone hoped, both read as a supported version to every reader and to us.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "kind": "mutation",+ "summary": "The measured matrix says one thing and the published table another.",+ "violation": {+ "json": [+ {+ "file": "docs/ops/home-version-matrix.json",+ "pointer": "results.0.tag",+ "set": "1999.1"+ }+ ]+ },+ "expect": "is stale"+ }+ },+ {+ "id": "i18n-home",+ "script": "scripts/i18n-home-keys.mjs",+ "npm": "i18n:home",+ "title": "Every string the connected home speaks has a catalog key",+ "protects": "Each `t()` and `plural()` call site under the home lane resolves to a key in public/locales/en.json whose English source value is byte-identical to the fallback written in the code, and no source value smuggles a template expression into a translatable string.",+ "why": "The HTML extractor reads `data-i18n` annotations, which covers the lane's page shells and misses the house itself: the rooms, the devices, the refusals, the confirmation and every spoken announcement are assembled in JS from live data and carry no markup to annotate. A new string added there is simply English forever in all 84 locales, and nothing complains, because the fallback argument renders perfectly. Drift is the quieter half: edit the English in the code and the catalog keeps serving the old sentence to every translated locale, so the product says two different things depending on the reader's language. The template-expression refusal guards a worse outcome, a user's own room or device name baked into a source string and machine-translated on the next run.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "kind": "mutation",+ "summary": "The catalog's English keeps a sentence the code no longer says.",+ "violation": {+ "json": [+ {+ "file": "public/locales/en.json",+ "pointer": "home_scene.act_close",+ "set": "Shut"+ }+ ]+ },+ "expect": "drift:"+ }+ },{"id": "check-awesome","script": "scripts/build-awesome.mjs",diff --git a/scripts/lib/guard-proofs.mjs b/scripts/lib/guard-proofs.mjsindex 5f115a278..62bd4ac7f 100644--- a/scripts/lib/guard-proofs.mjs+++ b/scripts/lib/guard-proofs.mjs@@ -93,6 +93,17 @@ export function normalizeProof(guard) {if (kinds.length !== 1) {throw new Error(`guard "${guard.id}" json op needs exactly one of insert/set/removeWhere`);}+ // Pointers are dot paths (`results.0.tag`), not RFC 6901 slash pointers.+ // A slash pointer does not fail: `set` splits it on `.`, finds one segment,+ // and writes a junk top-level key named `/results/0/tag` that the guard+ // never reads. The proof then reports NOT CAUGHT and reads as a rotted+ // guard rather than as a typo in its own declaration.+ if (op.pointer.includes('/')) {+ throw new Error(+ `guard "${guard.id}" json op pointer "${op.pointer}" is a slash path; ` ++ `pointers are dot paths, so write "${op.pointer.replace(/^\/+/, '').replace(/\//g, '.')}"`,+ );+ }}if (!proof.expect || typeof proof.expect !== 'string') {throw new Error(`guard "${guard.id}" proof needs an expect fragment`);