Commit Graph
17 Commits
Author SHA1 Message Date
que01 a5089220b5 fix: align carriageway edge handles with entry geometry 2026-09-11 09:36:31 +08:00
que01 cd65dbe879 fix: share complex junction entry sections across layers 2026-09-09 17:23:17 +08:00
que01 49212b3f34 feat: measure junction shared seam errors 2026-09-09 17:09:41 +08:00
que01 79f83412e6 feat: complete complex junction transition editing 2026-09-09 16:57:47 +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 63c6cefce7 feat(junction): enforce stage3 geometry validation on save 2026-09-07 15:47:34 +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 0318876e6a fix(compile): validate direct edit constraint ranges 2026-09-01 14:28:24 +08:00
que01andClaude Opus 5 5c89d92041 docs: record the two-road ambiguity and the range contract
The directional-road trap cost two rounds in one session — once on the client,
once in the solver — and both times produced a plausible number attached to the
wrong object, which nothing but a segment with two of the thing will catch.

Also tabulates what measuring three handle ranges turned up: one rejects past a
third of its declared span, one goes silently inert over most of it, and one
would happily place a stop line 126m from the junction it protects. Each was
derived independently, and each was wrong in its own direction.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-31 15:17:01 +08:00
que01andClaude Opus 5 e08af11b7d docs: record the direct-edit client and side conventions
Three of this task's defects were cross-layer wiring rather than logic, so they
belong in the spec where the next session will read them, not only in the task's
research notes.

Frontend: a new client spec covering layer ownership (baseline is never written,
preview hides rather than overwrites), why a handle carries only its id, why a
handle's position must derive from the clamped value, the ban on computing inside
a setState updater, and why per-pointermove React state is the wrong owner of
per-frame feedback.

Backend: the left/right convention now states the three places that must agree
and why a sign convention can be wrong on both sides of the wire at once; a table
of the four profile fields the geometry stage actually reads, so nobody builds UI
for interval-scoped editing again before the compiler honours it; and the
save-is-not-applying contract, including that compileFresh must be installed by
every path that sets session.area.

Also records that an identity test cannot catch an ignored editsFile, and that a
regression test is only trustworthy once it has been seen to fail.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-28 10:27:04 +08:00
que01 a26d4be666 docs: document direct edit solver and API contracts 2026-08-27 13:25:50 +08:00
que01 ba8eaba9d9 feat: compile revisions from area config snapshots 2026-08-26 18:08:55 +08:00
que01 c0c8a16dd4 feat: add immutable road revision storage 2026-08-26 17:54:38 +08:00