Reimplement transformation, handle Meta Nodes interrupting vertex grouping

[webdevred]

This update improves the way jbeam_edit processes meta nodes (such as {"group":"..."}) that interrupt vertex groupings within .jbeam files. Previously, encountering these meta nodes resulted in an explicit error message indicating unsupported input, preventing further processing.

Key changes:

• Extract all vertices from sections interrupted by meta nodes.
• Sort vertices within their respective groups while preserving the original order relative to meta nodes.
• Move and reinsert vertices back into their original nodes, maintaining file structure integrity.
• Enhance logic to gracefully handle meta nodes interrupting vertex lists.

Example of the previous grouping logic being broken by meta nodes:

{"group": "group1"}
["fr0", -0.426, -2.084, 0.235]
["fr1", 0.487, -2.072, 0.235]
{"group": "group2"}
["fr2", -0.418, -2.034, 0.300]

With this update, jbeam_edit properly handles such cases by treating meta nodes as separators, allowing vertices to be grouped and sorted correctly within their respective groups.

[webdevred]

VertexTree Transformation Roadmap

This roadmap outlines the transition from the existing VertexTree transformation logic to a more robust and flexible system. The goal is to support meta node handling, group-aware vertex positioning, and future extensibility.

---

Before

This update improves the way jbeam_edit processes meta nodes (such as {"group":"..."}) that interrupt vertex groupings within .jbeam files.
Previously, encountering these meta nodes resulted in an explicit error message indicating unsupported input, preventing further processing.
There was no support for grouping metadata and vertices together, no logic for relocating misplaced vertices, and renaming strategies were minimal and fragile.

After: New Transformation Logic

The transformation proceeds through several clearly defined stages:

1. Input & Parsing

• Input: A VertexTree structure, derived from .nodes data.
• Parsing steps:
  • getVertexTree: Flattens the top-level node structure into a list of VertexTreeEntry.
  • nodesListToTree: Rebuilds the hierarchical VertexTree from this flat list.
  • updateVertices: Entry point for renaming and movement.

2. Name & Group Preparation

• vertexNames: Collects all unique vertex names.
• Comment groups:
  • Vertices are grouped with surrounding comment/meta nodes into CommentGroups:

    data CommentGroup = CommentGroup
      { cComments :: [VertexTreeEntry]
      , cVertex :: Vertex
      }

  • Each group may have 0 or more comment/meta entries and exactly one vertex.
  • Comments and metadata are preserved and follow the vertex throughout the transformation.

3. Filtering & Movement

• filterVerticesToMove: Identifies vertices needing relocation, based on their type or context.
• Decision point:
  • If all vertices are in the correct location: skip movement, proceed to renaming.
  • If not, perform:
    • Type comparison between vertex and parent tree.
    • Relocation using type rules and spatial (X-axis) hints.
    • Tree restructuring where needed (new subtrees created).
    • Zipper-based tree traversal (to be implemented later).
    • All associated meta/comment nodes move along with the vertex.

4. Renaming & Updating

• Vertices within groups are sorted consistently.
• New names are assigned based on group and position.
• A vertexNameMap is created: mapping old → new names.
• Tree and .nodes entries are updated using this map:
  • Replaces names in VertexTree.
  • Updates references in metadata.
• ungroupCommentGroups: Reassembles the final structure with comments preserved.

5. Final Output

• A valid VertexTree with:
  • All misplaced vertices corrected.
  • Updated names.
  • Group/meta structure intact.
• Order is preserved unless a new tree is explicitly created.
• Users can expect:
  • Clean grouping.
  • Predictable naming.
  • Structural consistency.

After Merging

To be implemented in future PRs:

• Indent JBFL property to specify number of spaces for indentation.
• Detect support vertices (nodes with many beam connections) and group them automatically.
• Allow prefix replacement via CLI (e.g., replace bf in node/beam names).