Validate project device drop targets

docs/circuit-list-editor-interactions.md

@@ -57,6 +57,9 @@ Intent is separated by drag source type:
 - project device drag:
   - drop to section/placeholder -> create new circuit with linked row
   - drop to existing circuit row -> append row to that circuit
+  - lighting devices are accepted only by the lighting section
+  - other devices are accepted only by the section matching their phase type
+  - invalid targets show rejection feedback and do not create data
 - device row drag:
   - drop to existing circuit -> move row(s) into that circuit
   - drop to placeholder -> create new target circuit and move row(s)
@@ -68,6 +71,8 @@ Intent is separated by drag source type:
 - multi-circuit move:
   - supported for same-section selected circuit blocks
 
+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.
+
 ## Filtering and Sorting
 
 - Per-column filtering works on normalized displayed values.

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

@@ -8,4 +8,5 @@
 - 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.