fix: require source evidence for complex crosswalks

This commit is contained in:
que01 committed 2026-09-11 11:24:19 +08:00
1 parent 858db529ae
commit 3a8af43140
9 files changed
+320 -53

No files matched your search

+13 -3
View File
@@ -331,9 +331,9 @@ then `structureFromTopology(topology, shape, center, features)`. Projection is
`cluster:<id>`. The legacy singular field is null at this unscoped entry point.
- `GET /api/edit-state?junction=<node>` preserves the node selection contract;
`?cluster=<id>` selects a cluster. Preview uses the equivalent `selection`
object. A selected editable cluster publishes its external carriageway and
corner handles plus `cluster-crossing-inset` and
`cluster-stop-line-offset` for each external arm crossing.
object. A selected editable cluster publishes its external carriageway,
corner, and stop-line handles. It publishes `cluster-crossing-inset` only for
an arm with a matching OSM crossing node.
- A cluster carriageway anchor contains `clusterId`, stable
`carriagewayKey`, `sourceNodeIds`, and `sourceRoadIds`. Replay matches all
source identity; a missing or changed source is stale with `anchor-missing`.
@@ -353,6 +353,16 @@ then `structureFromTopology(topology, shape, center, features)`. Projection is
generator applies the inset once per stripe group and positions each incoming
stop line relative to its matching crossing. Never identify these facilities
by `crossing_node_id`, because complex members can share a node.
- A road envelope or inferred stop line is not crossing evidence. Without a
matching source crossing node, compilation emits no complex crosswalk,
publishes no crossing-inset handle, records facility evidence as
`unknown-no-crossing-source`, and emits
`complex-junction-crossing-source-missing`. A stop line may remain as an
independent inferred facility; its position must not consume a nonexistent
crossing inset.
- Source matching uses the same inferred arm radius in handle publication and
constraint solving. A published handle must remain applicable at every
advertised value, including `value.max`.
- Preview and save both evaluate the same candidate through the resolver and
`compileGeometry()`. Save rejects every `severity: error` diagnostic before
writing the edit document.