Record accepted routing evidence and remaining release work

harness/TASK_LEDGER.md

@@ -1,6 +1,6 @@
 # Task Ledger — first release
 
-Authoritative objective: attachment07aee762-7d27-4cbe-81c3-2e82c7170711/goal-objective.md, read fully on2026-09-05. STATE.md records execution evidence; PLAN.md is the living strategy; DECISIONS.md and linked release contracts retain detailed rationale.
+Authoritative objective: attachment `07aee762-7d27-4cbe-81c3-2e82c7170711/goal-objective.md`, read fully on 2026-09-05. STATE.md records execution evidence; PLAN.md is the living strategy; DECISIONS.md and linked release contracts retain detailed rationale.
 
 ## Goal and success criteria
 
@@ -18,32 +18,34 @@ System engineers can develop a coherent OA→SA system model, including iterativ
 
 - Native Capella SAB authoring creates function input/output endpoints with an FE. Component ports separately carry Standard/Flow kind, orientation, interface roles and explicit allocated function ports. Details and successfully performed versus merely observed operations are in release-capella-workflow-benchmark.md.
 - Studio uses one typed Project and validated atomic commands across Rust core/desktop/server. Hierarchy projection distinguishes actual allocation from inferred parent summaries; IDs and placement are separate.
-- Drag selection bug fixed and committed2ef16dc;71desktop tests and real moved-card selection/property editing passed before typed-port integration.
-- Typed ports/schema3 migration merged757ab88. Existing port identities survive as Legacy and missing FE endpoints are generated deterministically; current migration and port tests provide scoped evidence in release-port-core.md/release-port-migration.md.
-- Independent core review reproduced alias reservation and same-transaction allocation replacement defects; fixes have focused regression evidence. Desktop port integration has passing focused event/form tests; full checks and native acceptance are still pending.
+- Drag selection bug fixed and committed `2ef16dc`; 71 desktop tests and real moved-card selection/property editing passed before typed-port integration.
+- Typed ports/schema 3 migration merged at `757ab88`. Existing port identities survive as Legacy and missing FE endpoints are generated deterministically; migration and port tests provide scoped evidence in release-port-core.md/release-port-migration.md.
+- Independent core review reproduced alias reservation and same-transaction allocation replacement defects; fixes have focused regression evidence. Typed desktop integration `fa096ce` passed full checks and native creation/generation, undo/redo, save/reopen and no-op synchronization trials. Long-reference previews were inspected at 1440×900 and 1100×700; detailed evidence is in STATE.md.
+- Per-diagram pins and labels, source/API parity and shared orthogonal routing are implemented in `4e5a88d`, `a7c6f96`, `68b1eff` and `30c7db1`. `65fa9ab` resolves all six reproduced default SA label-overlap pairs. Native OA/SA editing, movement/undo, fold restoration, save/reopen, SVG inspection and short gestures at 1100×700 passed. Routing code/native acceptance and independent native follow-up are complete at `23535b4`; exact scope is recorded in release-routing-verification.md.
+- The source experiment passed 23 tests, but an independent probe reproduced positional item-comment misattachment, shorthand description rejection and unsupported deletion. Whole-model equality does not establish source-comment fidelity. The production updater retained comment attachment on the same reorder probe; extend its parser/updater instead of copying the experimental parallel implementation.
 - Current behavior diagrams derive geometry and only handle selection. Text editing currently flattens the accepted model. These remain product gaps regardless of underlying semantic coverage.
 
 ## Assumptions to test
 
 - Aggregate-oriented source files will reduce cognitive load enough for routine engineering edits; file splitting alone may leave declaration syntax too flat.
 - Behavior layout can reuse NodePlacement plus typed diagram context without duplicating semantic state; reconnection/reordering must preserve existing occurrence/relation identities.
-- Editable per-diagram bends plus an automatic initial route can resolve realistic crossings; an automatic layout cannot guarantee an ideal readable arrangement for arbitrary models. Test manual control, nesting, ports and persisted/exported route parity.
+- Editable per-diagram bends and the automatic initial route passed the recorded workshop trials. This does not guarantee an ideal arrangement or zero crossings for arbitrary models; the measured dense release full solve is 119 ms, above the initial 100 ms target.
 - Source comments and ownership can survive graphical edits by replacing only changed declaration spans. Generated IDs must stabilize before subsequent text edits.
 
 ## Open questions
 
