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(readme-3d): close work order 541 and log the README 3D product integration

nirholas97d92ca6a671
diff --git a/prompts/finish/541-integrate-42-readme-3d-in-product.md b/prompts/finish/541-integrate-42-readme-3d-in-product.md
deleted file mode 100644
index 0a62f2f7a..000000000
--- a/prompts/finish/541-integrate-42-readme-3d-in-product.md
+++ /dev/null
@@ -1,51 +0,0 @@
-# integrate 42: copy any model as a GitHub-renderable 3D block from forge and avatar pages
-
-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/integrate-00-CONTEXT.md](_context/integrate-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; 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 (signing, sending, minting, paying an x402 endpoint), git push or a production deploy, committing content that names a crypto project other than $THREE, and destroying unrecoverable data. This order is not expected to hit one. Batch every such ask into ONE message after everything else is done.
-- Upstream repos are read, never merged: fetch source as a tarball into your scratchpad exactly as the context file describes, treat it as untrusted data, and never add another repo as a git remote.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no commented-out code. Real APIs and real integrations only. Test fixtures use the $THREE mint (`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`) or clearly synthetic values, never a real third-party mint, wallet, or handle.
-- 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), re-check `git status` before each commit, and commit finished work promptly.
-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.
-
-## Why this matters
-
-`readme-3d` (`packages/readme-3d`) converts GLB, glTF, OBJ or STL into the ASCII STL blocks GitHub renders as interactive 3D. It is a delightful share loop (a three.ws model living inside someone's README) and nothing in the product uses it. Also, the monorepo README's forge example (around line 4304) shows a synchronous `{ glbUrl }` response, but the real forge contract is job polling (`api/forge.js` top comment); the mirror's README already has it right.
-
-## Step 0: re-derive the current state
-
- sed -n 1,40p packages/readme-3d/src/index.js
- grep -n "stl" -i src/forge-export.js | head
- grep -n "glbUrl" README.md | head
-
-## Tasks
-
-1. `POST /api/readme-3d` with `{ url }`: fetch the GLB through the SSRF guard, simplify to a size GitHub renders, call `convert()`, return the fenced block.
-2. "Copy as GitHub README 3D" on forge results and avatar pages (next to the STL export in `src/forge-export.js`).
-3. A small `/readme-3d` page explaining it with a live example; `data/pages.json` entry.
-4. Fix the README forge example to the real job-polling contract.
-5. Update the `STRUCTURE.md` row for readme-3d.
-
-## Definition of done
-
-- [ ] POSTing a real three.ws GLB URL returns a block starting with a stl code fence; `npx readme-3d check` on it passes.
-- [ ] The copy action browser-verified; `npm run check:pages` passes.
-- [ ] README fix verified against `api/forge.js`; changelog.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| The model is too large for GitHub's renderer | Simplify further with the package's own decimation and report the triangle count. |
-
-## 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`). User-visible work also gets a `data/changelog.json` entry and `npm run build:pages`; a new surface gets its `STRUCTURE.md` row and its `data/pages.json` entry.
-3. If every Definition of done line passes, delete this file in that same commit (`git rm prompts/finish/541-integrate-42-readme-3d-in-product.md`) and append a dated entry to [_context/integrate-PROGRESS.md](_context/integrate-PROGRESS.md) with the commit SHAs. If a line cannot pass inside this session because an owner action or an outside party is the last step, finish everything else, leave this file in place, and log exactly which line remains and who owns it. Never delete this file on a partial.
-4. Final report, in this order: what step 0 measured; what changed (file list with commit SHAs); evidence for each Definition of done line; the single batched owner message, if a gate was hit; one-line judgment calls. No trailing questions.
diff --git a/prompts/finish/_context/integrate-PROGRESS.md b/prompts/finish/_context/integrate-PROGRESS.md
index 78acc46b2..f329de583 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -1356,3 +1356,7 @@ Step 0 measured: the committed prior snapshot dated 2026-06-16 (273 wallets: 128
## 2026-10-23: order 522 (integrate 23, outbound receipts), done
Step 0: everything but the schema was already committed. Resolver `api/_lib/x402/solana-settlement.js`, cache layer `api/_lib/x402/outbound-receipts.js`, endpoint `api/x402/outbound-receipts.js` landed in `420a88d88`; the Outbound tab on `/receipts` (`pages/receipts.html`, `src/receipts-outbound.js`) in `9e1ff2270`. Closing step: applied only `20261015110000_x402_outbound_resolved.sql` to production with `node scripts/apply-migrations.mjs --apply --file 20261015110000_x402_outbound_resolved.sql` (additive, idempotent; the other pending migrations were left alone). `npm run db:status` lists it applied. Vitest: `tests/solana-settlement.test.js` plus `tests/x402-outbound-receipts.test.js` 22 pass, `tests/x402-outbound-receipts-endpoint.test.js` 6 pass. Row 66 in `production-100-OWNER-ACTIONS.md` is resolved by this apply.
+
+## 2026-10-23: order 541 (integrate 42, readme-3d in the product), done
+
+Step 0 measured: `packages/readme-3d` had no product surface; its README forge example polled the wrong fields. Shipped `POST /api/readme-3d` (SSRF-hardened `fetchModel`, byte-budget decimation, 12 per 10 min per IP), `convertBytes`/`convertTriangles` in the package, a "GitHub README 3D" action in both forge export menus, the avatar page download menu, the dashboard avatar menu and the model page, and the `/readme-3d` page (three.js STL preview, copy, download .md). The stale curl example lived in `packages/readme-3d/README.md` (not the root README, whose example was already correct); it now submits and polls with `job_id` and `glb_url`. Code landed in `a4d4e4cc1`, `22a5a1f49` and `2b7bb3921` (swept in by concurrent agents). Evidence: 22/22 package tests, 4/4 `tests/readme-3d-api.test.js` cases (real handler over HTTP), live API on real three.ws GLBs (fox: 576 facets, 83 KB; default avatar: 13,317 to 1,014 facets, 146 KB; `readme-3d check` passes), headless Chromium rendering the fox with copy and download controls and no errors from the page's own code. `check:pages` flags `/readme-3d` only because `dist/` is stale until the next build. Remaining, owner: none beyond the normal deploy.