Currently, clicking a segment on the canvas only changes its action type (pass, run, kick, etc.). However, if the auto-segmenter completely misses a direction change or creates a phantom split, there's no way for the operator to fix the boundary. Because users can't edit boundaries, we also can't collect feedback on where segment breaks should actually occur.
Suggested fix:
Add a canvas handle or hotkey (e.g., Shift-click a point or drag a boundary handle) to split or merge existing segments.
Trigger a recommit on the chain after editing.
Log boundary edits as a new correction type in the feedback DB.
Definition of Done:
An operator can split or merge segments on the canvas, the chain updates correctly, and the boundary edit is logged.
Currently, clicking a segment on the canvas only changes its action type (pass, run, kick, etc.). However, if the auto-segmenter completely misses a direction change or creates a phantom split, there's no way for the operator to fix the boundary. Because users can't edit boundaries, we also can't collect feedback on where segment breaks should actually occur.
Suggested fix:
Add a canvas handle or hotkey (e.g., Shift-click a point or drag a boundary handle) to split or merge existing segments.
Trigger a recommit on the chain after editing.
Log boundary edits as a new correction type in the feedback DB.
Definition of Done:
An operator can split or merge segments on the canvas, the chain updates correctly, and the boundary edit is logged.