Persist circuit structure edits

docs/spec/07-implementation-phases-todo.md

@@ -398,6 +398,9 @@ Implemented foundation:
   stack transition commit or roll back together
 - typed Circuit insert/delete commands treat the circuit and all device rows as
   one block, preserve every stable id and never renumber neighbouring circuits
+- standalone Circuit/CircuitDeviceRow insert/delete editor paths use those
+  commands with stable client-generated UUIDs and project-wide undo/redo; the
+  obsolete direct structure POST and CircuitDeviceRow DELETE routes are removed
 - typed CircuitDeviceRow move commands persist exact old/new circuit and sort
   positions for single or multi-row moves between existing circuits and derive
   affected reserve states in the same transaction
@@ -428,9 +431,9 @@ Implemented foundation:
   and rollback after a forced late persistence failure
 
 ProjectDevice CRUD, synchronization and disconnect on the project page and
-existing Circuit/CircuitDeviceRow cell edits in the circuit-list editor are
-connected to this history boundary. Remaining structural editor writes are not
-fully connected; the editor's visible undo/redo stack therefore remains
+Circuit/CircuitDeviceRow field/insert/delete actions in the circuit-list editor
+are connected to this history boundary. Move, reorder and renumber UI paths are
+not yet connected; the editor's visible undo/redo stack therefore remains
 session-local and is not reconstructed after reload.
 
 Acceptance criteria: