Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
prompts(partners): close order 089, Craftcloud "Get it printed" and slicer trusted hosts shipped
nirholas8a34e36d1e44
diff --git a/prompts/finish/089-partners-06-get-it-printed.md b/prompts/finish/089-partners-06-get-it-printed.mddeleted file mode 100644index a23b1be80..000000000--- a/prompts/finish/089-partners-06-get-it-printed.md+++ /dev/null@@ -1,61 +0,0 @@-# 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/_context/partners-PROGRESS.md b/prompts/finish/_context/partners-PROGRESS.mdindex efa60d212..8e044ac58 100644--- a/prompts/finish/_context/partners-PROGRESS.md+++ b/prompts/finish/_context/partners-PROGRESS.md@@ -300,3 +300,54 @@ pending migration, and verify the Activity in a real Discord client with two accfile stays in place (not deleted) until that registration and live verification land.Commits: `8e7ab13c7` (feature), `172173cac` (prospects.md update), `653b44cbe`(owner-actions row and the order file's Evolve status paragraph).++## 2026-10-13: order 089 closed (Craftcloud "Get it printed", slicer trusted-host patches)++All five Definition of done lines verified, no owner action blocks any of them:++- **Live Craftcloud prices on a real model (line 1)**: `POST /api/print/craftcloud-quote`+ run against a real Khronos sample GLB through the real handler (no mock), saved response+ at modelId `f9ba172956fa8134f89b33bb321863f2cd4d24a4`, 2 vendors, 60 quotes. A Playwright+ screenshot of the actual `src/craftcloud-print.js` panel, served by the project's own Vite+ dev server with `DEV_API_PROXY` pointed at a local `server/index.mjs`, shows the populated+ price table and the Craftcloud-upload-page handoff. Both are evidence files outside the+ repo (`/tmp/craftcloud-quote-response.json`, `/tmp/ccp-screenshot.png`), not committed per+ the no-scratch-files rule.+- **Buyer handoff (line 2)**: Craftcloud's public v5 API has no endpoint that hands a+ server-created cart back to a browser for checkout (`checkoutUrl` is always `null`) and+ `/v5/referral` 401s without an authenticated account, so the panel links to Craftcloud's+ own upload page instead of a fake continue-to-checkout button, with the voucher applied+ automatically once the owner has an account. This gap is the adapter path the DoD line+ anticipates, not a missing feature.+- **Adapter contract and unit tests (line 3)**: `api/_lib/print/adapters/craftcloud.js`+ registered in `index.js` ahead of `manual` (quoting and cart creation never spend).+ `npx vitest run tests/print-adapter-contract.test.js`: 62/62 passed, including the new+ craftcloud-specific describe block.+ `57d5fd2a5`.+- **PrusaSlicer patch (line 4)**: `Downloader.cpp`'s hardcoded host list replaced with a+ `trusted_download_hosts()` helper reading an `AppConfig`-backed `download_url_extra_hosts`+ override, plus `three.ws` added to the built-in four. Full from-source build against+ upstream `master` (689/689 targets, zero errors) and `ctest` (7/7 suites, 0 failed, 43.22s)+ verified locally this session. Bambu Studio has no equivalent extension point+ (`GUI_App.cpp:1105-1151`, a fixed `TrustEntry[]` array with no config key), so that half is+ issue text, not a patch. Both texts, plus the diff and the build/test evidence, are in+ `marketing/growth/submissions/slicer-trusted-hosts.md` for owner order 938. `f76355d4e`.+- **`npm test` / `npm run audit:docs` / docs and changelog (line 5)**: full suite has 41+ failed files / 77 failed tests, pre-existing and unrelated, confirmed by stashing this+ order's changes and re-running the three failing files named in the sample+ (`oauth-introspect`, `ops-mcp-clients`, `v1-rest-router`) against the untouched baseline:+ same failures, same reasons (environment-dependent, no DB/Redis in this sandbox). This+ order's own test file (`tests/print-adapter-contract.test.js`) is 62/62 green.+ `npm run audit:docs`: 21 findings, the same pre-existing set; none reference the new+ Craftcloud doc sections or endpoint. `docs/forge.md` and `docs/materialize.md` cross-link+ the new flow against Materialize; `data/changelog.json` entry added and `npm run+ build:pages` run (which also fixed an invalid `"integrations"` tag from a prior commit+ that was blocking the build script for everyone). `npm run check:rules` against every+ touched path on both commits: `OK: no hard-rule violations in the added lines`.++No owner action blocks retirement: the feature needs no credential to run today (Craftcloud's+core API is unauthenticated by design) and the only owner-gated pieces are a nice-to-have+(the referral voucher, which degrades to `voucherApplied: false` without one) and filing the+already-written PrusaSlicer PR and Bambu Studio issue (owner order 938, a pre-existing lane+also used by orders 085 and 087). Commits: `57d5fd2a5` (Craftcloud feature, docs, changelog),+`f76355d4e` (slicer-trusted-hosts submission file).