feat: add tripo3d as third 3d provider

[mvanhorn]

Summary

image-blast-3d now accepts --provider tripo, with Tripo3D running on FAL alongside the existing Meshy and Hunyuan adapters.

Why this matters

Image-blaster's per-object 3D layer already exposes a multi-provider switch (Meshy and Hunyuan). Tripo3D is the third top-tier image-to-3D engine and the one with the highest demo-video traction in 2026 by view count. Its hand-surface and cartoon-illustration models are well-regarded in the comparison literature, and it's available on FAL with the same queue + result shape the existing adapters already use.

Source	Evidence
Tripo3D v2.5 image-to-3D on FAL	endpoint exists, queue-based, returns model_mesh.url (.glb)
Tripo 3.1 demo	446K views, production-ready 3D from a single image
Hunyuan vs Meshy vs Tripo head-to-head	Tripo named top tier alongside the two providers already supported
ideate.xyz Trellis vs Tripo vs Meshy vs Rodin vs Hunyuan	comparative review of the same five engines

Demo

Simulated demo (HyperFrames):

Changes

• tripo-3d.mjs mirrors meshy-3d.mjs exactly: queue submit through fal-queue.mjs, response download through fal-3d-provider.mjs, indexed .N-<object>-request.json provenance unchanged
• generate-single-asset.mjs gains tripo aliases in MODEL_PROVIDER_ALIASES, a tripo branch in run3DProvider, a Tripo branch in modelRequestPrefix, and Tripo CLI flags (--texture, --pbr, --face-limit, --quad, --auto-size, --texture-alignment, --orientation)
• Skill + agent + README updated to advertise --provider tripo alongside the existing options

Tripo endpoint: tripo3d/tripo/v2.5/image-to-3d. Defaults: texture: "standard", pbr: true, face_limit: 30000, quad: false.

Testing

• node --check passes on tripo-3d.mjs and generate-single-asset.mjs
• Provider abstraction follows the same shape as the existing Meshy adapter; no API call was made from this PR (would require FAL credits + a test image)

AI was used for assistance.