fix(compile): validate direct edit constraint ranges
This commit is contained in:
1 parent
bb108267e3
commit
0318876e6a
7 files changed
+238
-11
No files matched your search
@@ -40,6 +40,10 @@ POST /api/revisions/:id/rebase
|
||||
- `POST /api/revisions/:id/rebase` is read-only and returns status counts plus
|
||||
per-constraint details. `pending`, `conflicted`, and `stale` constraints do
|
||||
not enter geometry solving.
|
||||
- A resolved constraint whose saved numeric value no longer fits the current
|
||||
geometry range is returned as `stale` with reason `range-out-of-bounds`.
|
||||
A missing replay anchor uses reason `anchor-missing`; callers must not infer
|
||||
the stale cause from the status alone.
|
||||
|
||||
## 4. Validation & Error Matrix
|
||||
|
||||
@@ -53,6 +57,7 @@ POST /api/revisions/:id/rebase
|
||||
| Solver replay anchor cannot resolve | Mark `stale` or `conflicted` with diagnostic; never silently apply |
|
||||
| Compiler geometry version differs | Mark all replayable constraints `recheck` without changing values |
|
||||
| Invariant violation (lane width, crossing boundaries, self-intersection, connector bounds) | Return a blocking diagnostic; do not clamp or silently repair |
|
||||
| Constraint value outside the current handle range | Return a blocking diagnostic; do not clamp or silently repair |
|
||||
|
||||
## 5. Good / Base / Bad Cases
|
||||
|
||||
|
||||
Reference in new issue
Block a user