Include components in project snapshots

This commit is contained in:
2026-07-30 19:24:28 +02:00
parent e7607c90c4
commit 012308984d
13 changed files with 915 additions and 46 deletions
+1 -1
View File
@@ -16,7 +16,7 @@ requirements and intended sequencing, not proof of implementation.
BMK rules.
- [x] Phase B1: additive relational schema, group backfill, component/protection
tables and shared BMK uniqueness.
- [ ] Phase B2: snapshot/transfer schema upgrade and deterministic compatibility
- [x] Phase B2: snapshot/transfer schema upgrade and deterministic compatibility
mapping.
- [ ] Phase C: persistent commands and new-board defaults.
- [ ] Phase D: group numbering, moves and destructive operations.
@@ -545,8 +545,7 @@ Acceptance:
### B. Persistence and Compatibility Model
Status: In progress. Relational foundation B1 is complete; logical
snapshot/transfer integration B2 is pending.
Status: Complete.
- add group category and group number
- add distribution-board component persistence
@@ -570,6 +569,21 @@ Implemented in B1:
- newly created legacy-compatible board structures receive the same initial
group identity while their persisted command format remains unchanged
Implemented in B2:
- snapshot schema version 7 includes group identity, distribution-board
components and both one-to-one protection collections
- capture, named and automatic snapshots, restore, Undo/Redo and portable JSON
transfers preserve the complete new relational state
- duplicate imports remap component UUIDs and both protection-owner references
together with the existing project structure
- versions 1 through 6 remain readable; version 6 maps the three established
section keys to group 1 and leaves new collections empty
- older flat circuit protection values remain present and are not guessed into
strict new protection configurations
- current snapshots reject invalid ownership, duplicate group numbers,
cross-entity BMKs and invalid protection configurations before persistence
Acceptance:
- a current database migrates without data loss