323ff9279f895f63198a2ea01326a974218f9a6e
Measured the grouping of every marking layer. Stop lines are nearly free — same feature builder, same key shape, an existing constraint kind, and a sweep shows the offset tracks one-to-one across its whole range with no dead zone. Arrows are not: neither kind exists and neither is read by the geometry stage. The trap is that crosswalks and stop lines share crossing_node_id on all eight groups, so grouping has to branch on provenance before touching the key or the two merge into one element. That is already how element.ts works and a test holds it. What the data earns is a provenance-keyed registry and nothing more: group keys are single-field, two-field and derived; group sizes run 1 to 230; two element types have no constraint at all. A universal element protocol would be inventing past the evidence, which the PRD rules out. Also records delivery state — steps 1 and 2 done, 3 through 5 not started — so the task is not mistaken for complete. 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%