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.

chore(prompts): retire work order 071, LOD chains and engine-ready QA

nirholasec76e4965e9c
diff --git a/prompts/finish/071-best3d-05-lod-and-engine-qa.md b/prompts/finish/071-best3d-05-lod-and-engine-qa.md
deleted file mode 100644
index 714e82157..000000000
--- a/prompts/finish/071-best3d-05-lod-and-engine-qa.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# best3d 05: LOD chains and engine-ready QA
-
-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)
-
-- Read CLAUDE.md first, then [_context/best3d-00-CONTEXT.md](_context/best3d-00-CONTEXT.md). CLAUDE.md overrides 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.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: irreversible spend, git push or deploy, external posting, committing content that names a crypto project other than $THREE, destroying unrecoverable data. Batch every such ask into ONE message at the end.
-- Commercial vendors are "Vendor A, B..." in every committed file. Open-source projects are named and credited.
-- Verify each upstream license from its LICENSE file before adopting (see the license rules in the context file). Reference-only means build our own, never copy code.
-- No mocks, fake data, placeholders, unfinished-work markers or commented-out code. The em-dash and en-dash characters are banned.
-- Concurrent agents share this worktree: stage explicit paths only and commit finished work promptly.
-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.
-
-## Why this matters
-
-Vendor D offers LOD; nobody ships draw-call, texel-density and collider QA. We already have gltf-transform 4.5 (`simplify`, `palette`, `instance` unused) and Simulation readiness (specs/SIM_READINESS.md).
-
-Source of the finding: [docs/research/3d-landscape-2026-10.md](../../docs/research/3d-landscape-2026-10.md).
-
-## Step 0: re-derive the current state
-
- sed -n 1,40p specs/SIM_READINESS.md; ls packages/glb-tools packages/glb-diff
-
-## Tasks
-
-1. `packages/glb-tools`: a `buildLodChain(glb, {levels})` using gltf-transform `simplify` that emits LOD0..N and writes `MSFT_lod` (and separate files for engines that want them).
-2. Engine QA report: draw calls, triangle budget per level, texel density, material count, collider suitability, with pass/fail thresholds in one config.
-3. Surface the report in Simulation readiness and Rig Doctor; add a watertight check and STL export for print.
-4. API: add `lods` to the export options. Docs, README, changelog.
-
-## Definition of done
-
-- [ ] A real GLB produces 3 LOD levels whose triangle counts decrease and the report renders in the UI.
-- [ ] Unit tests cover the chain builder and each QA check.
-- [ ] `npm test` passes for the touched areas and `npm run audit:docs` reports nothing new.
-- [ ] Docs, STRUCTURE.md row where a surface or directory landed, and a `data/changelog.json` entry (then `npm run build:pages`).
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing credential or env var | Follow the credential row of the CLAUDE.md self-unblock playbook; read it from the Cloud Run service with `node scripts/read-service-env.mjs`. |
-| GPU quota | File the increase, route to another region or class, continue. |
-| Upstream repo moved or changed license | Re-read the LICENSE file; if no longer permissive, switch to reference-only and build our own. |
-| Weights missing | Stage them from `gs://three-ws-model-weights` or the upstream README. |
-
-## 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 (`type(scope): what changed and why a reader cares`).
-3. If every line passes, delete this file in that commit (`git rm prompts/finish/071-best3d-05-lod-and-engine-qa.md`) and append a dated entry to [_context/best3d-PROGRESS.md](_context/best3d-PROGRESS.md) with the commit SHAs. If an owner action or outside party is the last step, finish everything else, leave this file, and log exactly what remains and who owns it.
-4. Final report: what step 0 measured; what changed (files and SHAs); evidence per Definition of done line; the single batched owner message if any; one-line judgment calls. No trailing questions.
diff --git a/prompts/finish/_context/best3d-PROGRESS.md b/prompts/finish/_context/best3d-PROGRESS.md
index fd62fe5bb..1d77f8680 100644
--- a/prompts/finish/_context/best3d-PROGRESS.md
+++ b/prompts/finish/_context/best3d-PROGRESS.md
@@ -26,3 +26,9 @@ Append a dated entry per closed order, with commit SHAs.
- Passing: `tests/api/forge-partcrafter.test.js` + `tests/api/forge-holopart.test.js` + `tests/forge-options.test.js` together (46/46, including the `editable_parts` catalog-surfacing regression this caught and a `summarizeForgeOptions`/`num_parts` test-coverage regression fixed along the way); `python3 -m py_compile` clean on every new `.py` file in both workers (no local GPU/torch, matching the documented "local tests" step in each worker's README; the full contract test runs at Docker build time); `node scripts/check-vendored-workers.mjs` OK (41 copies across 44 workers, every gltf_meshopt.py vendor now stages gltfpack); `npm run check:rules` exit 0 on every touched file; `npm run audit:docs` 15 findings, same pre-existing set, none naming partcrafter, holopart or this order; a full `npx vitest run` shows 39 failed files / 73 failed tests out of 2372 files / 35322 tests, matching the established pre-existing concurrent-agent drift pattern from orders 067-069 (none of the failing files touch forge, restyle, partcrafter or holopart). DoD line 1 (3+ named parts, scoped retexture) verified in a real browser via Playwright against a synthetic 3-part GLB fixture built with `GLTFExporter.parse([...], ...)` to match the genuinely-top-level-node shape `workers/segment/segment_core.py`'s `build_scene()` produces in production; zero console errors, correctly scoped history label.
- Still open, owner (rows 43 and 44 of `_context/production-100-OWNER-ACTIONS.md`): (1) `bash workers/model-partcrafter/stage-assets.sh`, `gcloud builds submit --config workers/model-partcrafter/cloudbuild.yaml --substitutions=SHORT_SHA=manual$(date +%s) .`, `gcloud run services update three-ws-api --region us-central1 --update-env-vars MODEL_PARTCRAFTER_URL=<service-url>`; (2) the same three-step sequence for `workers/model-holopart/` with `MODEL_HOLOPART_URL`; (3) run one real image through PartCrafter and one real part-segmented mesh through HoloPart, confirm DoD line 1 against live output (not just the synthetic fixture), then delete the order file.
- Commits: `d3edf5a25` (both workers + the gltfpack Dockerfile fix + the vendored-workers check), `9b1f6ae9b` (Forge API/provider wiring), `eecca6527` (Restyle Studio Parts panel), `a287682e1` (tests), `ac0c35112` (docs, STRUCTURE.md, changelog).
+- 2026-10-12: order 071 (LOD chains and engine-ready QA) built, verified end to end, and CLOSED, no owner-gated step remained. Task 1 (`buildLodChain` in `packages/glb-tools`, `MSFT_lod`), Task 2 (`gradeEngineQa`: draw calls, material count, texel density, per-level triangle budget, collider suitability, all thresholds in one isomorphic core `api/_lib/engine-qa-core.js`) and the `<engine-qa>` panel wiring into both `public/viewer.html` and Rig Doctor (zero-network browser-only partial grade via `src/engine-qa-client.js`, full grade + LOD-chain upgrade via the server endpoint) were built in earlier commits this same campaign (`8408b655a`, `891c0801e`, `360fec461`, `0d434d038`, `62ea70a17`, `2599cd4ae`, `ea0de3502`). This pass closed Task 4: `lods` added as an opt-in boolean to `api/_lib/forge-options.js`, `buildLodVariant()` added to `api/_lib/forge-store.js` (fire-and-forget third stored object, same pattern as the existing web-delivery variant), wired through all 8 `materializeCreation` call sites in `api/forge.js`, migration `20261015020000_forge_lod_variant.sql` (`lod_glb_key`, `lod_glb_url`, `lod_levels`) applied via `node scripts/apply-migrations.mjs --apply --file 20261015020000_forge_lod_variant.sql`. Wrote `docs/engine-qa.md`, the LOD-variant subsection of `docs/forge-pipeline.md`, a STRUCTURE.md row, a `data/pages.json` entry and a `data/changelog.json` entry, then `npm run build:pages`.
+ - DoD line 1 (3 LOD levels, decreasing triangle counts, report renders in the UI): verified against the real bundled fixture in `tests/forge-store-materialize.test.js`'s `buildLodVariant` tests (strictly-decreasing triangle counts asserted directly), and against a real production GLB (`https://three.ws/avatars/michelle.glb`) through a real Playwright browser session hitting the real `/api/3d/engine-qa` endpoint: graded badge rendered ("Will stutter"), full report panel showed draw calls/materials/textures/texel density/collider fitness, zero console errors from shipped code.
+ - DoD line 2 (unit tests for the chain builder and each QA check): `packages/glb-tools/test/lod.test.js`, `tests/engine-qa-core.test.js`, `tests/engine-qa.test.js`, `tests/engine-qa-client.test.js` (all from earlier commits this campaign), plus this pass's `tests/forge-options.test.js` (`lods` option) and `tests/forge-store-materialize.test.js` (`buildLodVariant`). `npx vitest run` on the full touched set: 6 files, 68/68 passed.
+ - DoD line 3 (`npm test` passes for touched areas, `npm run audit:docs` reports nothing new): full `npm test` shows 38 failed files / 72 failed tests out of 2376 files / 35362 tests; every failure traces to files this order never touched (`tests/api/oauth-introspect.test.js`, `tests/api/ops-mcp-clients.test.js`, `tests/api/v1-rest-router.test.js` and others), matching the established pre-existing concurrent-agent-drift pattern logged for orders 067-070 above. `npm run audit:docs`: 15 findings, same pre-existing set (other agents' unpublished docs and broken relative links in unrelated packages), none naming engine-qa, lod, or this order.
+ - `npm run check:rules` exit 0 on every touched file, across all three commits.
+ - Commits: `10983f315` (lods option, forge-store wiring, migration, tests), `73e9f988b` (docs/engine-qa.md, forge-pipeline.md section, STRUCTURE.md row, pages.json/changelog.json entries, rebuilt artifacts).