Skip to content

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.

docs(best3d): log order 069 close-out, add owner-deploy status note

nirholasd9283de7288a
diff --git a/prompts/finish/069-best3d-03-rig-anything.md b/prompts/finish/069-best3d-03-rig-anything.md
index 765c56c72..456193718 100644
--- a/prompts/finish/069-best3d-03-rig-anything.md
+++ b/prompts/finish/069-best3d-03-rig-anything.md
@@ -1,5 +1,15 @@
# best3d 03: Rig non-humanoids: SkinTokens, UniRig and AniGen
+## Evolve status (2026-10-11)
+
+Built, tested and committed; NOT closed. Two Definition of done lines need an owner GPU deploy that this session cannot run (gate 2, deploy). What remains and who owns it:
+
+1. Deploy `workers/rig-nonhuman` and set `RIG_NONHUMAN_URL` wherever `workers/rig`'s classifier reads it from: exact commands in row 40 of [`_context/production-100-OWNER-ACTIONS.md`](_context/production-100-OWNER-ACTIONS.md).
+2. Deploy `workers/model-anigen` and set `MODEL_ANIGEN_URL` on `three-ws-api`: exact commands in row 41 of the same file.
+3. Once both are live, run one real quadruped GLB through each lane, confirm it plays a clip in the viewer, then delete this order file and log the result in [`_context/best3d-PROGRESS.md`](_context/best3d-PROGRESS.md).
+
+Everything else in the Definition of done is verified in this session; see the progress log for command output.
+
How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate.
## Operating clause (binding)
diff --git a/prompts/finish/_context/best3d-PROGRESS.md b/prompts/finish/_context/best3d-PROGRESS.md
index c636126c7..01327eb74 100644
--- a/prompts/finish/_context/best3d-PROGRESS.md
+++ b/prompts/finish/_context/best3d-PROGRESS.md
@@ -16,3 +16,7 @@ Append a dated entry per closed order, with commit SHAs.
- 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.
+- 2026-10-11: order 069 (non-humanoid rigging: SkinTokens, UniRig, AniGen) built and committed, NOT closed. Step 0 confirmed `VAST-AI-Research/SkinTokens`, `VAST-AI-Research/UniRig` and `VAST-AI-Research/AniGen` all MIT, all pushed within the prior month. Task 1: a `mesh_classify.py` heuristic in `workers/rig` now routes non-humanoid meshes to a new `workers/rig-nonhuman` worker (UniRig skeleton prediction, SkinTokens skinning) behind `RIG_NONHUMAN_URL`, keeping Make-It-Animatable as the humanoid path. Task 2: AniGen shipped as a first-class Forge backend (`workers/model-anigen`), wired through `api/_lib/forge-tiers.js` (`BACKENDS.anigen`, `rigged: true`), `api/_providers/gcp.js` (mode dispatch, `result.rigged`/`result.jointCount`), `api/forge.js`/`api/gpt-forge.js`, and `src/forge.js` ("Rig on generate" engine label plus a rigged badge); opt-in only, never a default or failover target. Task 3: `src/glb-canonicalize.js` needed no change, its own null-safe lookup already returns the original ArrayBuffer by reference for a rig with zero canonical joints, so a non-humanoid GLB round-trips untouched and falls back per the existing `supportsCanonicalClips()` gate; covered with a new test describing an opaque-named quadruped rig in `tests/glb-canonicalize.test.js`. Task 4: Rig Doctor (`src/rig-report.js`) gained a dependency-light glTF VEC4 accessor reader (all 6 componentTypes, KHR-normalized integers, interleaved `byteStride`, multi-set `JOINTS_n`/`WEIGHTS_n`) feeding `maxInfluences`/`unweightedVertices`/`skinnedVertices` into the report and a new skin-weight-health note in the non-humanoid verdict branch, surfaced as a stat row in `src/rig-doctor-page.js` and documented in `docs/rig-doctor.md`. Task 5: `STRUCTURE.md` fleet row, two `data/changelog.json` entries (AniGen, rig-nonhuman) plus a third for the Rig Doctor stat, `npm run build:pages` after each.
+ - Passing: `tests/glb-canonicalize.test.js` + `tests/rig-report.test.js` together (685/685, including the new non-humanoid cases); `tests/api/forge-anigen.test.js` + `tests/api/forge-anigen-request.test.js` + `tests/api/forge-tiers.test.js` (37/37); `pytest -q` in `workers/rig/` (23 passed, humanoid path unchanged), `workers/rig-nonhuman/` (7 passed) and `workers/model-anigen/` (4 passed); `npm run check:vendored` (OK, 37 copies across 42 workers); `npm run audit:docs` (15 findings, same pre-existing set, none naming rig-nonhuman, anigen or this order); `npm run check:rules` exit 0 on every touched file. A full `npx vitest run` shows 38 failed files / 72 failed tests out of 2370 files / 35298 tests; every failure checked traces to files this order never touched (`tests/api/ops-mcp-clients.test.js`, `tests/api/v1-rest-router.test.js` and others, pre-existing concurrent-agent drift unrelated to rigging or Forge), matching the established pattern from orders 067/068 above.
+ - Still open, owner (rows 40 and 41 of `_context/production-100-OWNER-ACTIONS.md`): (1) `gcloud builds submit --config workers/rig-nonhuman/cloudbuild.yaml` and set `RIG_NONHUMAN_URL`; (2) `gcloud builds submit --config workers/model-anigen/cloudbuild.yaml` and set `MODEL_ANIGEN_URL` on `three-ws-api`; (3) once both are live, run one real quadruped GLB through each lane, confirm it plays a clip in the viewer, then delete the order file.
+ - Commits: `ac2eca062` (non-humanoid rig worker + dispatch), `ba76f8173` (AniGen worker), `7f2646b67` (AniGen Forge wiring), `af041fb9d` (docs: STRUCTURE.md + changelog for both), `fe5c55f0c` (test: glb-canonicalize non-humanoid coverage), `a7906b7c9` (feat: Rig Doctor skin-weight report), `aa3b812da` (docs: changelog for the Rig Doctor stat), `f10073da8` (docs: owner-action rows 40/41).