Create protected board defaults

docs/spec/08-current-product-backlog.md

@@ -18,7 +18,9 @@ requirements and intended sequencing, not proof of implementation.
   tables and shared BMK uniqueness.
 - [x] Phase B2: snapshot/transfer schema upgrade and deterministic compatibility
   mapping.
-- [ ] Phase C: persistent commands and new-board defaults.
+- [x] Phase C1: versioned new-board command with three groups and fixed header
+  components.
+- [ ] Phase C2: component and group CRUD/reorder commands.
 - [ ] Phase D: group numbering, moves and destructive operations.
 - [ ] Phase E: editor projection and editing.
 - [ ] Phase F: documentation and full GUI verification.

docs/spec/09-distribution-board-components-and-protection-groups.md

@@ -593,11 +593,25 @@ Acceptance:
 
 ### C. Persistent Commands and Board Defaults
 
+Status: In progress. New-board defaults C1 are complete; component and group
+management commands C2 are pending.
+
 - extend `distribution-board.insert` with fixed components and three groups
 - implement component and group CRUD commands
 - implement group and footer reordering
 - add complete inverse snapshots and rollback tests
 
+Implemented in C1:
+
+- `distribution-board.insert` schema version 3 carries stable UUIDs for three
+  initial groups, main switch `-Q0` and surge protective device `-FA`
+- its inverse verifies and removes the unchanged complete structure; Redo
+  restores the same UUIDs
+- a late revision/history failure rolls back board, list, groups and components
+  together
+- stored schema versions 1 and 2 retain four legacy sections and receive no
+  invented components
+
 Acceptance:
 
 - new boards contain the agreed fixed structure