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(partners): prep LiveKit and Pipecat submission packets, log owner actions for PyPI publish and the upstream PRs
nirholas230d014bd8ef
diff --git a/marketing/growth/opportunities.csv b/marketing/growth/opportunities.csvindex e8f6bd4fa..734316e8c 100644--- a/marketing/growth/opportunities.csv+++ b/marketing/growth/opportunities.csv@@ -61,7 +61,7 @@"P2","14","Jenqyang Awesome-AI-Agents listing","new-directory","not_started","PR one line under Applications or Tools (precedent: PR 498 merged 2026-09-18)","Owner","2026-09-25","src/element.js","A same-day-merging agent list","Merged PR URL","https://github.com/Jenqyang/Awesome-AI-Agents","2026-09-18""P2","14","three.js forum Showcase thread","owned-community","not_started","Owner posts a Forge or agent-3d showcase thread (24 new showcase topics since 2026-09-01; no three.ws thread exists)","Owner","2026-10-02","docs/share-and-embed.md","The canonical three.js builder audience","Live forum thread URL","https://discourse.threejs.org/c/showcase/7","2026-09-18""P2","13","LangChain JS tool integration","integration-registry","build_required","LangChain now takes integrations through an issue first and closes hand-written PRs automatically. Build the package in order 093, then the owner opens the integration issue (938)","Owner + eng","2026-10-23","packages","Listing in LangChain JS tools beside a same-shape generative-media tool","Accepted integration issue, published package and docs listing","https://github.com/langchain-ai/docs","2026-10-09"-"P2","12","LiveKit Agents avatar plugin","integration-partner","build_required","Decided: client-rendered, no server render lane (livekit/agents PR 5821, merged 2026-07-20, renders on the visitor device and sends motion data). Build in order 087, then the owner opens the plugin PR (938) and applies to LiveKit Startups (939)","Owner + eng","2026-10-30","src/runtime/livekit-voice.js","An avatar plugin in a 14k-star voice agent framework we already depend on","Merged plugin PR and a listing on the LiveKit avatar docs page","https://github.com/livekit/agents","2026-10-09"+"P2","12","LiveKit Agents avatar plugin","integration-partner","submission_ready","Built and verified in order 087 (livekit-plugins-threews: tests, ruff, and a real local-livekit-server browser E2E lipsync+gesture demo all pass). Owner opens the plugin PR (938) and applies to LiveKit Startups (939); submission text at marketing/growth/submissions/livekit-avatar-plugin.md","Owner + eng","2026-10-30","src/runtime/livekit-voice.js","An avatar plugin in a 14k-star voice agent framework we already depend on","Merged plugin PR and a listing on the LiveKit avatar docs page","https://github.com/livekit/agents","2026-10-13""P0","19","Web3D 2026 Competitions (AI and HAnim tracks)","new-event","not_started","Enter the AI and Web3D and HAnim animation competitions on easychair.org/conferences/?conf=web3d26 before 2026-09-30 23:00 PDT","Owner","2026-09-30","src/animation-retarget.js","Prize and a conference showcase for browser 3D agents at the Web3D consortium's own event","Submission receipt then results page","https://web3d.siggraph.org/","2026-09-18""P0","18","Colosseum Crypto World's Fair","new-event","not_started","Register and confirm in the official rules whether an existing product may enter; submissions due 2026-10-12","Owner","2026-10-12","docs/x402-distribution.md","Solana track prizes and an accelerator interview for x402 agent payments","Submission URL then results","https://colosseum.com/worldsfair","2026-09-18""P0","18","Walk Avatar on Chrome Edge and Firefox stores","owned-install-surface","release_checklist_open","Complete extensions/walk-avatar/RELEASE.md, build the zip, submit to Chrome Web Store then Edge Add-ons then Firefox Add-ons","Owner + eng","2026-10-02","extensions/walk-avatar","An installable browser surface that two published articles already described as live","Three live store URLs","https://chrome.google.com/webstore/devconsole","2026-09-18"@@ -99,7 +99,7 @@"P2","14","Microsoft Store and pwa.directory PWA listings","installable-distribution","not_started","Check the Store financial-services policy, package with PWABuilder, submit; submit pwa.directory free","Owner","2026-10-16","vite.config.js","Two install surfaces for the existing PWA","Two live listings","https://pwa.directory/submit","2026-09-18""P0","19","Tripo partner key and house lane","new-partner","reply_draft_ready","Owner sends the reply in docs/partners/tripo.md and holds the first call (order 936); order 084 builds the v3 house lane behind TRIPO_API_KEY","Owner + eng","2026-10-12","docs/partners/tripo.md","Tripo in front of every Forge user instead of the few who bring their own key, plus v3, webhooks and rig, splat and segmentation endpoints","Signed pilot, key on the service, Tripo house-lane jobs in forge_creations","https://developers.tripo3d.ai","2026-10-09""P1","17","Microsoft Copilot Studio and Microsoft 365 Copilot MCP certification","new-program","not_started","Draft the Partner Center application (order 939) and submit before the legacy route closes 2026-10-31","Owner","2026-10-24","mcp-server","A certified MCP connector in Copilot Studio and Microsoft 365 Copilot","Certified connector listing","https://learn.microsoft.com/en-us/microsoft-copilot-studio/","2026-10-09"-"P1","17","Pipecat community avatar integration","integration-registry","build_required","Build integrations/pipecat in order 087, then the owner opens the community-integration docs PR (938)","Owner + eng","2026-11-06","src/runtime/livekit-voice.js","A 3D avatar service listed among Pipecat community integrations","Merged docs PR","https://github.com/pipecat-ai/pipecat","2026-10-09"+"P1","17","Pipecat community avatar integration","integration-registry","submission_ready","Built and verified in order 087 (pipecat-threews: tests, ruff, and a real local-livekit-server browser E2E lipsync+gesture demo all pass, demo video captured). Owner opens the community-integration docs PR (938); submission text at marketing/growth/submissions/pipecat-integration.md","Owner + eng","2026-11-06","src/runtime/livekit-voice.js","A 3D avatar service listed among Pipecat community integrations","Merged docs PR","https://github.com/pipecat-ai/pipecat","2026-10-13""P1","16","Discord Activity","integration-partner","build_required","Build the Activity in order 088, then the owner completes app verification and Activity Discovery (939)","Owner + eng","2026-11-13","api/gateway/discord.js","A shared 3D Forge and agent inside Discord voice channels","Activity listed in the App Directory","https://discord.com/developers/docs/activities/overview","2026-10-09""P1","16","Craftcloud print fulfillment","integration-partner","build_required","Build the get-it-printed button and the Craftcloud adapter in order 089 against the public v5 API","Owner + eng","2026-11-06","api/_lib/print/adapters/contract.js","Live print quotes from 186 shops on every Forge model, with referral revenue","Live quotes on model pages and the first referred order","https://api.craftcloud3d.com/docs","2026-10-09""P1","16","Shopify product-media app","installable-distribution","build_required","Build integrations/shopify in order 091, then the owner creates the Partner account and submits to the App Store (939)","Owner + eng","2026-11-27","integrations","Photo to GLB and USDZ product media for Shopify merchants, billed through Shopify","Approved App Store listing","https://shopify.dev/docs/apps","2026-10-09"diff --git a/marketing/growth/submissions/livekit-avatar-plugin.md b/marketing/growth/submissions/livekit-avatar-plugin.mdnew file mode 100644index 000000000..42c40470c--- /dev/null+++ b/marketing/growth/submissions/livekit-avatar-plugin.md@@ -0,0 +1,93 @@+# LiveKit Agents avatar plugin submission++Target: [livekit/agents](https://github.com/livekit/agents), following the layout and+contribution bar set by their own merged client-rendered avatar plugin (PR #5821,+merged 2026-07-20) and `CONTRIBUTING.md`.++Ready for owner order 938. Built, tested, and verified end to end in work order 087;+the pull request and the LiveKit Startups application (939) are owner actions (see+CLAUDE.md gate 2: `git push` / publishing to a third party needs explicit owner+approval).++## What ships++`integrations/livekit/livekit-plugins-threews/` (package `livekit-plugins-threews`,+module `livekit.plugins.threews`), laid out the way livekit/agents expects+(`livekit-plugins/livekit-plugins-<name>`):++- `livekit/plugins/threews/avatar.py`: `AvatarSession`, joins the room beside the+ agent and republishes its TTS text and user-turn VAD events as+ `transcript` / `gesture` / `speech_started` / `speech_ended` JSON messages over the+ room's data channel. No audio or video synthesis; the three.ws `<agent-3d>` element+ already renders the avatar client-side.+- `examples/avatar_agent.py`: a complete, runnable example against a real local+ open-source `livekit-server`, no cloud account or API key required.+- `tests/test_avatar.py`: unit tests against a real `AgentSession`/`rtc.Room`+ instance (no mocks for the plugin's own logic).++## Pull request title++```text+Add three.ws avatar plugin (livekit-plugins-threews)+```++## Pull request description++```markdown+## What++Adds `livekit-plugins-threews`, an `AvatarSession` plugin that drives a+[three.ws](https://three.ws) `<agent-3d>` 3D avatar's lipsync and gestures from any+LiveKit `AgentSession`.++## Why++Every avatar provider on the current [avatar docs+page](https://docs.livekit.io/agents/integrations/avatar/) renders 2D video+server-side. three.ws avatars render entirely on the visitor's own device (the 3D+model, rig, and animation clip library already live in the browser), so this plugin+never synthesizes audio or video: it republishes the agent's TTS text and VAD+turn-taking events as small JSON messages over the room's existing data channel, and+the browser-side `<agent-3d voice="livekit">` element (already shipping in+production) renders the lipsync and gesture locally. Same pattern as PR #5821, applied+to a client-rendered 3D avatar instead of a 2D video one.++## How it was tested++- `ruff check` / `ruff format --check` pass.+- Unit tests in `tests/` run the plugin against a real `AgentSession`.+- End-to-end: a real agent joined a local open-source `livekit-server`, spoke through+ a real TTS service, and a real headless Chromium browser running+ `<agent-3d voice="livekit">` received and rendered the lipsync and gesture data+ (Playwright spec, video/screenshot attached).++## Checklist++- [x] Follows the `livekit-plugins/livekit-plugins-<name>` package layout+- [x] Passes `ruff check` / `ruff format`+- [x] Ships a runnable example+- [x] Ships unit tests+```++## Verification packet++- Public source: `https://github.com/nirholas/three.ws/tree/main/integrations/livekit/livekit-plugins-threews`+- License: Apache-2.0 (verified against the repository's own `LICENSE`)+- Example: `integrations/livekit/livekit-plugins-threews/examples/avatar_agent.py`+- Tests: `integrations/livekit/livekit-plugins-threews/tests/test_avatar.py`+ (`python -m pytest tests/ -v`, 2 passed)+- Lint/format: `ruff check .` and `ruff format --check .` both pass, config mirrors+ livekit/agents's own `[tool.ruff]` block+- Browser proof: `tests/e2e/agent-3d-livekit-avatar.spec.js` (real local+ `livekit-server`, real headless browser, 1 passed), screenshot captured at+ `test-results/agent-3d-livekit-avatar-*/agent-3d-livekit-avatar-final.png`+ (gitignored, local to the verifying machine; attach to the PR when opened)++## Owner steps (not automatable here)++1. Publish `livekit-plugins-threews` to PyPI (package metadata is already correct;+ this is a `pip install` publish action, not covered by the GCP credits this session+ may spend freely).+2. Open the pull request above against `livekit/agents`.+3. Apply to the [LiveKit Startups program](https://livekit.io) (up to USD 23,000)+ once the plugin PR is open, referencing it.diff --git a/marketing/growth/submissions/pipecat-integration.md b/marketing/growth/submissions/pipecat-integration.mdnew file mode 100644index 000000000..e3bc46e7c--- /dev/null+++ b/marketing/growth/submissions/pipecat-integration.md@@ -0,0 +1,104 @@+# Pipecat community avatar integration submission++Target: [pipecat-ai/pipecat](https://github.com/pipecat-ai/pipecat), following+`COMMUNITY_INTEGRATIONS.md` step by step.++Ready for owner order 938. Built, tested, and verified end to end in work order 087;+the pull request is an owner action (CLAUDE.md gate 2: publishing to a third party+needs explicit owner approval).++## What ships++`integrations/pipecat/pipecat-threews/` (package `pipecat-threews`, module+`pipecat_threews`):++- `src/pipecat_threews/avatar.py`: `ThreeWsAvatarProcessor`, a `FrameProcessor`+ placed after the TTS service and before `transport.output()`. Republishes+ finished TTS turns and user VAD/transcription boundaries as `transcript` /+ `gesture` / `speech_started` / `speech_ended` JSON messages over the transport's+ data channel. No audio or video synthesis of its own.+- `examples/avatar_bot.py`: a complete, runnable example against a real local+ open-source `livekit-server`, speaking through a real local `espeak-ng` TTS+ service, no cloud account or API key required.+- `tests/test_avatar.py`: unit tests driven through Pipecat's own `run_test`+ pipeline harness (4 tests, no mocks of the processor's own logic).+- `docs-submission/pipecat-threews.mdx`: the full docs page, ready to drop in at+ `api-reference/server/extensions/pipecat-threews.mdx`.+- `docs-submission/supported-services-row.md`: the exact row and full-table diff for+ `api-reference/server/services/supported-services.mdx`.+- `docs-submission/docs-json-navigation.md`: the exact `docs.json` navigation diff.++## Pull request title++```text+docs: add three.ws Avatar community integration+```++## Pull request description++```markdown+## What++Adds the `pipecat-threews` community integration: a `FrameProcessor` that drives a+[three.ws](https://three.ws) `<agent-3d>` 3D avatar's lipsync and gestures from any+Pipecat pipeline, plus its docs page.++## Why++three.ws avatars render entirely on the visitor's own device (3D model, rig, and+animation clips already live in the browser). This processor never synthesizes audio+or video: it taps the TTS and user-turn frames already flowing through a Pipecat+pipeline and republishes them as small JSON messages over the active transport's+data channel. Any transport whose implementation routes output messages to a real+data channel (LiveKit, Daily) works unchanged.++## Files changed++- `api-reference/server/extensions/pipecat-threews.mdx` (new)+- `api-reference/server/services/supported-services.mdx` (new row)+- `docs.json` (new navigation entry)++## How it was tested++- `ruff check` / `ruff format --check` pass (Pipecat's own `[tool.ruff]` config).+- 4 unit tests in `tests/` run the processor through Pipecat's own `run_test`+ pipeline harness, including a regression test for a cross-turn transcript+ leakage bug found and fixed during this work (`_last_user_transcript` is now reset+ on every new user turn).+- End to end: a real bot joined a local open-source `livekit-server`, spoke three+ lines through a real `espeak-ng` TTS service, and a real headless Chromium browser+ running `<agent-3d voice="livekit">` received and rendered the matching lipsync+ and gesture data (Playwright spec, 30-60s demo video attached per+ `COMMUNITY_INTEGRATIONS.md`).++## Checklist++- [x] Package published to PyPI as `pipecat-threews`+- [x] Passes `ruff check` / `ruff format`+- [x] Ships a runnable example+- [x] Ships unit tests+- [x] Docs page, services table row, and `docs.json` entry included+- [x] Demo video attached+```++## Verification packet++- Public source: `https://github.com/nirholas/three.ws/tree/main/integrations/pipecat/pipecat-threews`+- License: Apache-2.0 (verified against the repository's own `LICENSE`)+- Example: `integrations/pipecat/pipecat-threews/examples/avatar_bot.py`+- Tests: `integrations/pipecat/pipecat-threews/tests/test_avatar.py`+ (`python -m pytest tests/ -v`, 4 passed)+- Lint/format: `ruff check .` and `ruff format --check .` both pass, config mirrors+ pipecat-ai/pipecat's own `[tool.ruff]` block+- Browser proof: `tests/e2e/agent-3d-pipecat-avatar.spec.js` (real local+ `livekit-server`, real bot process, real headless browser, 1 passed)+- Demo video: captured locally at+ `test-results/agent-3d-pipecat-avatar-ag-64cca-wser-avatar-lipsync-gesture/video.webm`+ (gitignored, not committed; attach to the PR when opened)++## Owner steps (not automatable here)++1. Publish `pipecat-threews` to PyPI (package metadata is already correct).+2. Open the documentation pull request above against `pipecat-ai/pipecat`, using the+ three files in `docs-submission/` verbatim.+3. Attach the local demo video (path above) to the pull request.diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 13334a8e8..68ba808c9 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -9,7 +9,7 @@ it and, if that unblocks a work order, say which one in the owning pack's `produRows carry the date they were added so staleness is visible. Re-verify a row before actingon it; some resolve themselves as other work lands.-## Open rows (2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)+## Open rows (2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)| # | Action | Size | Unblocks | Detail lives in ||---|---|---|---|---|@@ -64,6 +64,7 @@ on it; some resolve themselves as other work lands.| 49 | **Finish wiring the Tripo signed webhook (work order 084-partners-01), three linked steps.** (added 2026-10-12 by the evolve loop closing out order 084). Not an active bug today: `TRIPO_WEBHOOK_SECRET` is unset in production, so `verifySignature` in `api/forge/webhook/tripo.js` rejects before it ever touches the database, and polling (`pollJob` in `api/forge.js`) answers every Tripo job either way. But all three steps are needed together before the webhook path can turn on for real: (a) apply the pending idempotency-ledger migration, `node scripts/apply-migrations.mjs --apply --file 20261015040000_forge_webhook_deliveries.sql` (or `npm run db:migrate`, which applies every pending migration immediately with no dry run; `npm run db:status` shows it as the only one left from this order), since `claimForgeWebhookDelivery`/`markForgeWebhookApplied` in `api/_lib/forge-store.js` would otherwise hit `relation forge_webhook_deliveries does not exist` the first time a verified delivery arrives; (b) set `TRIPO_WEBHOOK_SECRET` (`gcloud run services update three-ws-api --region us-central1 --update-env-vars TRIPO_WEBHOOK_SECRET=...`, never `--set-env-vars`) to whatever Tripo's dashboard issues; (c) register the production webhook URL (`https://three.ws/api/forge/webhook/tripo`) in Tripo's own dashboard, which only exists once a Tripo account is set up, the same account gate order 936 tracks for `TRIPO_API_KEY`. Putting a platform-paid `TRIPO_API_KEY` on the service is tracked separately in **order 936** (`936-partners-13-tripo-reply-and-house-key.md`), not duplicated here, since that order is itself gated on the owner's reply and call with Tripo. | one migration apply + one env var + one dashboard step | Lets a Tripo generation complete by webhook instead of only by poll, once a Tripo account exists | [084-partners-01-tripo-v3-house-lane.md](../084-partners-01-tripo-v3-house-lane.md), [936-partners-13-tripo-reply-and-house-key.md](../936-partners-13-tripo-reply-and-house-key.md) || 50 | **Publish the CC0 bulk animation library to production** (added 2026-10-13 by the evolve loop closing out order 085-partners-02). `GET /api/animations/library` currently answers `total: 0` in production: the bulk motion library (previously baked from Mixamo, which Adobe's own Mixamo FAQ says may not be redistributed as raw files) has been rebuilt from two CC0 1.0 Universal sources, Quaternius's Universal Animation Library 2 and Mesh2Motion's human animation packs, 219 clips retargeted and verified locally (0 failures, every entry carries `source`/`license`). The only remaining step is to run `node scripts/cc0-animation-library.mjs --upload` with the production R2 credentials (`node scripts/read-service-env.mjs` to read them from the `three-ws-api` Cloud Run service if not already in `.env.local`), which publishes the staged manifest to the live bucket the endpoint reads at request time, no code deploy required. This was deliberately not run this session: it is a production-publish action (CLAUDE.md gate 2) that makes 219 clips reachable to real users and third-party mirrors immediately. Separately, and not blocking this row: the Adobe Mixamo redistribution-permission letter is drafted and ready at [`marketing/growth/submissions/adobe-mixamo-permission.md`](../../marketing/growth/submissions/adobe-mixamo-permission.md); sending it is owner order 938. | one upload command | Makes the openly-licensed bulk animation library live on `/animations` and `GET /api/animations/library` | [085-partners-02-animation-library-license.md](../085-partners-02-animation-library-license.md) |+| 51 | **Publish and submit the LiveKit and Pipecat avatar integrations** (added 2026-10-13 by the evolve loop closing out order 087-partners-04). Both packages (`integrations/livekit/livekit-plugins-threews/`, `integrations/pipecat/pipecat-threews/`) are built, tested (unit tests, ruff lint/format), and verified end to end against a real local `livekit-server` with real browser automation driving the actual avatar lipsync and gesture off a live agent/bot in both frameworks (Playwright specs, both passing; the Pipecat run also captured the 30-60s demo video `COMMUNITY_INTEGRATIONS.md` asks for, saved locally and gitignored). Three remaining steps are all owner actions (CLAUDE.md gate 2, external posting/publishing): (a) `python -m build && twine upload` (or equivalent) to publish each package to PyPI as `livekit-plugins-threews` and `pipecat-threews`; (b) open the LiveKit plugin pull request against `livekit/agents` using the title, description and verification packet in [`marketing/growth/submissions/livekit-avatar-plugin.md`](../../marketing/growth/submissions/livekit-avatar-plugin.md), then apply to the LiveKit Startups program; (c) open the Pipecat documentation pull request against `pipecat-ai/pipecat` using the three files in `integrations/pipecat/pipecat-threews/docs-submission/` and the text in [`marketing/growth/submissions/pipecat-integration.md`](../../marketing/growth/submissions/pipecat-integration.md), attaching the local demo video. | two PyPI publishes + two pull requests + one program application | LiveKit plugin PR 938/Startups 939, Pipecat community-integration listing | [087-partners-04-livekit-pipecat-avatar.md](../087-partners-04-livekit-pipecat-avatar.md) |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.