-- Which combination of file organization, nesting syntax and navigation best supports realistic text-only engineering tasks? Independent candidate comparison is active.
-- Can an engineer discover and complete typed exchange/allocation and legacy resolution workflows with acceptable effort at minimum window size? Native acceptance is pending after physical Escape.
+- Which selected nesting/shorthand constructs justify production parser/updater extension while preserving comment attachment, exact source Undo, complete editing and clear diagnostics? The independent source probe provides concrete acceptance cases.
 - What remaining OA/SA gaps materially block target workflows? R3 semantic reconciliation, R6 data contracts, directly editable behavior, lifecycle/recovery and hosted editing remain in the release plan.
 
 ## Candidate designs and current decisions
 
-- Source candidate A: retain explicit source3 declarations in semantic aggregate files with includes. Candidate B: nested owner/context syntax lowering to the same model. Candidate C: independent critic to propose a materially different alternative. Rank on domain clarity, task effort, identity/roundtrip safety, Git locality and grammar/implementation complexity. Current pure bundle implementation is a testable foundation, not proof that A alone satisfies usability.
+- Source candidates compared explicit source3 aggregate files/includes with nested owner/context syntax lowering to the same model. The chosen implementation direction extends the production parser/span index and shared updater for selected constructs, preserving the pure bundle foundation. Do not copy the experiment's separate parser/writer. Freeze grammar only after comment ownership, edit/delete coverage, invalid drafts and exact source Undo pass their acceptance tasks.
 - Behavior alternatives: independent UI-only coordinates, new behavior-layout schema, or existing diagram placements with explicit context. Prefer the last candidate provisionally: it preserves text/API parity and command history without a second geometry system. Validate on direct state-machine creation/move/reconnect before extending all behavior views.
 - Ports: adopted typed separation based on official metamodel plus direct native evidence; rejected generic InOut/interface port conflation and inferred allocation facts. See release-port-contract.md. Revisit only with contradictory domain evidence or concrete usability failures.
+- Routing: a unique per-diagram route list references existing relation/trace IDs; pinned points and relative label placement are persisted, while orthogonal segments are derived by a shared pure router. This avoids duplicate semantic edge identities and preserves text/API/SVG parity. Folded endpoint promotion suspends custom geometry without deleting it. See release-routing-contract.md.
 
 ## Current strategy and evaluators
 
-Finish and independently review typed-port desktop integration; require creation/generation/split/undo/reopen invariants and native trials. In parallel, test pure source-bundle compilation/updates and independently evaluate text representations using representative engineering tasks. Then integrate per-file source editing, safe project saves and REST bundles against the selected design. Prototype persisted direct behavior gestures next. Continue remaining release semantics and cross-disciplinary acceptance; no subsystem checkpoint constitutes release completion.
+Extend production source parsing/updating using the independent probe findings as regressions; integrate per-file editing, safe project saves, exact source Undo and REST bundles. Independent current WSL tests, strict Clippy and release builds are in progress; Linux success is not yet claimed. Prototype persisted direct behavior gestures next. Continue R3 reconciliation, R6 data contracts, lifecycle/recovery, hosted editing, offline guidance and fresh Windows/Linux release acceptance; no subsystem checkpoint constitutes release completion.
 
-Meaningful progress now: committed drag fix and native evidence, integrated typed core contracts, reproduced/fixed transaction defects, passing focused authoring tests, and a concrete source experiment. Highest uncertainty is source/behavior usability; more feature enumeration without task evidence would be a poor proxy.
+Meaningful progress now includes verified drag and typed-port authoring, accepted editable routing with native save/reopen, group movement and minimum-size evidence, and tested source-bundle/nested-writeback foundations with independent limitations exposed. Production source and direct behavior usability remain open engineering tasks; feature counts alone do not establish completion.