Persist circuit cell edits

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

@@ -173,6 +173,11 @@ Completed foundation:
   to SQLite
 - public command, undo and redo endpoints require an expected revision; undo
   and redo reconstruct the eligible persisted inverse or forward command
+- the circuit tree returns the project's current revision; existing Circuit
+  and CircuitDeviceRow cell edits use the public command endpoint, while their
+  toolbar undo/redo actions use project-wide persistent history
+- obsolete direct Circuit and CircuitDeviceRow field-update PATCH routes are
+  removed so these editor writes cannot bypass revision history
 - `circuit-device-row.insert` and `circuit-device-row.delete` preserve stable
   row ids, complete deleted-row snapshots and circuit reserve state through
   atomic insert/delete, revision and stack transitions
@@ -210,10 +215,10 @@ Remaining constraints before completing persistent history:
   is complete
 - route the remaining structural and destructive domain
   writes through the shared command, revision and stack transaction boundary
-- replace the session-local frontend command stack only after server-side
-  command coverage is complete for structural and destructive circuit-editor
-  operations; the ProjectDevice synchronization UI already uses its persistent
-  command and project-wide undo endpoint
+- finish routing structural and destructive circuit-editor operations through
+  persistent commands, then reconstruct the visible frontend history state
+  after reload; Circuit/CircuitDeviceRow cell edits and ProjectDevice
+  synchronization already use persistent commands and project-wide undo
 - do not model IFCGUID as an overloaded circuit equipment identifier
 - keep database backup/restore checks separate from project history tests