feat: edit lane turn arrows in workbench

This commit is contained in:
que01 committed 2026-09-01 09:17:24 +08:00
1 parent 8b84166e6f
commit e48eb15827
9 files changed
+330 -28

No files matched your search

+13 -1
View File
@@ -140,6 +140,19 @@ match `main` exactly. Guard once at construction, not per call site.
while `compileGeometry()` ignores `profile.interval`. A control whose drag changes
nothing is worse than no control.
### V1 override selection is not direct edit
`lane-maneuver` is a saved v1 override for a discrete lane attribute, not a spatial
constraint. Its click selection and inspector selector are intentionally available
without `directEdit`: they stage `{ kind: 'lane-maneuver', laneId, maneuver }` and
wait for the existing save/recompile path. Do not route them through `EditSession`,
the preview endpoint, or a draggable element outline.
The distinction is observable: the ordinary workbench may select a turn-arrow part
or lane centerline and show this selector, while the `directEdit` flag still means
there are no edit sources, manifest requests, handles, ghosts, previews, or control
marking outlines.
---
## 10. Saving is not the same as applying
@@ -243,4 +256,3 @@ one. `handle.constraintId` — present only when a constraint exists — is also
- [ ] Every input channel meets at the shared exits, not a parallel path
- [ ] Displayed bounds round inward, so an offered extreme is accepted
- [ ] A focused field is not rewritten by an arriving preview