Persist circuit reorders

docs/project-history-and-external-model-architecture.md

@@ -200,6 +200,10 @@ Completed foundation:
 - `circuit.reorder-section` requires the complete section circuit set and
   stores exact expected/target sort positions; its inverse changes no
   equipment identifier and never splits a circuit block
+- `circuit.reorder-sections` applies the same invariants to every affected
+  section from a sorted view in one transaction and one history entry
+- circuit drag-and-drop and sorted-order application use these commands; the
+  obsolete direct reorder route and transaction method are removed
 - `circuit.renumber-section` is the separate explicit renumber operation; it
   stores every expected/target equipment identifier, uses collision-safe
   temporary values and restores the exact prior identifiers on undo
@@ -214,8 +218,8 @@ Completed foundation:
 
 Remaining constraints before completing persistent history:
 
-- route the remaining reorder and renumber editor writes through their existing
-  typed persistent commands and remove the final direct mutation routes
+- route the remaining renumber editor writes through its existing typed
+  persistent command and remove the final direct mutation routes
 - reconstruct the visible frontend history state after reload; Circuit and
   CircuitDeviceRow field/insert/delete actions plus ProjectDevice operations
   already use persistent commands and project-wide undo