que01
d94c546450
Saving wrote the v2 document but nothing else, and `/api/state` serves the outputs of the last compile — so a refresh showed the pre-edit geometry and a successful save was indistinguishable from a failed one. Reported as "saved, refreshed, edit gone"; the document on disk was in fact correct, resolving as `exact` with the constraint reaching the profile. Save now recompiles and clears the preview overlay, since the baseline carries the edit afterwards and would otherwise draw it twice. The recompile is reported separately from the save: if it fails the message says the edit was saved and names the compile error, rather than claiming the save failed. The existing identity test could not have caught this. An ignored `editsFile` and an empty document produce the same output, so it proved nothing about a non-empty one. The API test now compiles with and without a saved constraint and asserts the outputs differ. 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.