Confirm cross-section device moves

docs/circuit-list-editor-interactions.md

@@ -73,6 +73,8 @@ Intent is separated by drag source type:
 - device row drag:
   - drop to existing circuit -> move row(s) into that circuit
   - drop to placeholder -> create new target circuit and move row(s)
+  - crossing a section boundary requires explicit confirmation
+  - phase type, category, linked project device and local row values remain unchanged
 - circuit drag (BMK handle):
   - reorder circuits inside same section only
   - cross-section reorder is rejected
@@ -83,6 +85,8 @@ Intent is separated by drag source type:
 
 The sidebar insertion controls use the same project-device placement rules as drag-and-drop. Invalid section and circuit options are disabled after selecting a project device.
 
+Cross-section device moves show confirmation-required feedback before drop. The confirmation names source and target sections and warns that the unchanged device classification may need manual review. Cancelling leaves every row and circuit unchanged. Moving never renumbers existing circuits.
+
 ## Filtering and Sorting
 
 - Per-column filtering works on normalized displayed values.

docs/circuit-list-editor-known-limitations.md

@@ -8,5 +8,4 @@
 - Bulk device-row move flow is command-based but not fully transaction-hardened end-to-end across all affected circuits.
 - Sorting is view-only until users explicitly apply sorted order.
 - Cross-section circuit drag-reorder is intentionally blocked.
-- Existing device rows can currently be moved across sections without the planned classification confirmation dialog.
 - Legacy consumer and circuit-first paths coexist; migration is transitional and still requires operational discipline.