editor: add measurement tool

[sudhir9297]

What does this PR do?

Adds a registry-driven measurement tool for 2D and 3D editing, including distance, area, perimeter, and angle measurements; snap feedback and persisted measurement history; per-kind measurement definitions for built-in nodes; and consistent thinner measurement stroke styling across measurement overlays.

How to test

1. Run bun run lint and bun run check; both should complete without fixes.
2. Run bun run check-types and bun run build; both should complete successfully.
3. In the editor, choose the Measurement tool from Build tools and verify distance, area, perimeter, and angle measurements can be created in 2D/3D, snap to registry-provided node geometry, appear in the measurement history panel, and persist after save/reload.

Screenshots / screen recording

Not added yet — this is a visual/interactive measurement tool change.

Checklist

• I've tested this locally with bun dev
• My code follows the existing code style (run bun check to verify)
• I've updated relevant documentation (if applicable)
• This PR targets the main branch

---

Note

Medium Risk
Large editor/scene-graph feature with new node type and broad parent children schema updates; persistence and interaction paths need careful regression, but no auth or payment surface.

Overview
Introduces a registry-driven measurement system so editors can draw and persist length, area, perimeter, and angle readouts in 2D floorplan and 3D, instead of ad hoc dimension UI only.

Schema & core: New measurement nodes (MeasurementNode, attachments to geometry) can hang under levels, walls, slabs, stairs, cabinets, etc. NodeDefinition.measurement supplies snap anchors, direct length, area, and perimeter per node kind. The event bus and scene registry gain measurement events and a nodeIds reverse map so nested R3F picks resolve to the owning scene node.

Editor UX: Measure appears on the Build tab; the viewer menu adds a Measurements visibility toggle. A Measurement history panel controls mode, precision, chained measurements, snap kinds, and inline edits. MeasurementSceneGraphSync keeps the tool store and scene graph aligned for save/reload.

2D: FloorplanMeasurementToolLayer handles grid clicks, snapping (walls, roofs, MEP, intersections, guides), endpoint drag, hover previews, and zoom-stable HTML pill labels (shared with 3D styling via DimensionPillShell).

Misc: Group bbox helpers depend on meshEpoch without biome ignore comments; next.config adds allowedDevOrigins for 127.0.0.1.

^{Reviewed by Cursor Bugbot for commit ab131b0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Grid move clears hover previews

Medium Severity

Measurement hover previews for nodes (distance, area, perimeter) don't appear in 2D. The grid:move handler clears previewArea, previewPerimeter, and previewSegment at the start, immediately wiping any previews set by pointermove events.

 

^{Reviewed by Cursor Bugbot for commit 5d87835. Configure here.}

[cursor]

Collinear wall snaps zero angle

Medium Severity

When placing a 2D angle on a straight host (e.g. a wall), the second click can sit on the same ray as the reference leg. commitAngle then sets first and second to the same plan point, so angleBetweenMeasurements reports 0° instead of the corner angle users expect along that edge.

 

^{Reviewed by Cursor Bugbot for commit 5d87835. Configure here.}

[cursor]

Angle start ignores guide lines

Low Severity

Starting a 2D angle passes only target?.targetLine into beginAngle. Parallel and perpendicular snaps expose their geometry on guideLine, so the reference leg falls back to the generic grid axis instead of the host edge the snap indicator already highlights.

 

^{Reviewed by Cursor Bugbot for commit 5d87835. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 4 potential issues.

There are 7 total unresolved issues (including 3 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ab131b0. Configure here.}

[cursor]

Colinear angle collapses leg

Medium Severity

When committing an angle, if the second point falls on the reference line, referencePointForAngle can cause the first and second legs to align. This results in a degenerate 0° angle measurement, displaying an empty or misleading arc.

 

^{Reviewed by Cursor Bugbot for commit ab131b0. Configure here.}

[cursor]

Measurements dropped without field

High Severity

On load, editor state is restored only from sceneGraph.measurements, not from measurement nodes already in nodes. MeasurementSceneGraphSync then rebuilds scene nodes from an empty tool store and removes any persisted measurement_* entries, so saves missing the measurements field lose linear measurements silently.

 

^{Reviewed by Cursor Bugbot for commit ab131b0. Configure here.}

[cursor]

Orphan measurements at scene root

Medium Severity

Linear measurements without snap attachments get parentId: null and are appended to rootNodeIds. They are not parented under the active level or building, so the scene tree, outliner, and hierarchy-aware features can misplace or hide them compared to other level content.

 

^{Reviewed by Cursor Bugbot for commit ab131b0. Configure here.}

[cursor]

Unmount strips scene measurement nodes

Medium Severity

MeasurementSceneGraphSync runs syncLinearMeasurementSceneNodes([]) on unmount, removing every measurement node from useScene while useMeasurementTool segments are unchanged. Remounts restore them, but any autosave or UI that reads the scene graph between unmount and resync can persist or show a graph missing synced measurement nodes even though the measurements store still has data.

 

^{Reviewed by Cursor Bugbot for commit ab131b0. Configure here.}