Context
Phase 536 closed the bounded lasso screenshot proof route and Cookbook evidence. The parity roadmap still lists lasso toolbar UX and public activation ergonomics as the next React Flow whiteboard/lasso follow-up.
Current lasso support is source-backed through NodeCanvas.SelectionMode, NodeCanvasSelectionMode.Lasso, transient feedback, and the Phase 536 screenshot proof route. Activation is still mainly a host/API toggle rather than an ergonomic hosted authoring surface.
Scope
Add a bounded toolbar/public activation ergonomics slice for lasso mode that stays on existing editor/Avalonia seams:
- expose an ergonomic hosted authoring control path for switching between marquee and lasso selection where the current workbench already projects selection/layout tooling;
- keep the public activation surface tied to
NodeCanvas.SelectionMode / NodeCanvasSelectionMode.Lasso without inventing a new selection state model;
- add focused editor/Avalonia/Demo tests proving the hosted control projects and activates lasso mode predictably;
- update EN/ZH parity and Cookbook docs with the exact Phase 537 boundary.
Out of scope
No eraser behavior, no rectangle/freehand drawing primitives, no persistence, no renderer rewrite, no strict pixel baseline enforcement, no retained API removal, no full whiteboard parity, and no broad visual redesign.
Acceptance Criteria
- A tracker-backed implementation or docs-supported route exists for lasso toolbar UX/public activation ergonomics.
- Focused tests prove lasso activation remains backed by
NodeCanvas.SelectionMode / NodeCanvasSelectionMode.Lasso and does not create a parallel selection model.
- Demo/Cookbook or hosted authoring docs surface the ergonomic route with source-backed anchors.
- EN/ZH parity docs record Phase 537 with this GitHub issue and the Bead ID.
- Next Issue Wave removes Phase 537 as TBD while preserving Phase 538-540.
- Tests/docs explicitly retain the boundaries: no eraser, no drawing primitives, no persistence, no renderer rewrite, no strict pixel baselines, no retained API removal, and no full whiteboard parity.
Dependencies
Follows Phase 536 / GitHub #195 / avalonia-node-map-uvd. Avoid overlapping with Phase 538+ if they touch pointer-mode state or toolbar wording.
Context
Phase 536 closed the bounded lasso screenshot proof route and Cookbook evidence. The parity roadmap still lists lasso toolbar UX and public activation ergonomics as the next React Flow whiteboard/lasso follow-up.
Current lasso support is source-backed through
NodeCanvas.SelectionMode,NodeCanvasSelectionMode.Lasso, transient feedback, and the Phase 536 screenshot proof route. Activation is still mainly a host/API toggle rather than an ergonomic hosted authoring surface.Scope
Add a bounded toolbar/public activation ergonomics slice for lasso mode that stays on existing editor/Avalonia seams:
NodeCanvas.SelectionMode/NodeCanvasSelectionMode.Lassowithout inventing a new selection state model;Out of scope
No eraser behavior, no rectangle/freehand drawing primitives, no persistence, no renderer rewrite, no strict pixel baseline enforcement, no retained API removal, no full whiteboard parity, and no broad visual redesign.
Acceptance Criteria
NodeCanvas.SelectionMode/NodeCanvasSelectionMode.Lassoand does not create a parallel selection model.Dependencies
Follows Phase 536 / GitHub #195 /
avalonia-node-map-uvd. Avoid overlapping with Phase 538+ if they touch pointer-mode state or toolbar wording.