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
test(flake): make the walk sky and irl console assertions independent of when they run
nirholas1a6c536c022b
diff --git a/prompts/swarm-100/sweep-tests.md b/prompts/swarm-100/sweep-tests.mddeleted file mode 100644index 16d7b63c7..000000000--- a/prompts/swarm-100/sweep-tests.md+++ /dev/null@@ -1,86 +0,0 @@-# Sweep: Full test suite green--How to run: paste this file's repo path into a fresh Claude Code chat in this-repository and say "run this work order". This file is fully self-contained:-it depends on no other prompt file anywhere. If neighboring files in-prompts/swarm-100/ are gone, that work is done; if present, ignore them.-Every claim below rots; step 0 re-measures, and what you measure wins.--## Operating clause (binding)--- Read CLAUDE.md first. Its rules override everything, including this file.-- Finish 100% in this session. Never end the turn with a question, an option- list, or an unexecuted plan. A judgment call goes in one line of the final- report; it never becomes a question that halts work.-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real- funds or any irreversible on-chain write, git push or a production deploy,- committing content that references a crypto project other than $THREE, and- destroying unrecoverable data.-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no- commented-out code. Real APIs and real integrations only.-- The em-dash and en-dash characters are banned in everything you write.-- Concurrent agents share this worktree: stage explicit paths only (never a- bare add-everything), and commit finished work promptly.-- Before committing, run: npm run check:rules -- --paths <files you touched>.- It must exit 0.--## Step 0: re-derive the current state--Run the sweep's own command first and work from its output, not from any-memory of what used to fail:-- npm test--Capture the full output to the session scratchpad; do not work from an-excerpt.--## Task--Run the full suite (vitest then Playwright; the Playwright stage is gated on vitest passing). Fix every failure at its root: the code under test when the code is wrong, the test when the test asserts stale behavior. Never pipe through tail, never skip or quarantine a test to get to green.--Fix everything found in this sweep's scope. Findings that belong to a-different surface entirely (and would take this session off its one task) go-in the report as named follow-ups instead; everything in scope gets fixed-here, at root, with no masking.--## Definition of done--- [ ] The command above exits 0 (or, for measurement-style sweeps, the report- carries the measured numbers and every committed fix).-- [ ] Every fix is a root-cause fix; no check was weakened, skipped, or- quarantined to get to green.-- [ ] npm run check:rules -- --paths <touched files> exits 0; npm test passes- if code changed.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |-| Playwright browser missing | npx playwright install chromium |-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |--## Close out (required)--1. Verify every Definition of done line with the actual command output in- front of you. Never claim a line you did not verify.-2. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares).-3. Delete this prompt file in that same commit:-- git rm prompts/swarm-100/sweep-tests.md-- The shrinking directory is this campaign's only progress ledger; there is- no progress log to update.-4. Final report: what step 0 measured, what changed (file list), evidence per- Definition of done line, and any one-line judgment calls. No trailing- questions, no unexecuted plans.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns-it. Never delete this file on a partial.diff --git a/tests/branding-allowlist.json b/tests/branding-allowlist.jsonindex 51075329b..ec4960112 100644--- a/tests/branding-allowlist.json+++ b/tests/branding-allowlist.json@@ -414,6 +414,11 @@"file": "docs/avatar-pipeline.md","reason": "Factual list of third-party rig-name conventions glb-canonicalize.js recognizes (Mixamo, Avaturn, Unreal, VRM, Daz, MakeHuman, ...) \u2014 interoperability documentation, not brand promotion."},+ {+ "pattern": "Mixamo, Avaturn, Unreal",+ "file": "docs/api-reference.md",+ "reason": "Same factual rig-name list as the docs/avatar-pipeline.md entry above, in the /api/render/avatar-clip reference: it tells an API caller which third-party skeletons a posePresetId retargets onto. Interoperability reference a caller needs to predict the response, not brand promotion."+ },{"pattern": "avaturn_seed","file": "docs/ops/runtime-flags.md",diff --git a/tests/e2e/irl-discovery.spec.js b/tests/e2e/irl-discovery.spec.jsindex 8f7cc0d00..ddb35d219 100644--- a/tests/e2e/irl-discovery.spec.js+++ b/tests/e2e/irl-discovery.spec.js@@ -100,6 +100,14 @@ function trackConsoleErrors(page) {if (m.type() !== 'error') return;const t = m.text();if (/websocket|hmr|wss:|vite|favicon|net::ERR/i.test(t)) return;+ // "504 (Outdated Optimize Dep)" is the dev server invalidating a prebundled+ // chunk that was already in flight, which happens whenever a later page in+ // the run makes Vite discover a new dependency and re-optimize. The browser+ // refetches and the page loads; only the console line survives. It cannot+ // occur in production (no dep optimizer there, the bundles are prebuilt),+ // and the message carries no "vite" token for the filter above to catch.+ // Matched on that exact marker, so a real 504 from our own API still fails.+ if (/Outdated Optimize Dep/i.test(t)) return;// A 401 resource line from a signed-out auth/session probe is the browser// echoing an EXPECTED response (dev /api proxies to prod; no session in a// fresh context). Only this spec's own /api/irl/* surface stays fatal.diff --git a/tests/e2e/irl-pin-idle.spec.js b/tests/e2e/irl-pin-idle.spec.jsindex 482987d1f..16840e59c 100644--- a/tests/e2e/irl-pin-idle.spec.js+++ b/tests/e2e/irl-pin-idle.spec.js@@ -76,6 +76,9 @@ function trackConsoleErrors(page) {if (m.type() !== 'error') return;const t = m.text();if (/websocket|hmr|wss:|vite|favicon|net::ERR/i.test(t)) return;+ // Dev-server dep-optimizer invalidation, not a product error. Same reason+ // as the matching filter in irl-discovery.spec.js.+ if (/Outdated Optimize Dep/i.test(t)) return;if (/status of 401/i.test(t) && !/\/api\/irl\//i.test(m.location()?.url || '')) return;errors.push(t);});diff --git a/tests/walk-day-night.test.js b/tests/walk-day-night.test.jsindex ccfe57f78..1bfaca6c9 100644--- a/tests/walk-day-night.test.js+++ b/tests/walk-day-night.test.js@@ -61,9 +61,21 @@ describe('walk day/night cycle', () => {expect(rig.stageEl.style.background).toContain('radial-gradient');});+ // These two assert an exact sky string, so they force the write. The sky+ // paint is throttled (walk-day-night.js): update() only repaints once skyMix+ // has moved more than 0.005 since the last paint, and setEnvironment() seeds+ // that mark from the REAL clock, because it snaps the rig to the actual time+ // of day. A test that then jumps to an authored time can land inside that+ // epsilon of whatever time it really is, so the sky painted during setup+ // survives the jump and the assertion reads a near-miss blend+ // (`#050610 ... #1a233c` instead of night). Measured against the 480s world+ // cycle that is a 3160ms window for midnight and 1760ms for noon: 1.03% of+ // runs, which is exactly the kind of flake nobody can reproduce on demand.+ // Forcing pins the time-to-sky mapping these tests are actually about; the+ // throttle itself stays covered by the dusk sweep and the determinism case.it('renders the authored daytime anchors at noon', () => {rig.cycle.setEnvironment(OUTDOOR);- const day = rig.cycle.update(NOON);+ const day = rig.cycle.update(NOON, true);expect(day).toBeCloseTo(1, 5);expect(rig.sun.intensity).toBeCloseTo(1.7, 5);expect(rig.hemi.intensity).toBeCloseTo(0.75, 5);@@ -77,7 +89,7 @@ describe('walk day/night cycle', () => {it('drops to the cool low-light floor at midnight, never black', () => {rig.cycle.setEnvironment(OUTDOOR);- const day = rig.cycle.update(MIDNIGHT);+ const day = rig.cycle.update(MIDNIGHT, true);expect(day).toBeCloseTo(0, 5);expect(rig.sun.intensity).toBeCloseTo(0.07, 5);expect(rig.hemi.intensity).toBeCloseTo(0.12, 5);