Commit Graph
123 Commits
Author SHA1 Message Date
que01 38ea779d9b feat: add complex junction selection markers 2026-09-04 17:09:32 +08:00
que01 57248f1aa4 chore(task): archive direct edit junction tools 2026-09-04 14:52:20 +08:00
que01 1f439d98de fix(workbench): show junction traffic signals 2026-09-04 14:23:27 +08:00
que01 f10a5da325 feat(workbench): stabilize junction tools workspace 2026-09-04 09:46:19 +08:00
que01 e6b822416d fix(workbench): keep map visible in junction tools 2026-09-03 14:04:13 +08:00
que01 c9d9e45f48 fix(workbench): clarify junction browse mode 2026-09-03 13:54:26 +08:00
que01 39d7453ebc chore(tasks): archive completed edit workflows 2026-09-03 13:34:25 +08:00
que01 a78f5257fc test(junction): verify preview and compile parity 2026-09-03 13:32:37 +08:00
que01 3811790dc8 fix(workbench): persist junction workspace edits 2026-09-03 12:39:01 +08:00
que01 b7d9a1973e test(workbench): cover junction workspace deep links 2026-09-03 12:35:45 +08:00
que01 8c99bb7340 docs(tasks): plan junction tools delivery 2026-09-03 12:28:47 +08:00
que01 6a0736517f chore(task): record junction facilities progress 2026-09-03 12:13:01 +08:00
que01 ecfa391eea feat(workbench): summarize junction facilities and diagnostics 2026-09-03 12:07:50 +08:00
que01 1bd1fd712f chore(task): record junction geometry progress 2026-09-03 12:02:48 +08:00
que01 60e28f6b7a feat(workbench): expose junction geometry parameters 2026-09-03 12:02:16 +08:00
que01 f6f51fe90b feat(compile): expose effective junction plans 2026-09-03 11:44:26 +08:00
que01 4b38ce3c31 fix(workbench): require explicit junction draft exit 2026-09-03 11:28:49 +08:00
que01 c59fb704ef chore(task): archive 09-02-junction-tools-workspace 2026-09-03 11:24:23 +08:00
que01 2504e8342f feat(workbench): add junction tools workspace shell 2026-09-03 11:20:37 +08:00
que01 96833d3a63 chore(task): archive 09-02-junction-detection-hotspot 2026-09-03 11:13:45 +08:00
que01 7d9b0f46d4 feat(workbench): add junction hotspot entry points 2026-09-03 11:12:22 +08:00
que01 bd7b049930 chore(task): archive 09-02-junction-requirements-research 2026-09-03 11:05:03 +08:00
que01 6b75d273e7 chore(task): archive 09-01-lane-maneuver-position-drag 2026-09-03 09:51:14 +08:00
que01 15be3480ed chore(task): archive workbench-component-boundaries 2026-09-03 09:50:01 +08:00
que01 58f59c8a45 test(workbench): verify exported package contract 2026-09-02 17:52:54 +08:00
que01 fcb07b8396 test(workbench): add browser regression coverage 2026-09-02 17:39:25 +08:00
que01 2fb9db65e5 test(workbench): lock cross-domain edit history 2026-09-02 16:57:36 +08:00
que01 bb6c51c489 fix(workbench): preserve cross-domain undo order 2026-09-02 16:41:12 +08:00
que01 31552a5b6f feat(workbench): drag control markings as elements 2026-09-02 16:04:38 +08:00
que01 834470cfa1 refactor(workbench): split editor state and components 2026-09-02 15:04:58 +08:00
que01 caa3cb843f feat(workbench): add traffic signal rotation handle 2026-09-02 11:38:30 +08:00
que01 9b7c3d59bd feat(workbench): stage traffic signal edits 2026-09-02 09:30:03 +08:00
que01 9c83392b97 feat(workbench): drag traffic signal assemblies 2026-09-02 09:05:56 +08:00
que01 cf5bc0602b feat(workbench): improve traffic signal editing 2026-09-02 09:04:56 +08:00
que01 00d5f7650f refactor(workbench): use persistent mode switch 2026-09-01 17:20:16 +08:00
que01 c804a373ca feat(workbench): unify lane maneuver edits in v2 2026-09-01 16:46:22 +08:00
que01 118dc8e9aa fix(workbench): preview lane arrow drag 2026-09-01 15:04:11 +08:00
que01 fe73d993a9 fix(workbench): preview staged lane arrow overrides 2026-09-01 14:46:22 +08:00
que01 0318876e6a fix(compile): validate direct edit constraint ranges 2026-09-01 14:28:24 +08:00
que01 bb108267e3 feat(workbench): organize map editing panels 2026-09-01 13:47:30 +08:00
que01 6d80597642 feat(workbench): preview and drag lane turn arrows 2026-09-01 11:47:35 +08:00
que01 9cb715a592 feat: drag lane turn arrows along their lanes 2026-09-01 10:24:59 +08:00
que01 5457f960ff chore: record lane maneuver workbench session 2026-09-01 09:21:58 +08:00
que01 3d135761e7 fix: outline selected turn arrows 2026-09-01 09:21:24 +08:00
que01 2415733597 chore(task): archive lane maneuver override 2026-09-01 09:17:57 +08:00
que01 e48eb15827 feat: edit lane turn arrows in workbench 2026-09-01 09:17:24 +08:00
que01andClaude Opus 5 8b84166e6f chore(task): record lane-maneuver delivery and the UI prerequisite
All seven criteria pass against a live area. Notes what a UI would need first:
turn arrows group by lane plus maneuver, a two-field key, where crosswalks and
stop lines group by a single property — so the element registry's groupProperty
has to become composable before arrows can join it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 18:02:27 +08:00
que01andClaude Opus 5 335c8ea68a feat: override which turn arrow a lane shows
The arrow on a lane came from the OSM turn:lanes tag with no way to change it,
and a lane the tag skipped got no arrow at all. lane-maneuver is a v1 override
that sets it.

