Record verified Arrange reset workflow and evidence
This commit is contained in:
@@ -498,3 +498,26 @@ editing remains separate from semantic reconnect. The [decision and evidence
|
||||
map](edge-attachments-20260922.md) records alternatives, lifecycle rules,
|
||||
independent falsifiers, evaluators and the Process/Scenario applicability limits.
|
||||
This is branch-specific work; it does not establish an integrated release.
|
||||
|
||||
## Explicit Arrange resets visible authored geometry — 2026-09-25
|
||||
|
||||
Branch-specific candidate for issue #32, based on released715036e; not an integrated
|
||||
release checkpoint. Explicit Layout clears pins and the complete label override
|
||||
for existing projected routes whose displayed owners equal their actual placed
|
||||
owners. Freeze that eligibility before geometry changes, including at the operation's
|
||||
position in a Batch. Preserve route entries, order, attachments and semantic/manual
|
||||
port choices. Preserve existing equal-actual-owner translation for ineligible
|
||||
routes and retain ordinary movement behavior. Keep whole Reset routing distinct.
|
||||
|
||||
This narrowly amends the former pin-preserving Layout contract so an explicit
|
||||
arrangement can recover automatic route/label placement without deleting endpoint
|
||||
choices. Clearing the whole label record avoids retaining a stale authored fraction;
|
||||
it does not guarantee better geometry. The routing and node-placement algorithms
|
||||
remain unchanged. More aggressive experimental routing candidates were not adopted
|
||||
because independent scenes exposed tradeoffs and regressions.
|
||||
|
||||
[Results and evidence](experiments/arrange-reset-20260925/results.md) bind the
|
||||
contract, source/history tests, strict Clippy and expanded/folded native save/reopen
|
||||
acceptance to their actual code pins. Residual crossing/layout quality and viewport/
|
||||
guide discoverability remain outside this bounded acceptance. Gitea owns live
|
||||
publication and integration status; this record does not close issue #32.
|
||||
|
||||
Reference in New Issue
Block a user