API: tabPositions returns only entity references - no way to read positions of manually placed tabs (2D Contour)

[stefanUYMYK]

We run a production CNC operation (plywood nested sheets) and are automating our CAM setup through the API - now increasingly relevant with the new Fusion MCP connector enabling AI-driven workflows.

We rely entirely on manual tab placement (auto tab spacing doesn't meet our quality rules - placement depends on part shape, adjacency in the nest, and available anchor material). Automating this requires both reading and writing exact tab positions on 2D Contour operations, and we've hit a gap on the read side.

What works: Writing tabs at exact arbitrary positions works well — parameters.itemByName("tabPositions").value.value accepts SketchPoints (created in the setup model's root frame and passed as proxies in the setup's model context), and positions read back exactly. Thanks to the existing forum thread that documented the SketchPoint approach.

The gap: Tabs placed by clicking on a contour edge in the operation dialog are stored internally as edge reference + position-on-curve, but the API only exposes the edge reference. Concretely:

• Click 4 tabs at different points along one continuous 1240mm straight edge in the UI
• Read tabPositions via the API: you get 4 entries that are 4 identical BRepEdge references (same entityToken)
• The click positions are clearly retained internally — the dialog's Geometry tab displays the point markers and the generated toolpath places the tabs correctly — but there is no API access to the point or curve parameter for each entry

This makes it impossible to programmatically inspect, audit, migrate, or learn from existing manually-tabbed operations. Our current workaround is post-processing the operation and parsing NC output for mid-profile Z-lifts to recover tab XY positions, which is fragile and indirect.

Request: Expose the stored position for each tabPositions entry - e.g. return position data (Point3D and/or parameter-on-edge) alongside the entity reference, or provide a richer parameter value class for tab selections similar to how CadContours2dParameterValue exposes getCurveSelections().

Environment: Fusion (current), Windows, 2D Contour (contour2d), accessed both via Python API scripts and the Fusion MCP server.

Is there any existing way to get at this data that we've missed, and if not, can this be considered for the API roadmap?