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(prompts): open the partners work-order campaign that builds every integration the outreach plan pitches

nirholas759c41a10132
diff --git a/prompts/README.md b/prompts/README.md
index 8ba977138..b95a39376 100644
--- a/prompts/README.md
+++ b/prompts/README.md
@@ -84,6 +84,7 @@ directory, never this table. For the order to run them in, see [RUN-ORDER.md](RU
| `openai-pr-` | The OpenAI Apps SDK submission pack. Briefs 01 to 05 shipped; 06 (the tool count drifted to 11 across the kit) and 07 (the go/no-go, never run) remain, with the portal submit owner-only. |
| `parity-` | Closing the gaps a teardown of a leading agent launchpad found ("Competitor X", [docs/research/competitor-teardown-2026-09.md](../docs/research/competitor-teardown-2026-09.md)): per-agent creator earnings, `/analytics`, an earnings leaderboard, selling a whole agent over x402, `/experiments`, `/stories`, the $THREE fee flow, MCP use cases and safe paid retries (015 to 022, runnable), plus shipping, the npm publish, directory listings, a comparison page, a builder competition, pricing levers and an X mention bot (919 to 925, owner-gated). Shared facts: [finish/_context/parity-00-CONTEXT.md](finish/_context/parity-00-CONTEXT.md). |
| `best3d-` | Closing the gaps found by the 2026-10-09 sweep of open-source and commercial 3D ([docs/research/3d-landscape-2026-10.md](../docs/research/3d-landscape-2026-10.md)): TRELLIS.2 default lane with Hunyuan territory enforcement, Pixal3D and multi-view, non-humanoid rigging, editable parts, LOD and engine QA, engine bridges, the `<agent-3d>` AR contract, WebGPU, three-vrm, Audio2Face-3D, prompt-to-clip, keep-the-rig, signed exports, Scene Studio agent tab, splat parity, companion presence and generation controls (067 to 083, runnable), plus pricing preview, SAM 3D Objects, an orphaned-avatar campaign and store publishing (932 to 935, owner-gated). Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |
+| `partners-` | Working the 2026-10-09 partner prospects list ([docs/partners/prospects.md](../docs/partners/prospects.md), executed by [the outreach plan](../docs/partners/outreach-plan.md)), opened when Tripo reached out: the Tripo v3 house lane, the animation library off Mixamo clips, an open-source credits page, LiveKit and Pipecat avatar plugins, a Discord Activity, "get it printed" through Craftcloud, a video-to-motion landing, a Shopify product-media app, VRoid Hub import, agent-framework tool packages, site-builder embeds and the HACS package (084 to 095, runnable), plus the Tripo reply and house key, sponsorships, third-party submissions, program applications and a Sketchfab re-tag (936 to 940, owner-gated). Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |
| `production-100-` | The run-to-100% campaign: a master index sequencing every open work order toward a mechanically checkable "production ready, roadmap complete" end state, a standing ship-readiness order, closeout orders for residuals no other campaign owned (stranded custodial funds, master-key hygiene, verdict tuning), and the batched owner-action list. Its map was re-measured against code and production on 2026-09-01; start there. |
| `quality-bar-` | The GCP-credit quality campaign. Six open orders (fleet scale, PBR materials, forge UX, design system, mobile, avatar likeness); the reference pipeline, flagship lane, viewers and eval harness shipped. |
| `roadmap-` | Five runnable orders for existing surfaces (generation suite, creation consolidation, parametric avatar editor, developer resources, native home-screen widgets), plus the strategy layer ([the playbook](../docs/internal/fable-playbook.md)) that decides what to run next and [the reuse map](finish/roadmap-REUSE-MAP.md) for license-vetted OSS. |
diff --git a/prompts/finish/084-partners-01-tripo-v3-house-lane.md b/prompts/finish/084-partners-01-tripo-v3-house-lane.md
new file mode 100644
index 000000000..2efad4ec5
--- /dev/null
+++ b/prompts/finish/084-partners-01-tripo-v3-house-lane.md
@@ -0,0 +1,67 @@
+# partners 01: Tripo v3 house lane, webhooks, and the endpoints we do not use yet
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+Tripo reached out on 2026-10-09. Its v3.1 model is a Forge lane today, but only for users who paste their own key, over the legacy v2 endpoint, so it ran 2 jobs in the 30 days before the brief while the open-weight TripoSG worker ran 197. The brief ([docs/partners/tripo.md](../../docs/partners/tripo.md)) offers Tripo a v3 migration, webhooks, and five endpoints we do not use yet, and asks for a partner key. This order builds all of it so that the deal, when it lands, is switched on by one env var: `TRIPO_API_KEY`. Nothing here waits on the deal, and everything is kept whichever way it goes.
+
+## Step 0: re-derive the current state
+
+ sed -n 1,90p api/_providers/tripo.js
+ grep -n -A20 "tripo: Object.freeze" api/_lib/forge-tiers.js
+ node scripts/read-service-env.mjs '^TRIPO' --names
+ ls api/print/webhook/ && sed -n 1,40p "api/print/webhook/[provider].js"
+
+Read the v2-to-v3 migration guide and the webhook, rig, retarget, low-poly, splat and segmentation pages at developers.tripo3d.ai, and record the endpoint, request and webhook signature scheme for each. Query `forge_creations` (DATABASE_URL in `.env.local`) for Tripo-family jobs by `backend` over the last 30 days, so the final report can show before and after.
+
+## Tasks
+
+1. **v3 client.** Move [`api/_providers/tripo.js`](../../api/_providers/tripo.js) to the v3 API per Tripo's migration guide, keeping the provider interface every caller uses and the `TRIPO_MODEL_VERSION` override. Unit tests pin the v3 request shapes.
+2. **Signed webhooks.** Add a Tripo webhook receiver that verifies Tripo's signature, is idempotent on delivery id, and completes the job the same way polling does. Polling stays as the fallback when no webhook arrives in time. Follow the receiver pattern in `api/print/webhook/[provider].js`.
+3. **House key.** When `TRIPO_API_KEY` is set on the service, Tripo becomes a house lane: a default engine on the High tier and an explicit "Tripo" choice in the engine picker, billed through our credits like the other house lanes. A user's own key still takes precedence when supplied. With the variable unset, behavior is byte-for-byte what it is today; prove that with a test.
+4. **The endpoints we do not use yet**, each available only when a key (house or user) is present and each with its own UI state:
+ - auto-rig and retarget on the avatar path, with output that passes `src/glb-canonicalize.js` and plays the canonical clips;
+ - the low-poly (P-series) and quad options as a "game-ready" Forge preset;
+ - image-to-splat on the splat stage ([docs/splat.md](../../docs/splat.md));
+ - Smart Segmentation feeding the parts editor (coordinate with best3d order 070 if it is still open: one parts surface, not two).
+5. **Attribution.** The engine picker, the result card and exported file metadata name Tripo and the model version.
+6. **Reporting for the pilot.** A query script under `scripts/` that prints Tripo-lane jobs, completion rate and median latency by day from `forge_creations`, so the pilot report in the brief is one command.
+7. **Docs.** The Tripo lane in [docs/forge.md](../../docs/forge.md); change the "Engineering, ready to run" section of [docs/partners/tripo.md](../../docs/partners/tripo.md) to say what shipped; a `data/changelog.json` entry for the user-visible parts (BYOK users get v3 and the new endpoints immediately), then `npm run build:pages`.
+
+## Definition of done
+
+- [ ] With a Tripo key available (a user key in a real BYOK session counts), a text job and an image job complete on v3, and a webhook delivery completes a job.
+- [ ] With `TRIPO_API_KEY` unset, the engine list and job routing are unchanged (test output).
+- [ ] Auto-rig output loads in the viewer and plays a canonical clip; the game-ready preset, splat and segmentation each produce a real artifact or show their designed unavailable state.
+- [ ] `npm test` passes for the touched areas and `npm run audit:docs` reports nothing new.
+- [ ] Docs and changelog entry landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| No Tripo key anywhere | Prove every request shape against the live v3 API's documented auth error, ship the code, and list `TRIPO_API_KEY` in the owner message. Approving a platform key is order 936. |
+
+## 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/084-partners-01-tripo-v3-house-lane.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/085-partners-02-animation-library-license.md b/prompts/finish/085-partners-02-animation-library-license.md
new file mode 100644
index 000000000..562842c00
--- /dev/null
+++ b/prompts/finish/085-partners-02-animation-library-license.md
@@ -0,0 +1,62 @@
+# partners 02: Move the public animation library off Mixamo clips
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+[`api/animations/library.js`](../../api/animations/library.js) publicly serves a bulk clip library baked from Mixamo (`scripts/mixamo-all.mjs`) as raw JSON, and [`scripts/mirror-animation-library.mjs`](../../scripts/mirror-animation-library.mjs) exists so third parties can mirror it. Mixamo's terms, as Adobe states them on its community forum, allow royalty-free use of the animations inside projects but not redistribution of the animation files themselves. The partner sweep of 2026-10-09 flagged this as the one licensing risk that would embarrass us in front of any animation or avatar partner. Two CC0 libraries (Quaternius's Universal Animation Library and Mesh2Motion) and our own text-to-motion worker can replace it.
+
+## Step 0: re-derive the current state
+
+ sed -n 1,80p api/animations/library.js
+ sed -n 1,60p scripts/mixamo-all.mjs
+ sed -n 1,40p scripts/mirror-animation-library.mjs
+ grep -rln "animations/library" src api pages public --include=*.js --include=*.html | head -40
+ gh api repos/Mesh2Motion/mesh2motion-app --jq '[.full_name,.pushed_at[:10],.license.spdx_id]|@tsv'
+
+Count clips per manifest (Mixamo bake versus generative seeder) from the live endpoint (`?facets=1`) and record it. Read Mixamo's current FAQ and Adobe's terms, and quote the exact redistribution sentence in your report. Read the license on quaternius.com and in the Mesh2Motion repo for the animation assets specifically.
+
+## Tasks
+
+1. **CC0 replacement set.** Import the Quaternius Universal Animation Library and the Mesh2Motion CC0 clips, convert them to the library's clip format through the existing retarget pipeline, and fill gaps from the text-to-motion worker ([`workers/model-text2motion`](../../workers/model-text2motion/)). Map each Mixamo clip name the product deep-links to a replacement, so no consumer (the /animations gallery, the embed viewer, the pose studio) breaks.
+2. **Provenance on every entry.** Each manifest entry carries `source` and `license`. The gallery shows the credit per clip.
+3. **Public endpoints serve only what we may redistribute.** The library endpoint and the mirror script serve CC0 and self-generated clips. Mixamo-derived clips leave every public raw endpoint. Do not delete the stored Mixamo objects (unrecoverable data gate): unpublish them from the public manifest. If the license reading in step 0 supports keeping them for in-product playback applied to a user's avatar, keep that path and say why in the report; if it does not, the replacement set covers it.
+4. **Ask in writing for anything we want to keep.** Draft the permission request to Adobe in `marketing/growth/submissions/adobe-mixamo-permission.md`; sending it is owner order 938.
+5. **Docs.** A licensing section in the animation docs, the credit wired into the credits page (order 086, or its dataset if 086 has not run), and a changelog entry ("the animation library is now openly licensed").
+
+## Definition of done
+
+- [ ] No public endpoint or mirror path returns a Mixamo-derived clip (show the request and the manifest check).
+- [ ] Every product surface that used a Mixamo clip by name still plays a clip (browser check of /animations, the embed viewer and one pose deep link).
+- [ ] Every manifest entry has `source` and `license`.
+- [ ] `npm test` passes for the touched areas; `npm run audit:docs` reports nothing new.
+- [ ] Permission draft, docs and changelog entry landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| A clip has no CC0 equivalent | Generate it with the text-to-motion worker, and if that is not good enough, list it as kept for in-product playback only, with the reason. |
+
+## 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/085-partners-02-animation-library-license.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/086-partners-03-open-source-credits.md b/prompts/finish/086-partners-03-open-source-credits.md
new file mode 100644
index 000000000..f79072588
--- /dev/null
+++ b/prompts/finish/086-partners-03-open-source-credits.md
@@ -0,0 +1,61 @@
+# partners 03: Open-source credits page and in-surface credits
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+The partner sweep found that three.ws credits almost none of the open source it stands on where a visitor can see it. /objects is built from Poly Haven's CC0 catalog and never says so. meshoptimizer's credit lives in the header of a vendored file. The Forge does not name the open models that made a result. Every open-source partnership in the [outreach plan](../../docs/partners/outreach-plan.md) climbs the ladder Use, Credit, Contribute, and we are stuck on the first rung. `/credits` is the billing page, so this needs its own route.
+
+## Step 0: re-derive the current state
+
+ cat NOTICE | head -60 && ls third_party
+ node -e "const p=require('./package.json');console.log(Object.keys(p.dependencies||{}).length,Object.keys(p.devDependencies||{}).length)"
+ grep -n '"path": "/open-source\|"path": "/credits' data/pages.json
+ grep -rn "polyhaven\|Poly Haven" src pages --include=*.js --include=*.html | head
+ ls workers | head -80
+
+List every GPU worker's model and its license from the worker READMEs, and every asset source (Poly Haven, Quaternius, Mesh2Motion, and anything else under `scripts/fetch-*`).
+
+## Tasks
+
+1. **A credits dataset generated from the source of truth.** A script under `scripts/` builds `data/open-source-credits.json` from `package.json` and the lockfile (name, license, repository, funding link), `NOTICE`, `third_party/`, worker model licenses, and asset sources, plus a short hand-written "what it powers here" line per major project kept in a small curated file. Wire it into the existing pages build without reordering the `build:gcp` chain (if you change a load-bearing script, update CLAUDE.md in the same commit).
+2. **The page.** A new route (for example `/open-source`) grouped by area: rendering, formats and compression, generation models, motion, voice, assets, infrastructure. Each entry shows the license, a link, what it powers in three.ws, and a "sponsor" link where the project publishes one. All states designed; responsive; accessible. Add it to `data/pages.json` and the footer.
+3. **In-surface credits.** Poly Haven on /objects and on each object page; the engine and model name on Forge results and in exported file metadata; the clip source in the animation gallery; meshoptimizer and glTF-Transform in the export dialog's "how this file was made" detail.
+4. **A guard.** A test that fails when a new direct dependency lands without a dataset entry, so the page cannot rot.
+5. **Docs.** `STRUCTURE.md` row, a short doc on how to add a credit, changelog entry.
+
+## Definition of done
+
+- [ ] The page renders in a real browser at 320, 768 and 1440 pixels, with no console errors, and lists every direct dependency.
+- [ ] Poly Haven is credited on /objects; a Forge result names its engine.
+- [ ] The guard test fails on an uncredited dependency and passes on main.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] `data/pages.json`, `STRUCTURE.md` and changelog entries landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/086-partners-03-open-source-credits.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/087-partners-04-livekit-pipecat-avatar.md b/prompts/finish/087-partners-04-livekit-pipecat-avatar.md
new file mode 100644
index 000000000..f09363ed7
--- /dev/null
+++ b/prompts/finish/087-partners-04-livekit-pipecat-avatar.md
@@ -0,0 +1,62 @@
+# partners 04: LiveKit avatar plugin and Pipecat avatar service
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+LiveKit Agents (14,665 stars, `livekit-client` 4.36M weekly downloads) lists 16 avatar providers on its avatar docs page, and every one is a 2D video face. three.ws already runs LiveKit voice ([`src/runtime/livekit-voice.js`](../../src/runtime/livekit-voice.js)). The tracker row for this plugin was parked on a design question: does a plugin need a server render lane? It does not. livekit/agents merged a plugin (PR #5821, 2026-07-20) that renders on the visitor's device and sends only motion data over LiveKit, which is how three.ws already works. Pipecat (16,309 stars) documents a community-integration route step by step and shares most of the work. LiveKit's new Startups program (up to USD 23,000) is the commercial door this opens.
+
+## Step 0: re-derive the current state
+
+ sed -n 1,60p src/runtime/livekit-voice.js
+ sed -n 1,40p api/agents/_id/livekit-token.js
+ gh pr view 5821 -R livekit/agents --json title,files,mergedAt
+ gh api repos/livekit/agents/contents/CONTRIBUTING.md --jq .content | base64 -d | head -80
+ gh api repos/pipecat-ai/pipecat/contents/COMMUNITY_INTEGRATIONS.md --jq .content | base64 -d | head -120
+
+Read the merged plugin's layout to learn the expected package structure and the motion-data transport, as reference only (build our own; copy no code).
+
+## Tasks
+
+1. **The LiveKit plugin.** A Python package `livekit-plugins-threews` in `integrations/livekit/` laid out the way livekit/agents expects (`livekit-plugins/livekit-plugins-<name>`), with an `AvatarSession` that joins the room beside the agent and publishes viseme and gesture data derived from the agent's TTS audio. It passes their lint (ruff) and docs (pdoc) requirements.
+2. **The client.** `<agent-3d>` gains a LiveKit mode: it joins with a token, subscribes to the plugin's motion data, and drives lip sync and gestures on the visitor's device. Reuse the existing viseme path.
+3. **The Pipecat service.** `integrations/pipecat/` with a Pipecat frame processor that does the same for a Pipecat pipeline, plus everything COMMUNITY_INTEGRATIONS.md asks for: example, README, and the docs pull request text.
+4. **A runnable example for each**, verified end to end against a local open-source `livekit-server` (no cloud credentials needed). Record the 30 to 60 second demo video Pipecat asks for from a real run.
+5. **Submission text** in `marketing/growth/submissions/livekit-avatar-plugin.md` and `marketing/growth/submissions/pipecat-integration.md`, ready for owner order 938. Update the tracker row for the LiveKit plugin from `design_decision_required` to its new status.
+6. **Docs.** README in each new directory, a doc page linked from [docs/start-here.md](../../docs/start-here.md), `STRUCTURE.md` row, changelog entry.
+
+## Definition of done
+
+- [ ] A voice agent in a local LiveKit room speaks and a browser `<agent-3d>` lip-syncs to it (screen recording or screenshots in the report).
+- [ ] The Pipecat example runs end to end the same way, and the demo video exists.
+- [ ] Both packages pass their upstream lint and docs checks locally.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] Submission files, READMEs, docs, `STRUCTURE.md` and changelog landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/087-partners-04-livekit-pipecat-avatar.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/088-partners-05-discord-activity.md b/prompts/finish/088-partners-05-discord-activity.md
new file mode 100644
index 000000000..f269179bc
--- /dev/null
+++ b/prompts/finish/088-partners-05-discord-activity.md
@@ -0,0 +1,59 @@
+# partners 05: A three.ws Discord Activity
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+Discord Activities are web apps that run inside Discord voice channels, and the App Directory lists a verified Activity within about 24 hours of meeting its Discovery criteria. three.ws already has a Discord chat gateway ([`api/gateway/discord.js`](../../api/gateway/discord.js)) but no Embedded App SDK integration. A group that can forge, pose and talk to 3D agents together inside a voice call is the most shareable thing on the prospects list, and purchases inside Activities are supported (15% on the first USD 1M).
+
+## Step 0: re-derive the current state
+
+ sed -n 1,60p api/gateway/discord.js
+ node scripts/read-service-env.mjs '^DISCORD' --names
+ npm view @discord/embedded-app-sdk version
+
+Read Discord's Activities docs: the Embedded App SDK, the OAuth token exchange, URL mappings through Discord's proxy (every fetch, socket and CDN asset must go through a mapped prefix), the content security rules, and the App Directory Discovery criteria.
+
+## Tasks
+
+1. **Choose the experience** from what exists and works best for a group: a shared Forge where everyone in the call generates and votes, with a three.ws agent in the room that talks and reacts. Keep it free of coin and wallet features; Discord's review and this campaign both call for that. Record the choice in one line.
+2. **The Activity entry point**, using `@discord/embedded-app-sdk`: authorize, exchange the code on a new server endpoint, authenticate, and map the Discord user to a three.ws session.
+3. **The proxy.** Route every network call through the mapped prefixes, and make the three.ws assets the Activity needs load inside Discord's content security policy.
+4. **Shared state per Activity instance**, so everyone in the voice channel sees the same scene.
+5. **Purchases.** If the experience sells anything, use Discord's in-app purchase flow; otherwise leave it out and say so.
+6. **Docs and submission.** A doc page, `STRUCTURE.md` row, changelog entry, and `marketing/growth/submissions/discord-activity.md` with the exact developer-portal settings (URL mappings, OAuth redirects, Activity flags) and Discovery listing copy for owner order 939.
+
+## Definition of done
+
+- [ ] The Activity loads and works inside the Discord client in a test server, with two accounts seeing the same state (screenshots).
+- [ ] No console errors inside the Discord frame; every request goes through a mapped prefix.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] Docs, `STRUCTURE.md`, changelog and the submission file landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/088-partners-05-discord-activity.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/089-partners-06-get-it-printed.md b/prompts/finish/089-partners-06-get-it-printed.md
new file mode 100644
index 000000000..a23b1be80
--- /dev/null
+++ b/prompts/finish/089-partners-06-get-it-printed.md
@@ -0,0 +1,61 @@
+# partners 06: "Get it printed" through Craftcloud, plus slicer trusted-host patches
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+The Forge already serves print-ready STL and 3MF at `/api/slicer/<id>/` and hands models to slicers. Craftcloud (All3DP) compares 186 print and CNC shops through a public v5 API (price, offer, cart, order, payment, referral voucher), so "get it printed" needs no deal to start. The materialize pipeline already defines a fulfillment adapter contract ([`api/_lib/print/adapters/contract.js`](../../api/_lib/print/adapters/contract.js)) for exactly this. Separately, the slicer buttons hit two walls: Bambu Studio warns that three.ws is "not from a trusted site", and PrusaSlicer's `Downloader.cpp` only accepts printables.com and thingiverse.com URLs.
+
+## Step 0: re-derive the current state
+
+ sed -n 1,80p api/_lib/print/adapters/contract.js
+ sed -n 1,60p api/_lib/print/adapters/manual.js
+ sed -n 1,60p docs/materialize.md
+ sed -n 1,40p src/slicer-handoff.js
+ gh api repos/prusa3d/PrusaSlicer/contents/src/slic3r/GUI/Downloader.cpp --jq .content | base64 -d | grep -n -i "printables\|thingiverse" | head
+ gh search code "trusted" --repo bambulab/BambuStudio --filename GUI_App.cpp --limit 5
+
+Read Craftcloud's API v5 docs at api.craftcloud3d.com/docs end to end: authentication, model upload, price and offer polling, cart, order and payment, the referral voucher, and whether a cart can be handed to the buyer for checkout on Craftcloud's side.
+
+## Tasks
+
+1. **The buyer-direct button.** On model pages and Forge results, "Get it printed" uploads the model to Craftcloud, shows live prices by material and shop, and hands the buyer to Craftcloud's checkout with our referral voucher applied, if the API supports a buyer-side checkout. The buyer pays Craftcloud directly, so three.ws spends nothing.
+2. **The adapter.** `api/_lib/print/adapters/craftcloud.js` implementing the contract (`configured()` on its env vars, capabilities from Craftcloud's material catalog, `submit`, `status`, `cancel`, webhook verification if offered), registered in `index.js` ahead of `manual`. Verify quoting against the live API. Placing a paid order is a spend: test up to cart creation and stop there.
+3. **Slicer patches, prepared not sent.** Build PrusaSlicer locally with a patch that makes the trusted download hosts configurable (or adds three.ws), and run its tests. Write the Bambu Studio issue text with the exact `GUI_App.cpp` reference. Both go in `marketing/growth/submissions/slicer-trusted-hosts.md` for owner order 938.
+4. **Docs.** The adapter in [docs/materialize.md](../../docs/materialize.md), the button in the Forge docs, changelog entry.
+
+## Definition of done
+
+- [ ] A real Forge model gets live Craftcloud prices on its page (screenshot plus the API response).
+- [ ] The buyer handoff opens Craftcloud's checkout with the voucher, or the report shows the API cannot do that and the adapter path covers it.
+- [ ] The adapter passes the contract's shape checks and its unit tests.
+- [ ] The PrusaSlicer patch builds and its tests pass locally.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new; docs and changelog landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/089-partners-06-get-it-printed.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/090-partners-07-video-to-motion-landing.md b/prompts/finish/090-partners-07-video-to-motion-landing.md
new file mode 100644
index 000000000..5048c149f
--- /dev/null
+++ b/prompts/finish/090-partners-07-video-to-motion-landing.md
@@ -0,0 +1,60 @@
+# partners 07: A video-to-motion landing for creators whose mocap service closed
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+Several online markerless motion-capture services have closed or stopped taking new captures in 2026 (the [prospects list](../../docs/partners/prospects.md) records which, with dates). Their users still have videos to turn into animation and nowhere to do it. three.ws already runs the pipeline: [`workers/model-video2motion`](../../workers/model-video2motion/) turns a video of a person into a retargetable clip on the canonical skeleton, and it powers /motion-swap. What is missing is a page that speaks to a creator who wants the animation file itself (FBX, BVH, GLB) rather than a composited video.
+
+## Step 0: re-derive the current state
+
+ sed -n 1,80p workers/model-video2motion/README.md
+ grep -n '"path": "/motion-swap\|"path": "/mocap-studio\|"path": "/animations' data/pages.json
+ ls src | grep -i -E "motion|mocap|bvh|fbx"
+ grep -rn "BVHLoader\|FBXExporter\|bvh" src --include=*.js | head
+
+Run one real video through the production worker (use a short clip of yourself or a CC0 video) and time it, so the page's copy quotes a measured duration. Check which export formats the client can already write.
+
+## Tasks
+
+1. **The landing page.** A new route (for example `/video-to-motion`) aimed at animators and VTubers: upload a video, preview the motion on a default avatar or the user's own, trim, and download. Every state is designed: idle, uploading, processing with the worker's real progress, result, failure with a retry path, and a limit reached state.
+2. **Exports.** GLB with the clip, BVH, and FBX if a maintained open-source exporter supports it (check before writing one; if none qualifies, ship GLB and BVH and say why). Retarget onto any rig the user uploads through `src/animation-retarget.js`.
+3. **Save to the library.** A signed-in user can save the clip to their own animations and apply it to their agents.
+4. **Copy.** Neutral: "turn any video into an animation file", with no names of closed services. Whether to name them in outreach is the owner's decision, recorded in the owner message.
+5. **Wire it in**: links from /motion-swap, /animations and /mocap-studio; `data/pages.json`; `STRUCTURE.md`; a doc page; changelog entry.
+
+## Definition of done
+
+- [ ] A real video becomes a downloadable GLB and BVH that load in Blender (screenshot of the import) or the three.js editor.
+- [ ] The clip retargets onto an uploaded non-Mixamo rig in the browser.
+- [ ] All states render at 320, 768 and 1440 pixels with no console errors.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] Page entry, `STRUCTURE.md`, doc and changelog landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/090-partners-07-video-to-motion-landing.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/091-partners-08-shopify-product-media.md b/prompts/finish/091-partners-08-shopify-product-media.md
new file mode 100644
index 000000000..0f460b5b1
--- /dev/null
+++ b/prompts/finish/091-partners-08-shopify-product-media.md
@@ -0,0 +1,61 @@
+# partners 08: A Shopify app that turns product photos into 3D product media
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+Shopify product pages accept 3D models as product media (GLB for the web viewer, USDZ for iOS AR) through the Admin GraphQL API's `productCreateMedia`, yet most merchants have no 3D files. The Forge turns a photo into a textured GLB, and the export path can produce USDZ. A Shopify app that does "pick a product, get a 3D model on the page" is a direct line to merchants, and Shopify's Billing API means the app charges through Shopify with no extra payment integration.
+
+## Step 0: re-derive the current state
+
+ grep -rn -i "usdz" src api --include=*.js | head
+ grep -rn -i "shopify" api src --include=*.js | head
+ npm view @shopify/shopify-app-remix version 2>/dev/null; npm view @shopify/shopify-api version
+
+Read Shopify's current docs for: app scaffolding and the recommended template, OAuth and session tokens for embedded apps, the `productCreateMedia` mutation and the staged-upload flow for 3D models, mandatory privacy webhooks, the Billing API, and the App Store requirements checklist.
+
+## Tasks
+
+1. **The app** in `integrations/shopify/`, built on Shopify's official app template and libraries: install, OAuth, embedded admin UI listing the shop's products with their current media.
+2. **The flow.** Pick a product, pick its best image, run a Forge job through the public API, preview the model in the embedded admin, then attach GLB and USDZ to the product with staged uploads and `productCreateMedia`. Bulk mode for many products, with real per-item status.
+3. **Billing** through the Billing API, priced from our Forge credit cost. Prove it against a development store in test mode, which charges nothing.
+4. **Compliance**: the three mandatory privacy webhooks, scopes kept to what the flow needs, and every App Store checklist item that can be met in code.
+5. **Submission package** in `marketing/growth/submissions/shopify-app.md`: listing copy, screenshots from a real development store, the test credentials Shopify review needs, and the steps for owner order 939 (Partner account, App Store submission).
+6. **Docs.** README in `integrations/shopify/`, a doc page, `STRUCTURE.md` row, changelog entry.
+
+## Definition of done
+
+- [ ] On a Shopify development store, a product photo becomes 3D media on the live storefront product page, viewable in the web viewer (screenshot).
+- [ ] A test-mode charge completes through the Billing API.
+- [ ] Privacy webhooks respond correctly to Shopify's test deliveries.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] Submission file, README, docs, `STRUCTURE.md` and changelog landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| No Shopify Partner account yet | Creating one is free but it is an external account in the owner's name: put it first in the owner message, build everything that does not need it, and verify the rest the moment it exists. |
+
+## 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/091-partners-08-shopify-product-media.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/092-partners-09-vroid-hub-import.md b/prompts/finish/092-partners-09-vroid-hub-import.md
new file mode 100644
index 000000000..add72fb5f
--- /dev/null
+++ b/prompts/finish/092-partners-09-vroid-hub-import.md
@@ -0,0 +1,59 @@
+# partners 09: Import an avatar from VRoid Hub
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+VRoid Hub is where a very large share of the world's VRM avatars live, and its API lets an approved app download a model on the user's behalf, subject to the license conditions the creator set on each model. three.ws already loads VRM, canonicalizes VRoid and VRM 1.0 skeletons ([`src/glb-canonicalize.js`](../../src/glb-canonicalize.js)) and has an import page pattern in /import/rpm. A "bring your VRoid Hub avatar" button turns three.ws into somewhere those avatars can talk, walk and act as agents.
+
+## Step 0: re-derive the current state
+
+ ls pages | grep -i import; grep -n '"path": "/import' data/pages.json
+ sed -n 1,60p "$(grep -rl "import/rpm" src --include=*.js | head -1)"
+ node scripts/read-service-env.mjs '^VROID' --names
+
+Read the VRoid Hub API docs (developer.vroid.com): app registration and approval, OAuth, the download-license flow, the per-model license fields (avatar use, commercial use, redistribution, alteration), and the attribution rules.
+
+## Tasks
+
+1. **OAuth** behind `VROID_HUB_CLIENT_ID` and `VROID_HUB_CLIENT_SECRET`, with the callback route and token storage following the existing OAuth patterns in `api/`.
+2. **The picker.** A page at `/import/vroid` listing the user's own models and their hearted models that allow download, each with its license conditions shown in plain words.
+3. **Enforce the license.** Only offer actions the model's conditions allow (for example, no public agent if the creator disallows it, no export if redistribution is disallowed), keep the creator credit on every surface the avatar appears on, and store the license fields with the avatar.
+4. **The import.** Download through the license flow, run the existing VRM load and canonicalize path, and land the user in the avatar editor with idle and walk playing.
+5. **Docs and submission.** A doc page, `data/pages.json` entry, `STRUCTURE.md` row, changelog entry, and `marketing/growth/submissions/vroid-hub-app.md` with the app registration answers for owner order 939.
+
+## Definition of done
+
+- [ ] With credentials present, a real VRoid Hub model imports and plays canonical clips; without them, the page shows its designed "coming soon to your account" state and the route returns no error.
+- [ ] A model whose license disallows an action never offers that action (unit test over the license mapping).
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] Docs, page entry, `STRUCTURE.md`, changelog and the submission file landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| VRoid Hub app approval pending | Build and unit-test the whole flow against the documented API shapes, verify the OAuth redirect against the live authorize endpoint, and leave the approval as owner order 939. |
+
+## 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/092-partners-09-vroid-hub-import.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/093-partners-10-agent-tool-packages.md b/prompts/finish/093-partners-10-agent-tool-packages.md
new file mode 100644
index 000000000..9f46335eb
--- /dev/null
+++ b/prompts/finish/093-partners-10-agent-tool-packages.md
@@ -0,0 +1,65 @@
+# partners 10: Tool packages and registry entries for the agent frameworks
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+Agents already call three.ws through MCP (13,898 tool calls in September from 13 distinct clients, per the [proof brief](../../docs/partners/proof-brief-2026-10.md)), but most agent frameworks find tools through their own packages and registries, and three.ws is in almost none of them. The [prospects list](../../docs/partners/prospects.md) scores about thirty frameworks and coding tools with a free listing route. This order builds everything those listings need so the owner's part (order 938) is opening pull requests and submitting forms with text that already exists.
+
+## Step 0: re-derive the current state
+
+ ls packages | head -120
+ cat public/.well-known/mcp.json | head -40
+ grep -rn "HTTP-Referer\|X-Title" api --include=*.js | head
+ npm view ai version; npm view @langchain/core version
+
+For each framework in the agent table of the prospects list, re-check the intake route on the day you run this (several changed during the 2026-10-09 sweep: LangChain now takes integrations through an issue first, and hand-written pull requests are closed automatically). Record what you found.
+
+## Tasks
+
+1. **`packages/ai-sdk`**: three.ws tools for the Vercel AI SDK (`tool()` definitions over the public API: forge, rig, animate, render, agent chat), typed, tested against the live API, with a README example that runs.
+2. **`packages/langchain`**: the same tools as LangChain JS tools, following LangChain's current integration-package template, with the integration issue text.
+3. **Google ADK**: a docs page and a runnable sample that connects an ADK agent to the three.ws MCP server.
+4. **A skills index** at `/.well-known/skills/index.json` describing the agent skills we publish, in the format the agent-skills registries read.
+5. **OpenRouter attribution**: every OpenRouter request the platform makes sends the same `HTTP-Referer` and `X-Title`, so three.ws appears in OpenRouter's app rankings.
+6. **A Postman collection** generated from `public/.well-known/openapi.yaml`, checked in and kept in sync by a script.
+7. **Registry entries** for Hermes, Kilo, OpenHands, OpenCode, Dify and cursor.directory: each entry file in the exact format the registry wants, plus its pull request or form text, in `marketing/growth/submissions/agent-registries/`.
+8. Build and check each package with `npm pack --dry-run`. Publishing to npm is owner order 938.
+9. **Docs.** README per package, the agent docs updated, `STRUCTURE.md` rows, changelog entry.
+
+## Definition of done
+
+- [ ] Each package's README example runs against the live API and returns real results (output in the report).
+- [ ] `npm pack --dry-run` is clean for each package.
+- [ ] The skills index and Postman collection validate against their schemas.
+- [ ] One registry submission file per registry exists, matching the format checked in step 0.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] READMEs, docs, `STRUCTURE.md` and changelog landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/093-partners-10-agent-tool-packages.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/094-partners-11-site-builder-embeds.md b/prompts/finish/094-partners-11-site-builder-embeds.md
new file mode 100644
index 000000000..84a897091
--- /dev/null
+++ b/prompts/finish/094-partners-11-site-builder-embeds.md
@@ -0,0 +1,59 @@
+# partners 11: WordPress, Framer and Webflow embeds for <agent-3d>
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+The `<agent-3d>` web component already embeds anywhere with one script tag, SRI-pinned to an immutable release. Site builders are where non-developers put things on the web, and each has a directory: the WordPress plugin directory, the Framer marketplace, and the Webflow Apps marketplace. A native block or component in each turns "paste this script" into "search for three.ws".
+
+## Step 0: re-derive the current state
+
+ cat data/agent-3d-releases.json | head -30
+ grep -n "integrity=" docs/*.md | head
+ ls integrations
+
+Read the current submission rules for the WordPress plugin directory (readme.txt format, plugin check, security review), Framer code components and marketplace, and Webflow Designer Extensions and the Webflow Apps marketplace.
+
+## Tasks
+
+1. **WordPress**: `integrations/wordpress/`, a block plugin (block.json, editor preview, server render) that loads the SRI-pinned `<agent-3d>` release and takes an agent id or model URL, with shortcode fallback for the classic editor. Passes the official Plugin Check locally (run it in a local WordPress through docker). A `readme.txt` in the directory's format.
+2. **Framer**: `integrations/framer/`, a code component with property controls (agent, model, autoplay, background), tested in a real Framer project if an account exists, and its marketplace listing text.
+3. **Webflow**: `integrations/webflow/`, a Designer Extension or the documented embed path that inserts the element, plus listing text.
+4. **One release pin.** All three read the version and SRI hash from `data/agent-3d-releases.json` through a small build step, so a new release updates every embed at once.
+5. **Docs.** README per directory, an embed doc section per platform, `STRUCTURE.md` rows, changelog entry, submission text in `marketing/growth/submissions/site-builders.md` for owner order 938.
+
+## Definition of done
+
+- [ ] The WordPress block renders an agent in a local WordPress page, and Plugin Check passes (output in the report).
+- [ ] The Framer and Webflow components render an agent, verified in the real tool or, if no account exists, in the local harness each platform documents.
+- [ ] All three use the pinned release and hash from the ledger.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] READMEs, docs, `STRUCTURE.md`, changelog and submission text landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/094-partners-11-site-builder-embeds.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/095-partners-12-home-assistant-hacs.md b/prompts/finish/095-partners-12-home-assistant-hacs.md
new file mode 100644
index 000000000..f16a90a9f
--- /dev/null
+++ b/prompts/finish/095-partners-12-home-assistant-hacs.md
@@ -0,0 +1,62 @@
+# partners 12: Get the Home Assistant integration into the HACS default store
+
+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/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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
+
+[`home-assistant-integration/`](../../home-assistant-integration/) already holds a working custom integration with a `hacs.json`, a config flow and a manifest. HACS is how most Home Assistant users install custom integrations, and its default store lists a repository after a pull request to `hacs/default`, provided the repository passes HACS validation and hassfest in its own CI and has a brand icon in `home-assistant/brands`. The manifest points its issue tracker at a separate `three-ws-home-assistant` repository, so the integration needs a publishable standalone repository.
+
+## Step 0: re-derive the current state
+
+ cat home-assistant-integration/hacs.json
+ cat home-assistant-integration/custom_components/three_ws/manifest.json
+ ls home-assistant-integration/custom_components/three_ws
+ gh repo view nirholas/three-ws-home-assistant --json name,url 2>&1 | head -3
+
+Read the HACS publishing requirements (integration layout, `hacs.json`, releases, brands) and the `hacs/default` pull request rules on the day you run this.
+
+## Tasks
+
+1. **Validate locally.** Run hassfest and the HACS action's checks against the integration with docker (the same container images their GitHub Actions use), and fix every finding.
+2. **Manifest and metadata.** Correct `documentation`, `issue_tracker`, `codeowners` and `version`; make the `hacs.json` minimum Home Assistant version match what the code needs; add translations for the config flow.
+3. **Brand icon.** Produce `icon.png` and `[email protected]` (and dark variants) at the sizes `home-assistant/brands` requires, and write its pull request text.
+4. **A standalone repository export.** `scripts/export-hacs-repo.mjs` produces the exact tree the standalone repository needs (integration, README, LICENSE, `hacs.json`, and the two validation workflows that repository will run in its own CI). This repository does not use GitHub Actions, so those workflow files live only in the exported tree and the owner decides whether the standalone repository runs them.
+5. **Submission text** for `hacs/default` and `home-assistant/brands` in `marketing/growth/submissions/home-assistant.md`, for owner order 938.
+6. **Docs.** Update `home-assistant-integration/README.md` and the home docs page; changelog entry if anything user-visible changed.
+
+## Definition of done
+
+- [ ] hassfest and HACS validation pass locally against the exported tree (output in the report).
+- [ ] The integration installs into a local Home Assistant container through its config flow and receives a real event.
+- [ ] Brand icons exist at the required sizes.
+- [ ] `npm test` passes; `npm run audit:docs` reports nothing new.
+- [ ] The export script, submission text and docs landed.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| HACS needs CI in the standalone repository | The workflow files ship only inside the exported tree; creating that repository and turning them on is the owner's call in order 938. |
+
+## 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/095-partners-12-home-assistant-hacs.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/936-partners-13-tripo-reply-and-house-key.md b/prompts/finish/936-partners-13-tripo-reply-and-house-key.md
new file mode 100644
index 000000000..759d5b3f6
--- /dev/null
+++ b/prompts/finish/936-partners-13-tripo-reply-and-house-key.md
@@ -0,0 +1,63 @@
+# partners 13: Tripo reply, first call, and the house key (owner-gated)
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Blocked on owner actions; do everything the order assigns to the agent first.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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 is gated
+
+Sending the reply is posting to an external party, and putting a platform-paid `TRIPO_API_KEY` on the production service onboards a paid API. Both are the owner's call under CLAUDE.md. The agent's part is to make each of those a single step.
+
+## Why this matters
+
+Tripo reached out on 2026-10-09. The [brief](../../docs/partners/tripo.md) has the reply draft, the call questions and three deal shapes; order 084 builds the house lane behind the env var. This order carries the deal from reply to a live lane.
+
+## Step 0: re-derive the current state
+
+ sed -n '/## Reply draft/,/## Related/p' docs/partners/tripo.md
+ node scripts/read-service-env.mjs '^TRIPO' --names
+ ls prompts/finish | grep 084 || echo "084 done"
+
+Re-read the Tripo-family job counts from `forge_creations` for the last 30 days and update the brief's table if they moved.
+
+## Tasks
+
+1. **Refresh the brief** with today's numbers and anything Tripo has announced since 2026-10-09 (new models, pricing, the v3 endpoints).
+2. **Owner: send the reply** from the brief, copying `[email protected]` if the first contact came from elsewhere. Log it in the tracker row.
+3. **Owner: hold the call** with the six questions; the agent turns the owner's notes into the agreed deal shape in the brief.
+4. **Owner: approve the key.** Once terms are agreed, the owner sets it with `gcloud run services update three-ws-api --region us-central1 --update-env-vars TRIPO_API_KEY=...` (or as a Secret Manager reference, matching how the service holds every other credential). Never `--set-env-vars`.
+5. **After the key lands**: confirm Tripo jobs route as a house lane, run the reporting script from order 084 daily for the pilot, and draft the joint launch post in `marketing/growth/submissions/tripo-launch-post.md` for the owner to send.
+
+## Definition of done
+
+- [ ] Reply sent and logged in `marketing/growth/opportunities.csv`.
+- [ ] Deal shape recorded in the brief.
+- [ ] Key on the service, a production Tripo house-lane job completed, and the first pilot report produced.
+- [ ] Launch post drafted.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| Tripo has not answered in 12 days | Follow the cadence in [the outreach plan](../../docs/partners/outreach-plan.md#cadence-and-follow-up), then mark the row `no_reply`. Order 084's work stays useful to BYOK users either way. |
+
+## 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/936-partners-13-tripo-reply-and-house-key.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/937-partners-14-sponsorships.md b/prompts/finish/937-partners-14-sponsorships.md
new file mode 100644
index 000000000..d90222486
--- /dev/null
+++ b/prompts/finish/937-partners-14-sponsorships.md
@@ -0,0 +1,58 @@
+# partners 14: Sponsor the open source three.ws runs on (owner-gated)
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Blocked on owner actions; do everything the order assigns to the agent first.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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 is gated
+
+Every sponsorship is recurring spend, which only the owner can approve.
+
+## Why this matters
+
+The [outreach plan](../../docs/partners/outreach-plan.md) puts "Contribute" before every ask to an open-source project. Money is the fastest contribution and the one that most clearly says "we know we depend on you". The projects below are the ones three.ws uses most heavily in production, per the [prospects list](../../docs/partners/prospects.md).
+
+## Step 0: re-derive the current state
+
+ grep -n '"three"\|"@gltf-transform\|"@pixiv/three-vrm\|"meshoptimizer\|"@react-three' package.json
+
+For each project, read its sponsorship page today and record the tiers, what each tier gives the sponsor (logo, link, listing), and the payment route (GitHub Sponsors, Open Collective, Patreon, direct).
+
+## Tasks
+
+1. **Build the table** in `docs/partners/sponsorships.md`: project, what it powers in three.ws, tiers and prices read today, the tier recommended and why, and the recognition each tier gives. Start from: three.js, glTF-Transform, three-vrm (pixiv), meshoptimizer, Poly Haven, the Blender Development Fund, OrcaSlicer, Mesh2Motion, Quaternius and the pmndrs collective.
+2. **Recommend a monthly total** sized to the platform's current revenue and say how it was sized. Link it from the prospects and outreach pages.
+3. **Owner: approve and start** the sponsorships chosen.
+4. **After approval**: add each sponsored project's "sponsored by three.ws" status to the credits page (order 086) and send the one-line note from message template 2 in the outreach plan, owner-sent.
+
+## Definition of done
+
+- [ ] `docs/partners/sponsorships.md` exists with tiers read on the day, linked from the partner docs.
+- [ ] Owner decision recorded per project.
+- [ ] Each approved sponsorship is live and shown on the credits page.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/937-partners-14-sponsorships.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/938-partners-15-listings-prs-and-sends.md b/prompts/finish/938-partners-15-listings-prs-and-sends.md
new file mode 100644
index 000000000..bd5f8c898
--- /dev/null
+++ b/prompts/finish/938-partners-15-listings-prs-and-sends.md
@@ -0,0 +1,63 @@
+# partners 15: Open the pull requests, submit the listings, publish the packages, send the emails (owner-gated)
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Blocked on owner actions; do everything the order assigns to the agent first.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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 is gated
+
+Each item is a pull request, issue, form, listing, npm publish or email to a third party, all of which are external posting under CLAUDE.md. The runnable orders prepared every one of them as text in the repository; the owner sends them.
+
+## Why this matters
+
+Orders 085 to 095 each end with prepared submissions in `marketing/growth/submissions/`. This order is the owner's checklist for sending them, in the order that does the most good first, and the agent's job of keeping each one current on the day it goes out.
+
+## Step 0: re-derive the current state
+
+ ls marketing/growth/submissions/ marketing/growth/submissions/agent-registries/ 2>/dev/null
+ ls prompts/finish | grep -E "^0(8[4-9]|9[0-5])-partners" || echo "all runnable partners orders closed"
+
+For each submission file, re-check the intake route and any number it quotes on the day it is sent.
+
+## Tasks
+
+Send in this order, one tracker row per item, logging the outcome in `status` and `next_action`:
+
+1. **Agent registries** (order 093): npm publish of `packages/ai-sdk` and `packages/langchain`; the LangChain integration issue; Hermes, Kilo, OpenHands, OpenCode, Dify and cursor.directory entries; the Composio toolkit form; the GitHub MCP registry entry.
+2. **LiveKit and Pipecat** (order 087): the avatar plugin pull request to livekit/agents and the community-integration pull request to Pipecat's docs.
+3. **Home Assistant** (order 095): create the standalone repository from the export script, then the `home-assistant/brands` and `hacs/default` pull requests.
+4. **Slicers** (order 089): the PrusaSlicer trusted-hosts pull request and the Bambu Studio issue.
+5. **Site builders** (order 094): WordPress plugin directory, Framer marketplace, Webflow Apps.
+6. **Animation licensing** (order 085): the Adobe permission email, if order 085 kept anything that needs it.
+7. **Mocap landing** (order 090): announce it, and decide whether to name the closed services in outreach.
+
+## Definition of done
+
+- [ ] Every submission file has a tracker row with its sent date and outcome.
+- [ ] Merged or listed items are linked from the [prospects list](../../docs/partners/prospects.md) and, where the partner page's rules allow, [the partner page](../../docs/partners.md).
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/938-partners-15-listings-prs-and-sends.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/939-partners-16-program-applications.md b/prompts/finish/939-partners-16-program-applications.md
new file mode 100644
index 000000000..8458b4915
--- /dev/null
+++ b/prompts/finish/939-partners-16-program-applications.md
@@ -0,0 +1,63 @@
+# partners 16: Apply to the partner and startup programs (owner-gated)
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Blocked on owner actions; do everything the order assigns to the agent first.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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 is gated
+
+Each application creates an account or agreement in the owner's name, and some commit the platform to terms. Only the owner can do that.
+
+## Why this matters
+
+The [prospects list](../../docs/partners/prospects.md) found a set of programs that grant credits, listings or partner status to a platform like three.ws, several of which need a live integration first (built in orders 087 to 092). This order is the application checklist, with the answers drafted.
+
+## Step 0: re-derive the current state
+
+ ls marketing/growth/submissions/
+
+Re-read each program's page on the day: eligibility, deadline, what it grants, and the form fields. Microsoft's legacy route closes on 2026-10-31, so it goes first if it is still open.
+
+## Tasks
+
+1. **Draft every application** in `marketing/growth/submissions/programs/<program>.md` with each form field answered from verified facts and the proof brief:
+ - Microsoft (Copilot Studio and Microsoft 365 Copilot MCP certification, through Partner Center)
+ - LiveKit Startups, ElevenLabs startup grant, Deepgram startup program, Cloudflare for Startups
+ - Composio toolkit partnership, Meshy partner form
+ - VRoid Hub app approval (order 092), Shopify Partner and App Store review (order 091), Discord app verification and Activity Discovery (order 088)
+ - GitHub Technology Partner, JetBrains AI partner route
+ - Avaturn, Uthana and Rokoko partner or integration forms
+2. **Owner: submit** each, deadline first.
+3. **Log each** in the tracker and, when approved, wire what it grants (credits into the provider, listings into the partner docs).
+
+## Definition of done
+
+- [ ] One drafted application per program, each with the date its page was last read.
+- [ ] Each submitted application logged with its outcome.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+| A program page is gone or closed | Mark it in the prospects list's screened-out table with the date, and move on. |
+
+## 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/939-partners-16-program-applications.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/940-partners-17-sketchfab-retag.md b/prompts/finish/940-partners-17-sketchfab-retag.md
new file mode 100644
index 000000000..6a87e6f90
--- /dev/null
+++ b/prompts/finish/940-partners-17-sketchfab-retag.md
@@ -0,0 +1,59 @@
+# partners 17: Re-tag the Sketchfab models uploaded before the AI tag fix (owner-gated)
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Blocked on owner actions; do everything the order assigns to the agent first.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-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.
+- Never contact a third party: no email, issue, pull request, form, listing or post. Write the exact text into the repo and put the step in the owner message (context file rules).
+- Never onboard a paid API or spend. Wire paid vendors behind their env var and prove the code against the real API with whatever free or sandbox access exists.
+- Verify each upstream license from its LICENSE file before adopting anything.
+- 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 is gated
+
+Running the backfill edits public listings on a third-party platform under the platform's account, which is external posting.
+
+## Why this matters
+
+Sketchfab asks that AI-generated uploads carry its `createdwithai` tag. Since commit 919e54e82 (2026-10-09) every new upload does, but models uploaded earlier do not. Fab and Sketchfab are on the [prospects list](../../docs/partners/prospects.md), and an untagged back catalog is the first thing their team would notice.
+
+## Step 0: re-derive the current state
+
+ grep -n "createdwithai" api/_lib/sketchfab.js
+ sed -n 1,40p docs/sketchfab.md
+ node scripts/read-service-env.mjs '^SKETCHFAB' --names
+
+Count the platform's Sketchfab uploads made before 2026-10-09 from the database records the publish cron writes.
+
+## Tasks
+
+1. **The script.** `scripts/sketchfab-retag.mjs` lists every model the platform uploaded, adds `createdwithai` to those missing it without touching any other field, respects Sketchfab's rate limits, and is a dry run by default that prints exactly what it would change. `--apply` makes the changes.
+2. **Test** the request shape with a unit test, and run the dry run against the real API.
+3. **Owner: run** `node scripts/sketchfab-retag.mjs --apply`.
+4. **Docs.** A backfill note in [docs/sketchfab.md](../../docs/sketchfab.md).
+
+## Definition of done
+
+- [ ] Dry run output against the real API in the report.
+- [ ] After the owner runs `--apply`, a second dry run reports nothing to change.
+
+## 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`. If it exists nowhere, ship the feature wired behind the env var, prove it with a real call that the vendor answers (a documented auth error from their live API counts), and list the one missing variable in the owner message. |
+| A partner's docs or intake changed since 2026-10-09 | Build to what the page says today, and fix the row in [docs/partners/prospects.md](../../docs/partners/prospects.md) in the same commit. |
+| Upstream repo moved or changed license | Re-read the LICENSE file; if it is no longer permissive, switch to reference-only and build our own. |
+| A step needs a third-party account only the owner can create | Build and verify everything up to that step, write the exact sign-up and submission steps into the order's submission file, and put them in the owner message. |
+
+## 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/940-partners-17-sketchfab-retag.md`) and append a dated entry to [_context/partners-PROGRESS.md](_context/partners-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/partners-00-CONTEXT.md b/prompts/finish/_context/partners-00-CONTEXT.md
new file mode 100644
index 000000000..f16ec377d
--- /dev/null
+++ b/prompts/finish/_context/partners-00-CONTEXT.md
@@ -0,0 +1,90 @@
+# partners: shared context for every `partners-` work order
+
+Not a work order. Never run this file; read it when an order names it.
+
+## What the campaign is
+
+On 2026-10-09 Tripo reached out about a partnership, and the owner asked for a much longer list
+of partners and a plan to work it. Five research passes swept GitHub, npm and each company's own
+pages. The results are three documents, and every order in this campaign builds something one
+of them calls for:
+
+- [docs/partners/prospects.md](../../../docs/partners/prospects.md): the scored list, about 130
+ prospects in eight categories, with the "fix before we pitch" findings.
+- [docs/partners/outreach-plan.md](../../../docs/partners/outreach-plan.md): the waves, the
+ engagement ladder, the message templates and who does what.
+- [docs/partners/tripo.md](../../../docs/partners/tripo.md): the first prospect, worked in full.
+
+The split this campaign runs on: **agents build, the owner opens doors.** Every integration,
+package, page and pull request text is built and verified by an order in the 084 to 095 band.
+Every message sent, pull request opened on a third-party repository, form submitted, sponsorship
+paid and key approved is an owner action in the 936 to 940 band.
+
+## Rules (apply to every order)
+
+- **Never contact a third party.** No email, no issue, no pull request, no form, no listing
+ submission, no post. Write the exact text into the repo (the order says where) and add the
+ step to the owner message. CLAUDE.md gate 2.
+- **Never onboard a paid API.** An integration with a paid vendor ships wired behind its env var
+ and fully tested against the vendor's real API using a free or sandbox tier where one exists.
+ Putting a platform-paid key on the Cloud Run service is an owner action.
+- **Never spend.** Sponsorships, memberships, print orders and paid boosts are owner actions.
+ A real print order placed through a partner API is a spend.
+- **Partners are named.** Unlike the best3d campaign's commercial-vendor rule, partner prospects
+ are companies we are approaching openly, and they are already named in
+ [`api/_providers/`](../../../api/_providers/) and the partner docs. Direct competitors stay
+ unnamed, per the house rule.
+- **No other crypto project in a commit.** The CLAUDE.md commit gate holds: a diff that names a
+ crypto project other than $THREE needs the owner's yes first. This campaign deliberately
+ keeps on-chain partners out of its committed files.
+- **Licenses.** Re-read an upstream LICENSE file on the day you adopt anything:
+ `gh api repos/<owner>/<name>/contents/LICENSE --jq .content | base64 -d | head -30`.
+ CC0 assets need no permission but get credit anyway; that is the point of order 086.
+- **Re-verify before you build on a fact.** Intake routes and terms on the prospects page were
+ read on 2026-10-09 and rot fast. Re-read the page, and if it changed, fix the prospects row in
+ the same commit.
+
+## Facts every order relies on
+
+- The proof numbers (September 2026): 12,373 maker generation and rigging requests, 7,111
+ finished; 13,898 MCP tool calls at 99.4% handler success from 13 OAuth clients. Quote them
+ the way [the proof brief](../../../docs/partners/proof-brief-2026-10.md) says to.
+- Forge engines are registered in [`api/_lib/forge-tiers.js`](../../../api/_lib/forge-tiers.js);
+ vendor lanes live in [`api/_providers/`](../../../api/_providers/).
+- Print fulfillment is an adapter layer:
+ [`api/_lib/print/adapters/contract.js`](../../../api/_lib/print/adapters/contract.js), with
+ `manual` and `partner-cn` registered in `index.js`. A new print partner is a new adapter.
+- Avatar animation is universal (CLAUDE.md stack notes): a new rig convention is a bone-name
+ mapping in `src/glb-canonicalize.js` plus a test case, never a rig allowlist.
+- Production env lives on the Cloud Run service; read it with
+ `node scripts/read-service-env.mjs '^NAME$' --raw`.
+- We do not use GitHub Actions in this repository. Where a third party's intake requires an
+ Actions workflow in a separate public repository (HACS, n8n verified nodes), prepare it in
+ that repository's staged files and list the exception in the owner message.
+
+## Order map
+
+| Order | Item | Wave |
+|---|---|---|
+| 084 | Tripo v3 house lane, webhooks, and the endpoints we do not use yet | 0 |
+| 085 | Move the public animation library off Mixamo clips | 1 |
+| 086 | Open-source credits page and in-surface credits | 1 |
+| 087 | LiveKit avatar plugin and Pipecat avatar service | 2 |
+| 088 | Discord Activity | 2 |
+| 089 | "Get it printed" through Craftcloud, plus slicer trusted-host patches | 2 |
+| 090 | Mocap migration landing for stranded mocap users | 2 |
+| 091 | Shopify product-media app | 2 |
+| 092 | VRoid Hub import | 2 |
+| 093 | Agent tool packages and registry entries | 1 |
+| 094 | WordPress, Framer and Webflow embeds | 2 |
+| 095 | Home Assistant HACS package | 2 |
+| 936 to 940 | Owner-gated: Tripo reply and house key, sponsorships, third-party submissions, program applications, Sketchfab re-tagging | all |
+
+Run 085 and 086 first: they close the "fix before we pitch" findings. 084 runs any time. 093
+feeds 938. The rest are independent.
+
+Related campaigns, not duplicated here: best3d
+[072](../072-best3d-06-engine-bridges.md) (engine bridges),
+[075](../075-best3d-09-three-vrm.md) (three-vrm and VRM 0.x export),
+[934](../934-best3d-07-orphaned-avatar-campaign.md) (orphaned avatar users) and
+[935](../935-best3d-08-engine-store-publishing.md) (engine store publishing).
diff --git a/prompts/finish/_context/partners-PROGRESS.md b/prompts/finish/_context/partners-PROGRESS.md
new file mode 100644
index 000000000..64021d007
--- /dev/null
+++ b/prompts/finish/_context/partners-PROGRESS.md
@@ -0,0 +1,12 @@
+# partners: progress log
+
+Append a dated entry per closed order, with commit SHAs. Newest at the bottom.
+
+## 2026-10-09: campaign opened
+
+- Research and docs: [prospects](../../../docs/partners/prospects.md),
+ [outreach plan](../../../docs/partners/outreach-plan.md),
+ [Tripo brief](../../../docs/partners/tripo.md).
+- Fixed before writing the orders: VRM viewer copy named two apps that cannot load our avatars
+ (`e30e90c34`); Sketchfab uploads now carry Sketchfab's required Created With AI tag
+ (`919e54e82`).