Persist section renumbering

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

@@ -207,6 +207,9 @@ Completed foundation:
 - `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
+- the editor's explicit renumber action uses this command; obsolete direct
+  renumber and identifier-restore routes plus their transaction adapter are
+  removed
 - `project-device.sync-rows` records synchronization, disconnect and reconnect
   as one atomic multi-row operation; complete expected/target sync snapshots
   protect local values, links and override metadata against silent stale writes
@@ -218,11 +221,9 @@ Completed foundation:
 
 Remaining constraints before completing persistent history:
 
-- 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
+  CircuitDeviceRow operations plus ProjectDevice operations already use
+  persistent commands and project-wide undo
 - extend project-scoped commands only when further project mutations are
   deliberately added to history; the generic versioned envelope is complete
 - do not model IFCGUID as an overloaded circuit equipment identifier