feat: add canonical road movements

.trellis/tasks/08-13-native-road-compiler/design.md

@@ -52,6 +52,13 @@ override IDs, and diagnostics. Junction candidates likewise use their OSM node
 ID when available. Values include provenance such as `tag:lanes:forward`,
 `inferred:highway-default`, or `override:<id>`.
 
+Each `Movement` is a stable semantic record joining a connection, source and
+target road/lane, turn class, provenance, and an optional connector geometry.
+`geometryStatus="connector"` publishes a connector curve;
+`geometryStatus="continuous"` means the lane centerlines meet at the node and
+does not invent a zero-length curve; `deferred-too-long` retains the movement
+while withholding unsafe geometry.
+
 ### Override file
 
 `<area>/native-road-overrides.json` is versioned and human-reviewable. It
@@ -62,7 +69,8 @@ existence, finite values, and duplicate/conflicting edits before atomic write.
 
 ### Compiler artifacts
 
-`<area>/native-road/compiled.json` is the workbench's single read model.
+`<area>/native-road/compiled.json` is the workbench's single read model and
+contains the canonical `movements` list.
 `layers/` contains generated GeoJSON with source/provenance properties.
 `diagnostics.json` contains severity, stable subject ID, source IDs, rule,
 message, and optional geometry. `comparison.json` reports counts and coverage
@@ -71,10 +79,12 @@ visual differences.
 
 ## Browser Workbench
 
-The browser uses no framework or map runtime in v1. A Canvas/SVG map renders
-fit-to-data OSM centerlines, native surfaces, optional osm2streets reference
-layers, diagnostics, selected-object provenance, and overrides. This keeps the
-first interactive path dependency-free and permits precise local coordinates.
+The browser uses OpenLayers as its sole GIS runtime, served directly from the
+local allowlisted `node_modules` packages with a browser import map. The map
+renders fit-to-data OSM centerlines, native surfaces, optional osm2streets
+reference layers, diagnostics, selected-object provenance, movements, and
+overrides. This provides mature map selection and hit detection without a
+framework or bundler.
 
 The user can select a road or endpoint, edit only v1 fields, inspect the
 resulting override record, explicitly save it, and recompile/reload. Saved

.trellis/tasks/08-13-native-road-compiler/research/two-area-comparison.md

@@ -0,0 +1,50 @@
+# Two-Area Native Road Comparison
+
+## Runs
+
+2026-08-14:
+
+```bash
+npm run road:compile -- --config config/areas/nantaizi-lake-innovation-valley.json
+npm run build:area -- --config config/areas/hanyang-block.json --stages intermediates
+npm run road:compile -- --config config/areas/hanyang-block.json
+```
+
+`comparison.json` is a coverage and diagnostic record. Feature counts are not
+a geometry-quality score: osm2streets and the native compiler segment roads at
+different levels.
+
+| Area | Directional roads | Native surfaces | Native junctions | Movements | Internal ends | Manual candidates | osm2streets road surfaces |
+| --- | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
+| nantaizi-lake-innovation-valley | 34 | 19 | 6 | 46 | 4 | 2 | 50 |
+| hanyang-block | 475 | 352 | 20 | 369 | 161 | 83 | 1826 |
+
+## Observed Failure Modes
+
+The hanyang osm2streets/QGIS run completed, but its log reported repeated:
+
+- roads trimmed into oblivion;
+- degenerate intersections that could not be collapsed because layers, names,
+  highway types, or lane specifications differ;
+- intersection polygon requests with no roads.
+
+The native compiler did not hide the related uncertainty. It reported 161
+internal road ends. Eighty-three have one or more nearby, direction-compatible
+candidate departures within 35 metres; these remain suggestions for explicit
+review rather than automatic topology edits. The initial five one-way junctions
+that lacked connector curves now publish road-surface envelopes based on their
+semantic movements. Across hanyang, 369 movements are identified: 243 require
+a connector curve, while 126 are continuous at their OSM node and intentionally
+have no separate geometry.
+
+## Resulting Priorities
+
+1. Keep manual candidate suggestions and semantic overrides as the correction
+   path for near-miss topology. Do not bulk-connect candidates.
+2. Expand ordinary junction support from 3/4 physical approaches only after
+   identifying a repeated unsupported topology; one-way movements that are
+   continuous at a node are already supported without fake connector geometry.
+3. Add an inspectable movement artifact so turn geometry is not the only
+   representation of a road-to-road movement.
+4. Use a visual review of a few explicit hanyang diagnostics before changing
+   connection-distance or road-class rules.