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 motion ratchet so npm run gate reaches the checks behind it
nirholas9a33346b3aaa
diff --git a/data/guards.json b/data/guards.jsonindex 1b0e32b4b..e334c1585 100644--- a/data/guards.json+++ b/data/guards.json@@ -579,6 +579,27 @@"expect": "interactive-state gaps increased"}},+ {+ "id": "audit-motion-drift",+ "script": "scripts/audit-motion-drift.mjs",+ "npm": "audit:motion-tokens",+ "title": "Motion ratchet",+ "protects": "A transition cannot spell its duration or easing as a literal past a committed baseline.",+ "why": "public/tokens.css names four durations and three easings and collapses the durations to 0ms under prefers-reduced-motion, and none of that reaches a transition written as `150ms ease`. The platform was saying the same thing 41 different ways, which nobody notices on one control and everybody feels as the site not behaving like one product. Counting literals against a baseline and failing only when the count rises makes the debt strictly decreasing, the same contract as the design-token and interactive-state ratchets beside it. @keyframes and `animation` are deliberately out of scope: their durations are intrinsic to the effect, not a control response.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "summary": "A stylesheet whose transition states its duration and easing as literals instead of tokens.",+ "violation": {+ "write": {+ "public/guard-proof-motion.css": ".proof-motion { transition: opacity 137ms ease, transform 240ms ease-in-out; }\n"+ }+ },+ "expect": "motion drift increased"+ }+ },{"id": "check-browser-graph","script": "scripts/check-browser-graph.mjs",diff --git a/docs/guards.md b/docs/guards.mdindex 69846c7a5..e66254899 100644--- a/docs/guards.md+++ b/docs/guards.md@@ -97,6 +97,7 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| One `<model-viewer>` build | `npm run check:model-viewer` | Every `<model-viewer>` reference in tracked source names one version, no version is served under two integrity hashes, and the vendored copy matches. || Design-token ratchet | `npm run audit:tokens` | Hardcoded colour hexes cannot creep back past a committed baseline. || Interactive-state ratchet | `npm run audit:states` | A selector that declares cursor:pointer cannot ship without a hover rule behind it. |+| Motion ratchet | `npm run audit:motion-tokens` | A transition cannot spell its duration or easing as a literal past a committed baseline. || Credential material | `npm run check:secrets` | No dotenv file, private key, keystore, or downloaded cloud credential becomes a tracked file, and no added line carries a provider-issued key. || Python worker dependencies | `npm run audit:deps` | No pinned Python dependency in `workers/`, `services/` or `packages/` carries a known vulnerability in the OSV database. Needs network, so it runs on demand rather than in the gate. || iOS app icon | `npm run check:ios-icons` | The committed iOS icon and launch images are exactly what the current brand mark produces, and the icon carries no alpha channel. |diff --git a/public/guards.json b/public/guards.jsonindex 1b0e32b4b..e334c1585 100644--- a/public/guards.json+++ b/public/guards.json@@ -579,6 +579,27 @@"expect": "interactive-state gaps increased"}},+ {+ "id": "audit-motion-drift",+ "script": "scripts/audit-motion-drift.mjs",+ "npm": "audit:motion-tokens",+ "title": "Motion ratchet",+ "protects": "A transition cannot spell its duration or easing as a literal past a committed baseline.",+ "why": "public/tokens.css names four durations and three easings and collapses the durations to 0ms under prefers-reduced-motion, and none of that reaches a transition written as `150ms ease`. The platform was saying the same thing 41 different ways, which nobody notices on one control and everybody feels as the site not behaving like one product. Counting literals against a baseline and failing only when the count rises makes the debt strictly decreasing, the same contract as the design-token and interactive-state ratchets beside it. @keyframes and `animation` are deliberately out of scope: their durations are intrinsic to the effect, not a control response.",+ "stages": [+ "gate"+ ],+ "needs": "none",+ "proof": {+ "summary": "A stylesheet whose transition states its duration and easing as literals instead of tokens.",+ "violation": {+ "write": {+ "public/guard-proof-motion.css": ".proof-motion { transition: opacity 137ms ease, transform 240ms ease-in-out; }\n"+ }+ },+ "expect": "motion drift increased"+ }+ },{"id": "check-browser-graph","script": "scripts/check-browser-graph.mjs",