MCP backend

Use when: Iterative source-of-truth alignment repair, choosing sequential vs parallel correction order, generating fit repair queues, stopping on contradictory templates, or coordinating geometry/UV/lighting fixes from validation reports.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Fit Repair Optimizer

This skill converts validation failures into an executable repair queue. The source templates are the contract; the current model is disposable.

Decision: sequential or parallel?

Use sequential repair when failures are coupled:

1. Canonical view / source conflict unresolved.
2. Front silhouette or part count fails.
3. Geometry dimensions fail before UVs can be trusted.
4. Texture region boundaries depend on geometry changes.
5. Lighting/look depends on final material placement.

Use parallel repair only for independent tracks with disjoint write scopes:

• geometry recipe/placement tuning;
• atlas-region classification;
• material/look calibration;
• validation tooling improvements.

Do not parallelize two tasks that both edit the same Blender recipe, object transforms, or UV assignment file.

Mandatory repair order

0 source-conflict / multiview-rigidity gate
1 structural part count
2 front silhouette and landmarks
3 side/back/top depth and projection
4 UV/texture region fit
5 material/light/look calibration
6 export and final validation

If an earlier stage fails, later stages may be analyzed but must not be finalized.

Source-conflict gate

Before repair, use multiview-constraint-solver to check whether templates are mutually satisfiable. If the same physical axis receives incompatible ratios across views, write a conflict report and require a canonical policy:

• front+side canonical;
• front+top canonical;
• corrected template sheet;
• view-specific cheat renders only, not a rigid 3D model.

Repair queue schema

Each repair item must include:

• id
• stage
• view_scope
• failure
• measured_delta
• proposed_action
• write_scope
• parallel_group
• blocked_by
• acceptance_gate

Skill-gap rule

If the same failure recurs twice, stop and invoke quality-refinement-autoloop before another rebuild. The autoloop must capture evidence, diagnose the missing method, sanitize the lesson into generic publishable guidance, patch the relevant skill(s), validate the skill stack, then return here with a new repair queue. Common routing:

• geometry mismatch → contour-to-mesh, orthographic-registration, or this skill;
• UV/texture mismatch → atlas-uv-fitting;
• lighting mismatch → add/look-calibrate guidance to blender-lighting or a look-calibration skill;
• validation mismatch → multiview-fit-loop / reference-analysis-validator.

Output

Write a project repair plan such as ALIGNMENT_REPAIR_QUEUE.json and a human-readable ALIGNMENT_REPAIR_METHOD.md.