Commit Graph
75 Commits
Author SHA1 Message Date
que01 88fcee94a0 test(junction): validate offset unequal core closure 2026-09-09 12:08:00 +08:00
que01 a22319a149 fix(junction): protect entry surfaces from exclusion regions 2026-09-09 12:01:16 +08:00
que01 9b6b5b5791 test(junction): keep facilities aligned with width edits 2026-09-09 11:58:53 +08:00
que01 b1fd54f0f8 feat(junction): expose entry transition feasibility 2026-09-09 11:47:05 +08:00
que01 e5d805a369 fix(junction): reject collapsed core boundary edges 2026-09-09 11:44:51 +08:00
que01 c4902cd4c8 test(junction): preserve identity across input reorder 2026-09-09 11:40:17 +08:00
que01 9ec99ed03e test(junction): enforce core boundary invariants 2026-09-09 11:39:03 +08:00
que01 234dd46f59 test(junction): cover six-arm rotation stability 2026-09-09 11:34:56 +08:00
que01 0e162d1f43 feat(junction): project sourced islands 2026-09-09 10:54:45 +08:00
que01 4e7274ec61 fix(junction): bound complex cutback transitions 2026-09-09 10:28:55 +08:00
que01 280b726c6f feat(junction): taper complex carriageway edits 2026-09-09 10:24:57 +08:00
que01 a98d170757 fix(junction): align complex crossing handles 2026-09-09 10:20:01 +08:00
que01 48fd432266 feat(junction): place sourced complex crossings 2026-09-09 10:15:33 +08:00
que01 d49cdab40a feat(junction): mark complex crossing evidence 2026-09-09 10:13:25 +08:00
que01 c14b8b09f2 feat(junction): publish sourced traffic islands 2026-09-09 10:05:43 +08:00
que01 3bf2edaf99 fix(junction): reject overlapping exclusion cores 2026-09-09 10:00:32 +08:00
que01 75bdfbe607 test(junction): cover known island exclusions 2026-09-09 09:57:14 +08:00
que01 b6f4dfeb0c fix(junction): omit unsupported corner facilities 2026-09-09 09:23:58 +08:00
que01 f56c0978b0 refactor(junction): keep edit metrics pure 2026-09-09 09:17:52 +08:00
que01 88d8b841e5 feat(junction): close verified complex cores 2026-09-09 09:15:58 +08:00
que01 b4abfdb870 feat(junction): derive complex approach boundary sections 2026-09-08 18:02:24 +08:00
que01 4de971ce68 fix(junction): align complex boundary trims 2026-09-08 17:57:03 +08:00
que01 a12e2ac823 feat(junction): share complex topology build plan 2026-09-08 17:47:35 +08:00
que01 855400fba2 fix(junction): keep complex carriageways connected 2026-09-08 17:16:51 +08:00
que01 53a2cb3450 fix(junction): make complex corner radius responsive 2026-09-08 17:06:05 +08:00
que01 36a8291c05 fix(junction): resolve complex handle preview roads 2026-09-08 16:16:59 +08:00
que01 49a44fdf73 feat(junction): edit complex crossing facilities 2026-09-08 15:05:00 +08:00
que01 80f122be46 feat(junction): edit complex cutbacks and corners 2026-09-08 14:30:43 +08:00
que01 c4bcbe8ff9 feat(junction): enable complex carriageway width editing 2026-09-08 12:09:44 +08:00
que01 0a5a229ce3 feat(junction): establish stable complex junction structure 2026-09-08 11:25:57 +08:00
que01 0065c3eaec feat(junction): project advanced facilities and associations 2026-09-07 17:12:29 +08:00
que01 63c6cefce7 feat(junction): enforce stage3 geometry validation on save 2026-09-07 15:47:34 +08:00
que01 fc7fe81eff feat(junction): expose stage1 structure and standards panel 2026-09-07 14:52:06 +08:00
que01 61cf276745 feat(junction): add structure and standards contract 2026-09-07 14:11:44 +08:00
que01 a359f88edc feat(junction): classify complex junction shapes 2026-09-07 10:52:12 +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 a78f5257fc test(junction): verify preview and compile parity 2026-09-03 13:32:37 +08:00
que01 b7d9a1973e test(workbench): cover junction workspace deep links 2026-09-03 12:35:45 +08:00
que01 f6f51fe90b feat(compile): expose effective junction plans 2026-09-03 11:44:26 +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 c804a373ca feat(workbench): unify lane maneuver edits in v2 2026-09-01 16:46:22 +08:00
que01 0318876e6a fix(compile): validate direct edit constraint ranges 2026-09-01 14:28:24 +08:00
que01 9cb715a592 feat: drag lane turn arrows along their lanes 2026-09-01 10:24:59 +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 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
que01andClaude Opus 5 479ffd00ed fix: publish the crosswalk inset ceiling that actually moves the zebra
Every junction-crosswalk-inset handle advertised max 8. Sweeping the real
response across eight groups, the ceiling ran 1.0 to 4.5 and varied per
approach, so 44-88% of the declared range moved nothing and returned no
diagnostic. Two approaches had a ceiling at or below the 1.5 default, meaning
dragging outward there did nothing at all — which is what made direct editing
look broken rather than limited.

crossingJunctionInset() stops responding once the inset reaches the cutback, and
sooner still when the crossing sits beyond the 4m cap, giving
cutback - max(0, junctionDistance - 4). Predicted ceilings matched all eight
measurements within the 0.5m sweep step, and the published max now matches them
8/8 where it used to be a flat 8.

The distance needs to know which crossing an approach serves, which lived only
inside compileControlMarkings(). crossing-approach.js now holds that rule at road
level, which is model-only and so usable from the solver. Behaviour is
unchanged: every lane of a road shares its junction distance, so the compiler's
(road, lane) ordering already grouped by road — fixtures confirm the geometry is
byte-identical.

Both directional roads of a segment can meet at one junction serving different
crossings; taking the first match published one road's ceiling on the other's
handle. The road that ends at this node wins, which is the same rule the client
uses to find the handle and the same one crossingJunctionInset() applies.

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