Persist circuit protection updates

2026-07-31 07:37:38 +02:00
parent 0c92fbd09e
commit 18ca5eb3d4
12 changed files with 501 additions and 2 deletions
@@ -36,7 +36,8 @@ requirements and intended sequencing, not proof of implementation.
 - [x] Phase E2b: render the structure projection in the editor grid.
 - [x] Phase E3a: create, edit and delete mutable group and footer components.
 - [x] Phase E3b1: create, rename and safely delete empty circuit groups.
- [ ] Phase E3b2: circuit-protection editing.
+- [x] Phase E3b2a: persistent circuit-protection update command.
+- [ ] Phase E3b2b: circuit-protection defaults on insert and editor modal.
 - [ ] Phase E4: group reorder, renumber, circuit moves and populated-delete warning.
 - [ ] Phase E: editor projection and editing.
 - [ ] Phase F: documentation and full GUI verification.
@@ -742,7 +742,9 @@ Acceptance:
 Status: In progress. The complete tree read model E1, pure structural
 projection E2a, grid rendering E2b and mutable component editing E3a are
 complete. Basic group management E3b1 is also complete. Circuit-protection
-editing and structural drag/renumber/delete workflows remain pending.
+editing now has its persistent E3b2a command boundary; insertion defaults and
+the editor modal as well as structural drag/renumber/delete workflows remain
+pending.

 - render fixed header components
 - render group components and circuit blocks
@@ -777,6 +779,10 @@ Implemented in E1/E2a/E2b/E3a:
  child BMKs remain stable
 - an exactly empty group can be removed through the persistent group command;
  populated deletion stays disabled until the dedicated warning UI is present
+- `circuit-protection.update` inserts or updates one validated 1:1 protection
+  snapshot, rejects stale state and preserves exact persistent Undo/Redo
+- user commands cannot remove circuit protection; a nullable target exists
+  only as the inverse of adding protection to a retained circuit without it

 Acceptance: