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(best3d): re-verify order 068, nothing drifted since the pixal3d close-out
nirholas14602f692bd1
diff --git a/prompts/finish/_context/best3d-PROGRESS.md b/prompts/finish/_context/best3d-PROGRESS.mdindex 7a86edd14..c636126c7 100644--- a/prompts/finish/_context/best3d-PROGRESS.md+++ b/prompts/finish/_context/best3d-PROGRESS.md@@ -15,3 +15,4 @@ Append a dated entry per closed order, with commit SHAs.- Passing: 52/52 on the touched test files (`tests/forge-options.test.js`, `tests/forge-view-slots.test.js`, `tests/api/forge-pixal3d.test.js`, `tests/api/forge-pixal3d-request.test.js`, `tests/api/forge-multiview-photo.test.js`); the broader `tests/api/forge-*.test.js` + `tests/forge-*.test.js` run shows 996 passed, 3 pre-existing failures in files outside this diff (`forge-director-rewrite.test.js`, `forge-director.test.js`) unrelated to pixal3d/view-slots, not caused by this change; worker suite 81 passed, 1 skipped (`pytest -q` in `workers/model-pixal3d/`); `npm run check:vendored` OK (33 copies across 40 workers); `npm run audit:docs` 15 findings, same pre-existing set, none naming pixal3d or this order; `npm run check:rules` exit 0 on every touched file. Verified in a real browser (Playwright against a synthetic catalog entry, since the worker isn't deployed): the engine button renders, the panel toggles, slots 4/5 disable/re-enable correctly, and the views counter denominator tracks the per-engine cap.- Still open, owner (row 39 of `_context/production-100-OWNER-ACTIONS.md`): (1) `workers/model-pixal3d/stage_weights.sh`, (2) `gcloud builds submit --config workers/model-pixal3d/cloudbuild.yaml --region us-central1 --project aerial-vehicle-466722-p5 --substitutions=SHORT_SHA=manual$(date +%s) .`, (3) `gcloud run services update three-ws-api --region us-central1 --update-env-vars MODEL_PIXAL3D_URL=<service-url>`, (4) run one real 3-image generation, confirm the `forge_creations` row records all three input URLs and the GLB validates, then delete the order file.- Commits: `5b4f31d05` (backend + worker + tests), `d85ce1936` (frontend UI), `192c01233` (docs + changelog).+- 2026-10-11 (re-verification pass): re-ran order 068 end to end, nothing drifted and no code changed. Confirmed fresh: worker suite (`pytest -q` in `workers/model-pixal3d/`, 81 passed, 1 skipped); the five touched test files (52/52); the broader `tests/api/forge-*.test.js` + `tests/forge-*.test.js` run (998 passed, 2 failed, both pre-existing in `tests/api/forge-director.test.js` and `tests/api/forge-director-rewrite.test.js`, introduced by unrelated commit `41e8e201a` and verified to touch neither `pixal3d` nor view-slot code); `npm run check:vendored` (OK, 33 copies across 40 workers); `npm run audit:docs` (15 findings, same pre-existing set, none naming pixal3d or this order); `npm run check:rules` exit 0 on every touched file. `data/changelog.json` and the STRUCTURE.md fleet row are both still present from commit `192c01233`. `gcloud run services describe model-pixal3d --region us-central1` still answers "Cannot find service" and `node scripts/read-service-env.mjs` still shows no `MODEL_PIXAL3D_URL` on `three-ws-api`, confirming row 39 of `_context/production-100-OWNER-ACTIONS.md` is still accurate and the order's "Evolve status" paragraph needs no edit. The remaining step stays the owner's GPU deploy; no code or doc changes this pass beyond this log entry.