Persist circuit group renumbering
This commit is contained in:
@@ -662,9 +662,8 @@ Acceptance:
|
||||
|
||||
### D. Group Numbering and Circuit Moves
|
||||
|
||||
Status: In progress. The deterministic renumber planner D1a is complete;
|
||||
persistent execution D1b, cross-group moves D2 and populated deletion D3
|
||||
remain pending.
|
||||
Status: In progress. Deterministic planning D1a and persistent execution D1b
|
||||
are complete; cross-group moves D2 and populated deletion D3 remain pending.
|
||||
|
||||
- implement nested identifier generation
|
||||
- support same-category cross-group circuit moves
|
||||
@@ -680,6 +679,17 @@ Implemented in D1a:
|
||||
- collisions with unchanged groups, no-op mappings and mismatched current BMKs
|
||||
are rejected before persistence
|
||||
|
||||
Implemented in D1b:
|
||||
|
||||
- `circuit-group.renumber` persists the complete expected/target plan as one
|
||||
project revision
|
||||
- group-number swaps use collision-safe temporary group identities and BMKs
|
||||
across both circuit and component tables
|
||||
- every current circuit and group component must be included unchanged before
|
||||
execution starts
|
||||
- Undo/Redo uses the exact inverse plan; late revision/history failures roll
|
||||
back every group, prefix and BMK
|
||||
|
||||
Acceptance:
|
||||
|
||||
- target identifiers use highest suffix plus one
|
||||
|
||||
Reference in New Issue
Block a user