Record bounded placement clearance result and preserved quality regressions
This commit is contained in:
@@ -531,3 +531,18 @@ node interiors do not prove compatibility with our inflated obstacles and leads.
|
||||
Do not silently shorten those leads, move authored anchors, or persist external
|
||||
generated bends to make a comparison pass. Revisit engine integration only with
|
||||
a faithful geometry interface and observed usability benefit.
|
||||
|
||||
## Lead compatibility does not establish layout quality — 2026-09-25
|
||||
|
||||
The [bounded separation experiment](experiments/placement-clearance-20260925/results.md)
|
||||
at07405126 fixes the exact sparse mandatory-lead conflict by moving eight nodes
|
||||
down11 units. It removes NoClearPath and node penetration while preserving model
|
||||
records, anchors and repeated-call stability. Existing route-control output is
|
||||
byte-identical to released routing. However crossings20→22, shared length666→761
|
||||
and label/stroke intersections0→1 prevent a general readability improvement
|
||||
claim. Keep this flat-only repair isolated; do not connect it to production
|
||||
Arrange or increase its rounds to tune away the result. Use actual endpoint
|
||||
compatibility as a necessary placement constraint in a future initial coordinate
|
||||
assignment with connection ordering and corridor/label space. Compound geometry,
|
||||
automatic side changes and native tracing remain separate required evidence.
|
||||
This is branch-specific experimental evidence, not an integrated capability.
|
||||
|
||||
Reference in New Issue
Block a user