Polyweft 0.2: inspect what a clean mesh merge introduces

A clean Blender field merge can still create crossing surfaces. Polyweft 0.2 compares the same face pair in the ancestor, both edited branches and the configured result, using actual native Blender tessellation in each state.

Try the four-state inspection studio · Review the original Tide merge

• Exact intersection witnesses, face history and accepted vertex edits bound to source hashes and explicit choices.
• Recorded native triangles for quads and concave polygons. Changing a choice immediately disables stale inspection evidence while retaining decision export.
• Bounded work and explicit unknown/incomplete results. Shared-edge suppression requires a real boundary edge in both parent polygons.
• Original source-bearing Flanges bundle: 16 independent edits, zero competing values, separated inputs and 20 crossing face pairs in their combination. Its saved native output was freshly reopened and matched the inspected surface.

Install the wheel with Python 3.11+ and use your local Blender executable:

polyweft plan base.blend left.blend right.blend --output review --blender /path/to/blender
polyweft inspect review --output inspected --blender /path/to/blender
polyweft studio inspected --port 0

Add --decisions decisions.json to inspect a review with conflicts. The portable examples redact local paths; recapture a local plan from their native source files before inspecting or applying. Download SHA256SUMS.txt alongside the assets to check file integrity.

Verification: 32 Python tests, including actual native capture/save/reopen and HTTP boundaries, and 13 Node controls passed on Linux with official Blender 4.5.14 LTS under Python 3.11 and 3.14, and locally with a pinned Blender 5.3 Alpha build. Independent agent review compared 492 triangle pairs with a separate exact test, reproduced native tessellation cases and rechecked the corrected shared-diagonal regression. Actual browser choices were exported and applied by the installed package outside the checkout with fresh reopen and unchanged input bytes. Review was AI-assisted; it is not a separate human approval.

Inspection covers represented surfaces between distinct faces of the admitted target mesh. It does not establish containment, within-polygon distortion, other objects, evaluated modifiers, animation, physical clearance or safety. Prepared stable topology and trusted Blender/assets remain required. All data outside the admitted merge payload comes from the right branch. No dependency, account or cloud service is required at runtime beyond Python and local Blender.