FA-88793 / Mesh topology invariants / Member archive

Edge split reports success when the edge is absent · case 03

Requests for a non-existent edge return the unchanged mesh with a new vertex id.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Input [faces, a, b] for a triangle mesh (any non-triangle returns "non-triangle"). Insert vertex m = max index + 1 on edge {a,b}: each triangle (u,w,c) with {u,w}={a,b} along its boundary becomes [u,m,c] then [m,w,c] at its original position. No such triangle returns "no-edge". Return [m, faces, number of split triangles].

Why this case matters

Mesh processing pipelines (remeshing, export, simulation, printing) trust these topological counts and adjacency answers; a wrong invariant silently accepts broken meshes or rejects valid ones.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
missing edge	`[4, [[0, 1, 2], [2, 1, 3]], 0]`	`"no-edge"`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.