leeway-triposr
Governed single-image-to-3D reconstruction provider skill for the existing LeeWay TripoSR runtime. Produces a reconstruction candidate mesh that must be inspected/normalized and may flow into 3D Engin
SKILL.mdskills/leeway-triposr/SKILL.md
GitHubLeeWay TripoSR
Existing LeeWay runtime evidence
Historical ecosystem evidence identifies triposr-studio / leeway-triposr-tool, with containers leeway-triposr-backend and leeway-triposr-web. Recorded host publication was backend 18000→8000 and web 13000→3000. The former machine path is retained only as provenance in config/image-to-3d-refinement-pipeline.json. Discover the authorized current image-to-3D adapter and endpoint; no former drive, container name or port is a universal prerequisite.
Purpose
TripoSR is the rapid reconstruction provider for single-image → candidate 3D mesh. It does not own engineering dimensions, blueprint constraints, Blender scene authority, or final verification.
Canonical weave
reference image → image preparation/mask as required → TripoSR reconstruction → candidate mesh/artifact → geometry inspection → scale/orientation normalization → 3D Engineering Blueprint constraints/measurements when engineering intent exists → Blender refinement/materials/topology/lighting/scene → render/measurement verification → export → receipt.
One-shot behavior
For creative one-shot image-to-3D work, TripoSR may produce the initial mesh directly from one image. Because unseen surfaces are inferred, treat backside/occluded geometry as reconstruction hypothesis until inspected. Never promote one-view reconstruction to dimensionally accurate engineering geometry without measurements/reference constraints.
Output expectations
Capture when available: source-image hash/reference, model/runtime version, reconstruction parameters, mesh format/path/hash, texture mode/resolution, vertex/face counts, runtime duration, CPU/GPU/VRAM evidence, errors, and receipt identity.
Blender handoff
Before Blender refinement record coordinate system, units/scale status, orientation, material/texture status, mesh validity and known reconstruction uncertainties. Blender may repair topology, remesh, UV/material, light, rig, animate, scene-compose and export. Blender success does not erase TripoSR uncertainty.
Provider resilience
TripoSR is one provider for IMAGE_TO_3D_RECONSTRUCTION. Newer providers such as Stable Fast 3D or SPAR3D may be qualified later behind the same abstract capability; do not replace the existing runtime without evidence and explicit promotion.
Live qualification
PRESENT/configured historical evidence != live. Before claiming live TripoSR: rediscover container identity, image, health endpoint/API contract, published ports, model availability, inference result, output artifact and receipt.