Keep Revit and manual row quantities consistent

Editing "Anzahl" on a row with linked Revit objects set manualQuantity to
the new total, so the row no longer matched its objects and detaching
them failed with "row.manualQuantity must not exceed row.quantity".

Such rows now lock "Anzahl" in the editor. The new optional columns
"Anz. manuell" (editable) and "Anz. Revit" (read-only) show both shares;
stored column layouts get them hidden next to "Anzahl". The device-row
update derives the total from a manual-only edit and rejects any change
that breaks quantity = manual + Revit, for every source. Two history
fixtures inserted rows with quantity 1 and the column default
manualQuantity 0, a state no runtime path creates; they now insert 1/1.

Undoing "Revit-Objekte lösen" re-validated planning-value conflicts that
the user had confirmed on the original assignment and was rejected.
Undo/redo of row assignments now restores the accepted state without a
new confirmation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

AGENTS.md

@@ -597,6 +597,13 @@ Critical target rules:
   remain canonical and are never silently changed.
 - Multi-socket objects remain indivisible. Row quantity stays
   `manualQuantity + sum(effectiveQuantity)`.
+- A row with linked Revit objects locks "Anzahl" in the editor. Its manual
+  share is edited in the optional column "Anz. manuell"; "Anz. Revit" shows
+  the linked share read-only. `circuit-device-row.update` derives the total
+  from a manual-only edit and rejects any quantity change that breaks
+  `quantity = manualQuantity + sum(effectiveQuantity)`, for every source.
+- Undo/redo of a row assignment restores an accepted state and does not ask
+  again for planning-value conflict confirmation.
 - The project configuration has no independent version counter. Preview and
   apply use `expectedRevision`; import batches store a configuration copy.
 - Apply retransmits and parses the workbook. Undo/Redo never reads Excel; they