Meshy asset production

Turn a governed reference pack into an auditable geometry candidate and texture child task. Read WORKFLOW.md before a provider transaction; it contains the established recipe and receipt requirements.

Before transacting

• Read the current coordination board, applicable plan, subject contract, prepared manifest and existing task receipts. Codex is the sole writer for Meshy credits and the proof ledger under the project ownership rules.
• Resolve existing user authorization, the applicable credit ceiling, spend already recorded and outstanding jobs. Continue authorized work without repeated permission questions. A skill request or old balance entry does not itself authorize spending; do not reuse another plan's allowance.
• Use the signed-in Meshy Chrome session through the available browser tools. Follow their current documentation; use supported upload/download mechanisms and preserve private visibility.
• Verify the four actual upload files and slot thumbnails against their hashes and directions. If pack preparation is missing, use game-art-reference-packs.
• Inspect the live settings and displayed charge. Treat the recipe as the project's recorded baseline, not a promise about current provider prices or UI labels. Record cosmetic label changes; resolve material cost, privacy, model or route changes against existing authority before submitting.

Generate and review