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>
26 lines
595 B
JSON
26 lines
595 B
JSON
{
|
|
"id": "crosswalk-element-editor",
|
|
"name": "crosswalk-element-editor",
|
|
"title": "斑马线元素级编辑器实验",
|
|
"description": "",
|
|
"status": "in_progress",
|
|
"dev_type": null,
|
|
"scope": null,
|
|
"package": null,
|
|
"priority": "P2",
|
|
"creator": "dingkang",
|
|
"assignee": "dingkang",
|
|
"createdAt": "2026-08-28",
|
|
"completedAt": null,
|
|
"branch": null,
|
|
"base_branch": "main",
|
|
"worktree_path": null,
|
|
"commit": null,
|
|
"pr_url": null,
|
|
"subtasks": [],
|
|
"children": [],
|
|
"parent": "08-26-direct-manipulation-road-editor",
|
|
"relatedFiles": [],
|
|
"notes": "",
|
|
"meta": {}
|
|
} |