Commit Graph
16 Commits
Author SHA1 Message Date
que01 a0bdd25c9d chore: record journal 2026-09-07 17:39:10 +08:00
que01 61ae90352a chore: record journal 2026-09-07 16:47:22 +08:00
que01 4519cad562 chore: record journal 2026-09-07 15:50:49 +08:00
que01 cb55b3ad68 chore: record journal 2026-09-07 15:24:47 +08:00
que01 b89c5fd174 chore: record journal 2026-09-07 14:56:16 +08:00
que01 0f804b71d1 chore: record journal 2026-09-07 14:23:11 +08:00
que01 39e338668b chore: record journal 2026-09-07 14:14:47 +08:00
que01 8d6f531377 chore: record journal 2026-09-07 10:58:40 +08:00
que01 5457f960ff chore: record lane maneuver workbench session 2026-09-01 09:21:58 +08:00
que01 b2da3b6866 chore: record journal 2026-08-28 17:45:38 +08:00
que01andClaude Opus 5 c7425f5ed4 feat: make crosswalk and stop-line offsets solvable
Step 1 of the control-marking task, and deliberately server-only: no handle is
drawn yet. This project already shipped a range handle for `profile.interval`,
which compileGeometry ignores, so the control dragged and changed nothing. The
consumer comes first now.

Two kinds join the taxonomy — `junction-crosswalk-inset` and
`junction-stop-line-offset`, both on the existing `junction-approach` anchor. The
solver writes them onto the approach entry, `applyDirectJunctionPlans` carries
them onto the compiled approach, and `compileControlMarkings` reads them in place
of the module constants it used for every junction. They move markings without
reshaping the junction, so unlike width and cutback they deliberately do not
trigger a boundary recompute.

`applyJunctionConstraint` becomes an explicit switch. Its trailing `else` had
meant every kind that was not approach-width fell through to the cutback
validator, so a new kind would have been silently validated and written as a
cutback. The same non-exhaustive shape in the test fixture's `valueFor` is fixed
the same way, and now throws for an unnamed kind rather than answering with a
corner radius.

design.md's taxonomy is updated with it — a test asserts the two cannot drift,
which is what caught the omission.

Measured on a 41-road workspace with 8 crossings: both constraints change their
marking geometry, neither drags the other, and out-of-range blocks instead of
clamping. That measurement is not in the suite: the synthetic junction resolves
`junction_inset_m` to 0 because its crossing never binds to a plan, and the
committed OSM fixture has no crossings at all. The tests assert the wiring the
handles will depend on — values reaching the approach entry, distinct branches,
blocking diagnostics — and the gap is recorded in the test itself.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-28 15:01:36 +08:00
que01 e25c564bb9 chore: record journal 2026-08-27 13:30:19 +08:00
que01 a26d4be666 docs: document direct edit solver and API contracts 2026-08-27 13:25:50 +08:00
que01 94e319c717 chore: record direct edit solving progress 2026-08-27 12:37:32 +08:00
que01 67e67e66bf chore: record direct edit manifest progress 2026-08-27 12:19:54 +08:00
que01 c5e762e1a9 chore: record journal 2026-08-27 09:06:40 +08:00