v1 rather than a v2 constraint, because "which arrow" is a discrete attribute of
a lane with no station to anchor to, while every v2 anchor is positional. The
existing road override already covers OSM-derived values this way — laneCount,
width, sidewalks — and this is the same kind of thing. Arrow *placement* is the
positional half and stays out; it also still has an open question about whether
a group is a lane or a single arrow.

Three behaviours, each measured against compiled output: an override replaces
the tag's maneuver, it adds arrows to a lane the tag never marked, and '' removes
one the tag asked for. The empty string is therefore distinguished from "no
override" rather than falling through to the tag. An empty override set leaves
the arrows byte-identical and the fixtures untouched.

Validation lists the accepted maneuvers and rejects anything else, including
correctly-spelled components in the wrong order. It cannot be left to
normalizeManeuver(), which returns unrecognised input unchanged — a typo would
otherwise reach the template lookup and silently produce no arrow.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 18:00:53 +08:00
que01andClaude Opus 5 15d41be444 chore(task): record progress and the blocker on corner grips
Steps 1, 2 and 4 are done and step 3 is parked with a reason: the client never
reads affects and no highlighting exists, so fixing it alone changes nothing a
user can see. It belongs with the highlight, as one piece of work.

Step 5 has a design question that should be settled before code. The size value
is a pair while the drag path is scalar end to end, so a corner grip moving one
component has to preserve the other or every drag resets the half it did not
touch. Three options noted, with the reason the tempting one — letting element
controls build their own value — is the wrong shape.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 17:12:57 +08:00
que01andClaude Opus 5 f3924caa5c feat: make crosswalk size a constraint the geometry stage reads
Every zebra was six stripes at 3m by 0.45m on a 0.9m pitch, all literals. Depth
and stripe count are now a constraint, junction-crosswalk-size, and the loop
reads them.

The span across the road stays derived rather than stored: it is count times
pitch, and pitch is fixed because stripe and gap widths are standardised while
the road they cross is not. Widening a crossing means adding stripes, which is
what a real one does, and it is why the span quantises in 0.9m steps.

That also fixes a span pinned at 4.95m regardless of the street. Measured, every
crossing sat on a 6.50m carriageway and covered under four fifths of it. The
default now follows the segment width — both directions, since a crossing spans
the carriageway — giving eight stripes and 6.74m, reaching the kerb rather than
stopping short. Fixture baselines move for exactly two entries on the one area
with crossings; the area without them is untouched.

No handle is published yet. design.md requires proving compileGeometry() consumes
a parameter before any grip is drawn — the rule left over from profile.interval
shipping a handle that did nothing — so the grips come next, on a value already
known to work.

Adding the kind made the client's exhaustive scalar switch fail to compile, which
is the check working: size is a pair and has no dragged-scalar form, so that case
now says so and throws rather than writing half a value.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 17:10:45 +08:00