Add project device sync history

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

@@ -192,18 +192,21 @@ 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
+- `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
 
 Remaining constraints before completing persistent history:
 
 - extend the concrete project-scoped command union and executors beyond the
   Circuit field/insert/delete and CircuitDeviceRow
-  field/insert/delete/move plus section-reorder/renumber slices; the generic
-  versioned command envelope is complete
-- route the remaining structural, synchronization and destructive domain
+  field/insert/delete/move, section-reorder/renumber and ProjectDevice row-sync
+  slices; the generic versioned command envelope 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, destructive and synchronization
-  operations
+  command coverage is complete for structural and destructive operations; then
+  route the existing synchronization UI through its persistent command
 - do not model IFCGUID as an overloaded circuit equipment identifier
 - keep database backup/restore checks separate from project history tests