4b70b0221def72a9a46211a21cef42ca58531345
Sweeping the declared [0, 8] range and measuring where the group actually lands: 0 to 3.2 tracks one-to-one, and 3.2 to 8 does not move at all. No diagnostic, no feedback — roughly 60% of the advertised range is inert. crossingJunctionInset() drives it. targetDistance bottoms out once inset reaches the approach's cutback, and a 4m cap sits above that, so the real ceiling varies per approach while the manifest publishes a flat 8 for all of them. This is worse than the edge-offset case already on file. That one refuses and says so; this one silently does nothing, which is indistinguishable from a broken control — the exact failure the interval flag exists to prevent, occurring in the upper half of a range rather than across a whole handle. A user whose first drag lands in the dead zone concludes direct editing does not work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Road Compiler
Compiles a native-road-package/v1 RoadCompilerInput JSON file into native-road GeoJSON, diagnostics, traffic-signal runtime assets, and a deterministic completion marker.
npx road-compiler --input /absolute/path/road-compiler.input.json
The compiler does not read host area configuration. The caller owns configuration normalization and creates the input JSON. Successful compilation writes exactly one NATIVE_ROAD_COMPILE_DONE JSON marker to stdout.
Run npm test after npm ci to validate the package and its two self-contained area fixtures without the host repository. The migrated baselines remain upgrade corpus; the host repository owns the strict path-normalized parity gate.
Languages
JavaScript
47.8%
Python
25.3%
TypeScript
25%
CSS
1.3%
HTML
0.6%