fix(eval): resolve cross "topmost" via the order matrix, not array position #25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The spec resolves a
crossintersection on stacked layers to "the material point on the topmost layer". The implementation takes the last preimage in face-array iteration order (eval.ml:63) — butfold_state.ml:5states that array index carries no z-meaning and all stacking lives inorder. This only works today because of the deliberately preserved legacy append order plusflipreversing the array.The moment a fold inserts a face between existing layers (pocket slice),
crosssilently returns the wrong material point. The covering faces pairwise overlap at the point, so their restriction oforderis total and "topmost" is well-defined — consult the order matrix instead.Must land before the pocket slice.