chore(task): correct the elementId premise and split the first gate

Measured rather than assumed: grouping the 48 stripes by crossing_node_id yields
exactly 8 groups of 6, and no crossing maps to more than one road. The uniqueness
is structural — compileControlMarkings() iterates model.crossings and each pass
emits one group from one candidate — so crosswalk:node/<crossingId> is already a
stable group id and needs no compiler change.

The earlier claim that no group id existed conflated the crossing node
(node/-26452, the pedestrian crossing) with the junction node (node/1140799725).
Different ids. Grouping client-side therefore reads a published identifier rather
than clustering by proximity, which is what the PRD forbids.

The missing affects entries are real and unchanged, but they only degrade
drag highlighting; they do not block selection. The two are now separate steps,
and selection moves first because it costs nothing on the server.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
que01andClaude Opus 5 committed 2026-08-31 13:13:09 +08:00
1 parent 086939be93
commit 623481fd2c
3 files changed
+43 -31

No files matched your search

@@ -3,7 +3,7 @@
"name": "crosswalk-element-editor",
"title": "斑马线元素级编辑器实验",
"description": "",
"status": "planning",
"status": "in_progress",
"dev_type": null,
"scope": null,
"package": null,