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
chore(partners): log order 093's owner-gated remainder, keep the order open
nirholas520dfeb76a37
diff --git a/prompts/finish/093-partners-10-agent-tool-packages.md b/prompts/finish/093-partners-10-agent-tool-packages.mdindex 9f46335eb..20590529a 100644--- a/prompts/finish/093-partners-10-agent-tool-packages.md+++ b/prompts/finish/093-partners-10-agent-tool-packages.md@@ -1,5 +1,20 @@# partners 10: Tool packages and registry entries for the agent frameworks+**Evolve status (2026-10-13):** Every buildable and testable line is done. `packages/ai-sdk/`+and `packages/langchain/` are complete, real-API-tested (5/5 passing in each, live calls+against production) and `npm pack --dry-run` clean. `examples/google-adk/` connects an ADK+agent to the free MCP server and was verified live (`node index.mjs --check` runs a real+`rig_mesh` call against production). The skills index (`/.well-known/skills/index.json`) and+the new deterministic Postman collection (`/.well-known/postman-collection.json`, generated by+`scripts/build-postman-collection.mjs`, checked via `npm run check:postman-collection`) both+validate. OpenRouter attribution is wired on all 19 real OpenRouter-calling files. The six+registry submission files exist in `marketing/growth/submissions/agent-registries/`. The only+remaining steps are owner-gated third-party actions (CLAUDE.md gate 2: publish, and contact a+third party): publishing `@three-ws/ai-sdk` and `@three-ws/langchain` to npm, opening the+LangChain integration issue, and submitting the six registry entries. Logged as row 56 in+[production-100-OWNER-ACTIONS.md](_context/production-100-OWNER-ACTIONS.md). This file stays+in place until those publishes and submissions land.+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/partners-PROGRESS.md b/prompts/finish/_context/partners-PROGRESS.mdindex 91cfc1c6c..e9684ab39 100644--- a/prompts/finish/_context/partners-PROGRESS.md+++ b/prompts/finish/_context/partners-PROGRESS.md@@ -526,3 +526,72 @@ rendered, a disallowed action actually blocked). Logged as row 55 instays in place (not deleted) until that registration, env update, migration, and liveverification land. Commits: `05fdde784` (feature, docs, changelog, tests, owner-actions row),this entry's commit (re-verification log only, no code changes).++## 2026-10-13: order 093 built and verified end to end; npm publish and three registry/issue submissions remain, order file stays open++Order 093 asked for the agent-framework tool packages and registry entries the prospects list+depends on. Step 0 found `packages/ai-sdk/` and `packages/langchain/` already shipped in an+earlier segment of this same session (`e388d1458`), the ten published Agent Skills already+em-dash-clean (`a9925cd4a`), and the skills index already live (`0871315f4`); this session's+work closed the remaining gaps: a Google ADK sample, the Postman collection, and the docs/+STRUCTURE.md wiring those needed.++- **AI SDK and LangChain packages (tasks 1, 2)**: re-verified rather than re-built. Both+ packages' `npm test` (Node's own `node --test`) run live against production: ai-sdk 5/5+ passing (render, agentChat, forge, rig, animate, including a real x402 `PaymentRequired`+ challenge on the paid animate tool); langchain the same 5 tools under their `three_ws_*`+ names, 5/5 passing. `npm pack --dry-run` is clean for both (5 files each, LICENSE ++ README + package.json + src/client.js + src/index.js). `packages/langchain/INTEGRATION_ISSUE.md`+ already carries the LangChain integration-issue text.+- **Google ADK (task 3)**: `examples/google-adk/` (package.json, index.mjs, README.md) connects+ an ADK agent to `https://three.ws/api/mcp-studio` via `MCPToolset`. `node index.mjs --check`+ discovers the live 15-tool catalog and runs a real `rig_mesh` call against production+ (returned a real viewer/GLB/embed/IRL/AR/run-receipt link set), proving the wiring without a+ Gemini credential; a full `LlmAgent` conversation runs when `GOOGLE_API_KEY` or Vertex+ credentials are present (neither exists in this sandbox, so that path is gated, not faked).+ `docs/google-adk.md` follows the `docs/grok.md` template and is linked from `docs/mcp.md`'s+ per-server guides and `data/pages.json` (which regenerated the changelog and page-index+ derived files via `npm run build:pages`).+- **Skills index (task 4)**: `/.well-known/skills/index.json` (20 entries) already shipped in+ `0871315f4`; re-validated this session by loading and counting it.+- **OpenRouter attribution (task 5)**: re-verified rather than re-built. All 19 files under+ `api/` that call `openrouter.ai/api` import the shared `openrouter-attribution` helper, zero+ exceptions.+- **Postman collection (task 6)**: new. `scripts/build-postman-collection.mjs` converts+ `public/.well-known/openapi.yaml` through `openapi-to-postmanv2` and checks in+ `public/.well-known/postman-collection.json`. The converter injects random ids and fabricated+ example values on every run regardless of `schemaFaker`; a `clean()` pass strips the ids,+ drops the fabricated response examples (no fake data, per CLAUDE.md), and canonicalizes+ free-form request-body placeholders. Verified deterministic across three independent+ regenerations (byte-identical) and loads cleanly through the official `postman-collection`+ SDK (`new Collection(data)`, 3 top-level items). Converting the spec surfaced nine+ pre-existing em-dashes in `public/.well-known/openapi.yaml` itself (a hard-rule violation+ this change now touches); fixed in the same commit. `build:postman-collection` /+ `check:postman-collection` are wired into `npm run gate`.+- **Registry entries (task 7)**: the six files for Hermes, Kilo, OpenHands, OpenCode, Dify and+ cursor.directory already existed in `marketing/growth/submissions/agent-registries/` from an+ earlier segment of this session; confirmed present, one per registry.+- **`npm pack --dry-run` (task 8)**: clean for both packages (re-verified above).+- **Docs (task 9)**: `docs/google-adk.md` (new), `docs/mcp.md` and `docs/api-reference.md`+ updated, `STRUCTURE.md` rows for the Google ADK example, the Postman collection, and (a gap+ from the earlier `e388d1458` commit) the `@three-ws/ai-sdk`/`@three-ws/langchain` npm+ workspace entries, `data/pages.json` entry for `/docs/google-adk`, changelog regenerated via+ `npm run build:pages`.+- **`npm test`**: 44 failed files / 2354 passed (80 failed tests, 35372 passed, 244 skipped),+ the same pre-existing, environment-dependent baseline (OAuth, MCP wallet, idempotency-key,+ ops-mcp-clients) orders 089-092 each independently measured in this shared worktree; none of+ the failing files reference ai-sdk, langchain, google-adk, or the Postman collection.+- **`npm run audit:docs`**: 21 findings, the same pre-existing baseline; none reference the new+ doc page, example, or collection.+- **`npm run check:rules`** against every touched path across both commits: `OK: no hard-rule+ violations in the added lines`.++Two steps are owner-gated (CLAUDE.md gate 2: publish, and contact a third party) and cannot be+done inside this session: `npm publish --access public` for `@three-ws/ai-sdk` and+`@three-ws/langchain`, opening the LangChain integration issue+(`packages/langchain/INTEGRATION_ISSUE.md`), and submitting the six registry entries per each+file's own "Owner steps" section. Logged as row 56 in+[_context/production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md). The order file+stays in place (not deleted) until those publishes and submissions land. Commits: `746c27934`+(Google ADK example and docs), `5b7ebbf19` (Postman collection, openapi.yaml em-dash fix),+this entry's commit (owner-actions row and the order file's Evolve status paragraph).diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 2aeb71aae..6e3bb0430 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -70,6 +70,8 @@ on it; some resolve themselves as other work lands.| 54 | **Register the Shopify Partner app, run its migration, and verify the photo-to-3D flow on a development store** (added 2026-10-13 by the evolve loop closing out order 091-partners-08). The embedded app ([`api/shopify/`](../../api/shopify/), [`api/_lib/shopify/`](../../api/_lib/shopify/), [`pages/shopify-app.html`](../../pages/shopify-app.html), [`src/shopify-app/app.js`](../../src/shopify-app/app.js), migration [`20261015060000_shopify_app.sql`](../../api/_lib/migrations/20261015060000_shopify_app.sql)) is built and unit-tested (`tests/shopify-hmac.test.js`, `tests/shopify-session-token.test.js`, `tests/shopify-store.test.js`, `tests/shopify-graphql.test.js`, `tests/shopify-webhooks.test.js`, 42/42 passing, real HMAC/JWT round trips and a real PGlite-backed store, no mocked SQL semantics). No Shopify Partner app exists in production yet (`node scripts/read-service-env.mjs '^SHOPIFY' --names` returns zero matches), so nothing past OAuth is testable from this workspace, and the migration is deliberately left unapplied (`npm run db:status` lists it `[pending]`): this evolve session is denied every owner-gated action, applying migrations to the production database included. Full step-by-step with exact Partner Dashboard settings and the App Store listing copy: [`marketing/growth/submissions/shopify-app.md`](../../marketing/growth/submissions/shopify-app.md). Summary: (a) create the Shopify Partner account and app, App URL `https://three.ws/apps/shopify`, redirect `https://three.ws/api/shopify/callback`; (b) set scopes to `read_products,write_products` and enable embedding; (c) `gcloud run services update three-ws-api --region us-central1 --update-env-vars SHOPIFY_API_KEY=...,SHOPIFY_API_SECRET=...,SHOPIFY_APP_URL=https://three.ws` (never `--set-env-vars`), plus `VITE_SHOPIFY_API_KEY` as a build-time variable before the next frontend build; (d) `npm run db:status` then `npm run db:migrate` to create the four `shopify_*` tables (applies immediately, no dry run); (e) create a development store, install the app, generate and attach a model, confirm it renders on the live storefront product page, approve a test-mode Billing charge, and send test webhook deliveries for the three mandatory topics plus `app/uninstalled` from the Partner Dashboard (screenshots); (f) submit the App Store listing using the exact copy in the submission file. | one Partner Dashboard app + one env update + one migration apply + one live development-store verification + one App Store submission | Turns on the Shopify app for real merchants; completes order 091's three live-verification Definition of Done lines | [091-partners-08-shopify-product-media.md](../091-partners-08-shopify-product-media.md), [marketing/growth/submissions/shopify-app.md](../../marketing/growth/submissions/shopify-app.md) || 55 | **Register the VRoid Hub developer application, set its client credentials, run its migration, and verify the avatar import on a real VRoid Hub account** (added 2026-10-13 by the evolve loop closing out order 092-partners-09). The OAuth connect flow, license evaluator, listing endpoint, and import endpoint ([`api/auth/vroid/[action].js`](../../api/auth/vroid/%5Baction%5D.js), [`api/_lib/vroid/`](../../api/_lib/vroid/), [`api/vroid/`](../../api/vroid/), [`pages/import-vroid.html`](../../pages/import-vroid.html), migration [`20261015070000_vroid_hub_source.sql`](../../api/_lib/migrations/20261015070000_vroid_hub_source.sql)) are built and unit-tested (`tests/vroid-license.test.js`, 9/9 passing). Every endpoint shape (PKCE requirement on `/oauth/authorize`, the Doorkeeper `/oauth/token` grant-type requirement, the `{data,error,_links,rand}` envelope, the real `CharacterModelLicenseSerializer` fields, and the two-step `download_licenses` flow) was confirmed live against `hub.vroid.com` and `developer.vroid.com`'s published API reference this session, not guessed. No VRoid Hub application exists in production yet (`node scripts/read-service-env.mjs '^VROID' --names` returns zero matches), so nothing past OAuth is testable from this workspace, and the migration is deliberately left unapplied (`npm run db:status` lists it `[pending]`): this evolve session is denied every owner-gated action, applying migrations to the production database included. Full step-by-step with exact hub.vroid.com/oauth/applications settings: [`marketing/growth/submissions/vroid-hub-app.md`](../../marketing/growth/submissions/vroid-hub-app.md). Summary: (a) create the application at `hub.vroid.com/oauth/applications` (confirmed live 2026-10-13, a real pixiv-account "Application management" sign-in screen), redirect URI `https://three.ws/api/auth/vroid/callback`, and submit for approval if the dashboard requires it; (b) no scope changes needed beyond VRoid Hub's own `default` scope; (c) `gcloud run services update three-ws-api --region us-central1 --update-env-vars VROID_HUB_CLIENT_ID=...,VROID_HUB_CLIENT_SECRET=...` (never `--set-env-vars`); (d) `npm run db:status` then `npm run db:migrate` to widen the `avatars.source` check constraint (applies immediately, no dry run); (e) connect a real VRoid Hub account at `/import/vroid`, import a character, confirm it lands on `/avatars/{id}/edit` with idle/walk playing, confirm the creator credit line renders, and confirm a license that disallows an action actually blocks it (screenshots). | one hub.vroid.com app + one env update + one migration apply + one live account verification | Turns on the VRoid Hub avatar import for real users; completes order 092's live-verification Definition of Done lines | [092-partners-09-vroid-hub-import.md](../092-partners-09-vroid-hub-import.md), [marketing/growth/submissions/vroid-hub-app.md](../../marketing/growth/submissions/vroid-hub-app.md) |+| 56 | **Publish the AI SDK/LangChain packages and submit the six agent-registry entries plus the LangChain integration issue** (added 2026-10-13 by the evolve loop closing out order 093-partners-10). `packages/ai-sdk/` (`@three-ws/ai-sdk`) and `packages/langchain/` (`@three-ws/langchain`) are both built, real-API-tested (`npm test` in each: 5/5 passing, live calls against production forge/rig/render/agent-chat/animate), and `npm pack --dry-run` clean. Neither has ever been published (new package names, no npm publish has run from this workspace). The six registry entries for Hermes, Kilo, OpenHands, OpenCode, Dify and cursor.directory are written in `marketing/growth/submissions/agent-registries/` in each registry's confirmed real format, and the LangChain integration-package issue text is at [`packages/langchain/INTEGRATION_ISSUE.md`](../../packages/langchain/INTEGRATION_ISSUE.md). Summary: (a) `cd packages/ai-sdk && npm publish --access public`, then the same in `packages/langchain/`; (b) open the LangChain integration issue against `langchain-ai/langchainjs` using `packages/langchain/INTEGRATION_ISSUE.md`'s text; (c) submit each of the six registry entries per its own file's "Owner steps" section in `marketing/growth/submissions/agent-registries/`. | two npm publishes + one GitHub issue + six registry submissions | Lists three.ws in the Vercel AI SDK and LangChain JS tool ecosystems and in six agent-framework registries | [093-partners-10-agent-tool-packages.md](../093-partners-10-agent-tool-packages.md), [packages/langchain/INTEGRATION_ISSUE.md](../../packages/langchain/INTEGRATION_ISSUE.md), [marketing/growth/submissions/agent-registries/](../../marketing/growth/submissions/agent-registries/) |+Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), whichdeclared itself "delete on reading" and had outlived that by three weeks.