Align documentation with clean baseline

Remove circuit structure preview
Add editable project floors and rooms
2026-07-31 16:41:37 +02:00 · 2026-07-31 14:52:37 +02:00 · 2026-07-31 14:46:06 +02:00 · 2026-07-31 14:37:45 +02:00 · 2026-07-31 14:33:47 +02:00 · 2026-07-31 14:07:26 +02:00
179 changed files with 9766 additions and 31325 deletions
@@ -33,17 +33,12 @@ It must support circuits, device rows, project devices, drag-and-drop restructur
 - General application repositories also require an explicit `AppDatabase`;
  `src/server/composition/application-repositories.ts` owns their runtime
  instances, and controllers never import the global SQLite client.
- The upgrade-only legacy migration service follows the same dependency rule;
-  its concrete repositories are instantiated only in
-  `scripts/db-migrate-legacy-consumers.ts`.
 - General Circuit, CircuitDeviceRow, CircuitList and DistributionBoard
  repositories expose only active reads. Runtime writes belong in typed command
  repositories; direct integration fixtures belong under `tests/support`.

-The supported runtime model is Circuit-First. The former Consumer UI and API are
-removed. Retained `consumers` rows, migration mappings and reports are upgrade-only
-data accessed by `npm run db:migrate:legacy-consumers`; do not build application
-features on them.
+The supported runtime model is Circuit-First. The former Consumer UI, API,
+tables and upgrade tooling are removed; do not reintroduce them.

 See `docs/current-architecture.md` for the complete module and request flow.

@@ -250,14 +245,14 @@ Immutable revision metadata is available through the paginated
 stored command payloads.
 Named logical snapshots can be created and listed through project-scoped API
 endpoints. Their schema-versioned payload contains the complete supported
-project runtime state and a SHA-256, excludes global/upgrade-only data and does
+project runtime state and a SHA-256, excludes global data outside the project and does
 not change the project revision or undo/redo stacks. Restoring a server-stored
 snapshot verifies its checksum and the current-state hash, replaces supported
 project data atomically and records a new `restore` revision with a complete
 inverse command. Restore can therefore be undone and redone after a restart.
-Snapshot schema version 7 also contains circuit-group identity,
+Baseline snapshot schema version 1 contains circuit-group identity,
 distribution-board components and the separate circuit/component protection
-records. Versions 1 through 6 remain readable. Portable duplicate imports
+records. Pre-baseline snapshots are unsupported. Portable duplicate imports
 remap component ids and protection-owner references together with the existing
 project graph.
 The central revision boundary creates an automatic logical snapshot after each
@@ -294,13 +289,18 @@ change in one revision and Undo/Redo restores them together; the project PUT
 route requires `expectedRevision`. The system catalog is `AV`, `SV`, `EV`,
 `USV`, `MSR`, `SiBe`; at least one must be enabled and a type used by a board
 cannot be disabled.
-Distribution-board setup uses `distribution-board.insert` schema version 3
+Distribution-board setup uses `distribution-board.insert` schema version 1
 with a complete stable snapshot of the board, circuit list, three default
 groups, main switch `-Q0` and surge protective device `-FA`. Its
 inverse removes only the same unchanged and still-empty structure; the POST
 route requires `expectedRevision` and returns the updated history state.
-Stored schema-version 1 and 2 setup commands remain executable with their four
-legacy sections and without invented components.
+Complete populated distribution-board copying and deletion use
+`distribution-board.insert-subtree` and `distribution-board.delete-subtree`.
+Their exact snapshots include the board, circuit list, groups, circuits,
+device rows, components and all one-to-one protection data. Copy remaps all
+owning ids but preserves project-device and room links. Both operations are
+atomic persistent commands with restart-safe Undo/Redo; deletion requires an
+explicit UI warning.
 Mutable group-protection and auxiliary distribution-board components use
 `distribution-board-component.insert` and
 `distribution-board-component.delete`; edits and footer reordering use
@@ -335,15 +335,15 @@ UUID in foreign-key-safe order.
 The circuit-tree read model exposes fixed `headerComponents`, group-owned
 `components`, `footerComponents`, optional group category/number and optional
 one-to-one protection DTOs for circuits and group components. These are
-additive to the retained flat circuit protection fields during the transition.
+the only supported circuit-protection source; no flat compatibility fields remain.
 Distribution-board floor assignment and a project-enabled supply type use
 `distribution-board.update`; both values are snapshot/export fields and one
 persistent undo step.
-Floor and room setup use `project-floor.insert` and `project-room.insert` with
-complete stable snapshots. Their inverses remove only unchanged records and
+Floor and room setup uses persistent insert, update and delete commands with
+complete stable snapshots. Their inverses remove or restore only unchanged records and
 reject floors with assigned rooms/distribution boards or rooms referenced by
-device rows or retained upgrade data. Both POST routes require `expectedRevision` and return
-the updated history state.
+device rows. All write routes require `expectedRevision` and return the updated
+history state.

 Required operations:

@@ -382,7 +382,10 @@ Users must be able to override sizing suggestions.
 ## Persistence and Migration Rules

 - SQLite is the currently supported database.
- Never edit an already applied migration.
+- Migration `0000` is the clean release baseline for empty databases.
+- Pre-baseline development databases, snapshots and stored commands are not
+  supported.
+- After the first release, never edit an already applied migration.
 - Back up an existing database before applying a new migration.
 - Inspect generated SQL; it must contain only the intended schema change.
 - Keep database backups separate from logical project snapshots.
@@ -12,7 +12,11 @@ implementiert.
 ## Unterstützter Arbeitsablauf

 - Projekte, Verteilungen, Etagen und Räume verwalten
- pro Verteilung eine Stromkreisliste mit festen Bereichen bearbeiten
+- pro Verteilung geschützte Stromkreisgruppen für Beleuchtung, 1-phasige und
+  3-phasige Stromkreise verwalten
+- Hauptschalter, Überspannungsableiter, Gruppenschutz und zusätzliche
+  Verteilergeräte in der Stromkreisliste abbilden
+- Schutzgeräte je Stromkreis und optional je Gruppe konfigurieren
 - leere, einzeilige und mehrzeilige Stromkreise abbilden
 - Stromkreise und Gerätezeilen per Drag-and-drop umstrukturieren
 - Projektgeräte einfügen, verknüpfen und kontrolliert synchronisieren
@@ -90,6 +94,7 @@ Frontend und API laufen anschließend auf denselben Ports wie im Docker-Setup.
 npm test
 npm run build:api
 npm run build:web
+npm run typecheck:scripts
 npx tsc --noEmit -p tsconfig.next.json
 ```

@@ -103,11 +108,9 @@ npm run db:generate
 ```

 `db:backup` verwendet die SQLite-Online-Backup-API und prüft das Ergebnis auf
-Integrität und Fremdschlüsselverletzungen. Vor jeder Migration einer bestehenden
-Datenbank ist ein Backup erforderlich.
-
-`db:migrate:legacy-consumers` und `db:backfill:sections` sind ausschließlich
-Upgrade-Werkzeuge für ältere Datenbanken. Neue Installationen benötigen sie nicht.
+Integrität und Fremdschlüsselverletzungen. Die Migration `0000` ist die
+Release-Baseline und richtet ausschließlich eine neue, leere Datenbank ein.
+Datenbanken aus Entwicklungsständen vor dieser Baseline werden nicht unterstützt.

 ## Dokumentation

@@ -20,9 +20,6 @@ ausdrücklich getrennt und dürfen nicht als bereits implementiert verstanden we

 - [Entwicklungs- und Contributor-Workflow](development-workflow.md)
 - [Deployment und Betrieb](deployment.md)
- [Lokale Circuit-First-Datenbankmigration](local-db-circuit-first-migration.md)
- [Retained Legacy-Datenmigration](circuit-list-editor-migration.md) –
-  ausschließlich für Upgrades alter Datenbanken

 ## Zukunftsarchitektur

@@ -59,16 +59,23 @@ this value for optimistic concurrency checks.
  - clients cannot submit arbitrary `project.restore-state` payloads through
    the generic command endpoint

-The public dispatcher currently supports `circuit.update`, `circuit.insert`,
-`circuit.delete`, `circuit-device-row.update`,
-`circuit-device-row.insert`, `circuit-device-row.delete`,
-`circuit-device-row.move`, `circuit-device-row.move-with-new-circuit`,
-`circuit.reorder-section`, `circuit.reorder-sections`,
-`circuit.renumber-section` and
-`project-device.update`, `project-device.insert`, `project-device.delete` and
-`project-device.sync-rows` as well as `project.update-settings`, all with
-schema version `1`. Other command types
-are rejected. Insert commands contain the complete entity or circuit block
+The public dispatcher supports the Circuit and CircuitDeviceRow commands
+`circuit.update`, `circuit.insert`, `circuit.delete`,
+`circuit-device-row.update`, `circuit-device-row.insert`,
+`circuit-device-row.delete`, `circuit-device-row.move`,
+`circuit-device-row.move-with-new-circuit`, `circuit.reorder-section`,
+`circuit.reorder-sections` and `circuit.renumber-section`.
+
+Protected-board structure uses
+`distribution-board-component.insert|update|delete`,
+`circuit-group.insert|update|delete|reorder|renumber`,
+`circuit.move-group`, `circuit-group.delete-subtree` and
+`circuit-protection.update`. A subtree restore is normally emitted only as the
+persisted inverse of a delete. The dispatcher also supports the documented
+project-device, project settings, distribution-board and project-location
+commands. The generic editor commands listed here use schema version `1`;
+the clean pre-release baseline does not accept older development formats.
+Unsupported types or schema versions are rejected. Insert commands contain the complete entity or circuit block
 with stable ids; delete commands include the expected parent identity. Circuit
 snapshots contain zero, one or multiple complete device rows. Move commands
 contain each row's expected and target circuit plus its exact expected and
@@ -101,6 +108,24 @@ targets occupied by other sections, then applies swaps through collision-safe
 temporary identifiers. Undo restores the exact prior identifiers; sort
 positions and device rows remain unchanged.

+`circuit-group.reorder` changes only complete group sort assignments.
+`circuit-group.renumber` carries every affected group, child circuit and group
+component with expected and target identifiers so swaps can be applied
+collision-safely. `circuit.move-group` changes one complete circuit's group,
+BMK and position and stores the deterministic target BMK. The target group must
+have the same category.
+
+`circuit-group.delete-subtree` carries the complete warned group state,
+including both protection layers and every device-row link/override value. The
+server captures the current subtree again inside the transaction and rejects a
+stale or incomplete snapshot. Undo restores the same UUIDs through the stored
+inverse command.
+
+`circuit-protection.update` inserts or replaces the complete validated
+one-to-one circuit protection state. Users cannot remove the required
+protection row; removal is available only to a stored inverse when undoing its
+initial creation.
+
 `project-device.sync-rows` represents `synchronize`, `disconnect` and
 `reconnect` operations. Every selected row carries complete expected and target
 snapshots of all ProjectDevice-sync fields, the link and `overriddenFields`.
@@ -200,14 +225,27 @@ returns HTTP `409` with `PROJECT_HISTORY_OPERATION_UNAVAILABLE`.
    `{ "distributionBoard": { ... }, "revision": { ... }, "history": { ... } }`
  - persistent Undo removes only the unchanged and still-empty generated
    structure; Redo restores the same ids
-  - stored command schema versions 1 and 2 remain executable with their four
-    legacy sections and without generated components
  - stale revisions return `409 PROJECT_REVISION_CONFLICT`
 - `PUT /projects/:projectId/distribution-boards/:distributionBoardId`
  - body:
    `{ "floorId": null, "supplyType": "AV", "expectedRevision": 13 }`
  - executes `distribution-board.update`; floor and supply type are restored
    together by persistent Undo/Redo
+- `POST /projects/:projectId/distribution-boards/:distributionBoardId/copy`
+  - body: `{ "name": "UV-02 Kopie", "expectedRevision": 14 }`
+  - duplicates the complete distribution-board subtree with new owning UUIDs
+    while preserving project-device and room links
+  - response includes the new `distributionBoard`, its `circuitList`, the
+    revision and current history state
+- `DELETE /projects/:projectId/distribution-boards/:distributionBoardId`
+  - body: `{ "expectedRevision": 15 }`
+  - removes the complete, exactly captured distribution-board subtree in one
+    transaction
+  - response includes `distributionBoardId`, the revision and current history
+    state
+- Copy and deletion use `distribution-board.insert-subtree` and
+  `distribution-board.delete-subtree`. Persistent Undo/Redo restores or
+  removes the same complete subtree, including protection devices.

 ### Project Floors and Rooms

@@ -215,16 +253,27 @@ returns HTTP `409` with `PROJECT_HISTORY_OPERATION_UNAVAILABLE`.
  - body: `{ "name": "EG", "expectedRevision": 13 }`
  - executes `project-floor.insert` with a stable floor id
  - response: `{ "floor": { ... }, "revision": { ... }, "history": { ... } }`
+- `PUT /projects/:projectId/floors/:floorId`
+  - body: `{ "name": "1. OG", "expectedRevision": 14 }`
+  - executes an exact persistent floor update
+- `DELETE /projects/:projectId/floors/:floorId`
+  - body: `{ "expectedRevision": 15 }`
+  - rejects floors with assigned rooms or distribution boards
 - `POST /projects/:projectId/rooms`
  - body:
    `{ "floorId": "floor_1", "roomNumber": "001", "roomName": "Technik", "expectedRevision": 14 }`
  - executes `project-room.insert` with a stable room id; `floorId` is optional
    and must belong to the project when present
  - response: `{ "room": { ... }, "revision": { ... }, "history": { ... } }`
- Persistent Undo removes only unchanged, unreferenced records. A floor with
-  assigned rooms or distribution boards and a room referenced by device rows
-  or retained upgrade data are rejected instead of silently clearing foreign
-  keys.
+- `PUT /projects/:projectId/rooms/:roomId`
+  - body:
+    `{ "floorId": null, "roomNumber": "101", "roomName": "Büro", "expectedRevision": 16 }`
+  - updates number, name and optional floor as one persistent command
+- `DELETE /projects/:projectId/rooms/:roomId`
+  - body: `{ "expectedRevision": 17 }`
+  - rejects rooms referenced by device rows
+- Persistent Undo/Redo restores exact previous and target records without
+  silently clearing foreign keys.
 - Stale revisions return `409 PROJECT_REVISION_CONFLICT`.

 ### Tree Endpoint
@@ -318,12 +367,6 @@ available only as the corresponding versioned commands through
 structure POST, move, reorder, renumber, identifier-restore, Circuit DELETE or
 CircuitDeviceRow DELETE routes.

-## Removed Legacy Endpoints
-
-The former `/consumers` read/write endpoints were removed after every retained
-consumer had a verified Circuit-First migration mapping. Database upgrade tooling
-reads retained legacy rows directly; application features must use the Circuit-First
-endpoints above.

 ## Linked Project Device Review

@@ -17,13 +17,15 @@ The pure grid modules have no React state and are covered by focused unit tests.
 ## Domain Model Overview

 - `CircuitSection`
-  - Groups circuits by planning section (for example lighting, single-phase, three-phase).
-  - Owns section metadata (`key`, `displayName`, `prefix`, ordering).
+  - Represents a protected circuit group in one of the categories lighting,
+    single-phase or three-phase.
+  - Owns category, positive group number, generated prefix, display name and
+    ordering.
 - `Circuit`
  - Core electrical unit in the list.
  - Owns circuit-level identifiers and technical data:
    - `equipmentIdentifier` (BMK)
-    - protection data
+    - one explicit one-to-one protection device
    - cable data
    - reserve state
    - voltage and optional control requirement for future sizing
@@ -43,11 +45,10 @@ The pure grid modules have no React state and are covered by focused unit tests.
 - `ProjectDevice`
  - Reusable device template entity at project level.
  - Can be linked to `CircuitDeviceRow` entries, with copied display values on insert.
- Retained legacy migration source
-  - Old `consumers` rows, mappings and reports are available only to explicit
-    database upgrade tooling.
-  - They are not application-domain entities and have no UI or API.
-
+- `DistributionBoardComponent`
+  - Represents fixed header components, optional group protection and manually
+    named auxiliary footer devices with their own unique BMK.
+  - Group protection may own a separate one-to-one protection configuration.
 ## Why A Circuit Is Not One Row

 A circuit can contain zero, one, or many device rows. Treating a circuit as a single row breaks:
@@ -77,7 +78,9 @@ Section-level `-frei-` placeholder rows represent insertion targets for creating
 `equipmentIdentifier` / BMK is circuit-owned (`Circuit.equipmentIdentifier`).

 - Device rows do not have their own BMK.
- Existing identifiers must stay stable unless explicitly changed by user action.
+- Existing identifiers stay stable on sort, insert and delete. Explicit
+  renumbering may change them, and a user-initiated complete-circuit move to
+  another same-category group assigns the next target-group identifier.
 - Renumbering is explicit, not implicit on move/sort/delete.

 ## Data Ownership Split: Circuit vs Device Row
@@ -108,14 +111,14 @@ Primary circuit-first editor route:

 - `/projects/:projectId/circuit-lists/:circuitListId/tree-edit`

-The sibling `/tree` route is a read-only structure preview. Old
-`/projects/:projectId/circuit-lists` bookmarks redirect to the project page.
+Old `/projects/:projectId/circuit-lists` bookmarks redirect to the project
+page. A future print view will provide a dedicated read-only presentation.

 ## Future Persistence Direction

-Persistent undo/redo, project revisions, logical snapshots, external-model exchange and PostgreSQL readiness are specified in [Project History and External Model Architecture](./project-history-and-external-model-architecture.md).
-
-Critical multi-write commands already use explicit persistence transaction
-adapters. The next step is to compose these command boundaries into server-side,
-project-scoped revisions and change sets. Database backups remain separate from
-user-visible project snapshots.
+Persistent Undo/Redo, project revisions and logical snapshots are implemented
+through project-scoped commands and the shared transaction boundary. Database
+backups remain separate from user-visible project snapshots. External-model
+exchange and PostgreSQL readiness are specified in
+[Project History and External Model Architecture](./project-history-and-external-model-architecture.md)
+and remain future work.
@@ -28,6 +28,7 @@ The editor can have a selected cell without an active editor input. `editingCell
 The UI works from a normalized `visibleRows` model built from filtered/sorted sections:

 - section header rows
+- fixed header, group-protection and auxiliary footer component rows
 - circuit rows (`circuitCompact`, `circuitSummary`, `reserveCircuit`)
 - device rows (`deviceRow`)
 - section placeholder rows (`placeholder`)
@@ -82,13 +83,21 @@ Intent is separated by drag source type:
 - device row drag:
  - drop to existing circuit -> move row(s) into that circuit
  - drop to placeholder -> create new target circuit and move row(s)
+  - drop on the upper or lower edge of a circuit row -> create a new target
+    circuit directly before or after that circuit and move the row(s)
+  - the center of a circuit row remains the explicit target for adding the
+    row(s) to that existing circuit
  - crossing a section boundary requires explicit confirmation
  - phase type, category, linked project device and local row values remain unchanged
  - target creation, row assignments and reserve-state updates use one SQLite transaction
 - circuit drag (BMK handle):
-  - reorder circuits inside same section only
-  - cross-section reorder is rejected
-  - the complete section order is validated and stored in one SQLite transaction
+  - reorder one or multiple circuits inside the same group without changing BMKs
+  - move exactly one circuit into another group of the same category
+  - a cross-group move assigns the highest existing target suffix plus one;
+    gaps are not filled
+  - cross-category and cross-group multi-circuit moves are rejected
+  - same-group reorder validates the complete group order; cross-group move
+    stores the one exact source/target transition
 - bulk device row move:
  - supported via multi-selection + drag
 - multi-circuit move:
@@ -96,7 +105,25 @@ Intent is separated by drag source type:

 The sidebar insertion controls use the same project-device placement rules as drag-and-drop. Invalid section and circuit options are disabled after selecting a project device.

-Cross-section device moves show confirmation-required feedback before drop. The confirmation names source and target sections and warns that the unchanged device classification may need manual review. Cancelling leaves every row and circuit unchanged. Moving never renumbers existing circuits.
+Cross-section device moves show confirmation-required feedback before drop. The confirmation names source and target sections and warns that the unchanged device classification may need manual review. Cancelling leaves every row and circuit unchanged. Device-row moves never renumber circuits; the explicitly initiated complete-circuit group move is the sole automatic BMK-changing move.
+
+## Protected Group and Component Controls
+
+- New groups are created manually in one of the three supported categories and
+  receive the highest existing category group number plus one.
+- Group headings always show the stored editable display name; category labels
+  do not overwrite names of the default first groups.
+- Group reorder buttons move only relative to category peers and never change a
+  group number or BMK.
+- `Gruppen-BMK neu nummerieren` is an explicit confirmed category-wide action.
+  It follows the persisted group order and updates group prefixes, optional
+  `.0` protection BMKs and circuit BMKs together.
+- Optional group upstream protection and group FI as well as auxiliary footer
+  components use labeled, type-dependent modals.
+- Each circuit protection device uses its own modal; only fields valid for the
+  selected type are shown.
+- Removing a populated group warns with circuit, device-row and group
+  protection counts. The complete deletion remains persistently undoable.

 ## Filtering and Sorting

@@ -118,7 +145,8 @@ Cross-section device moves show confirmation-required feedback before drop. The

 - Column visibility and order are configurable.
 - BMK column (`equipmentIdentifier`) is locked as first column.
- Layout is saved in local storage (`circuitTreeEditor.columnLayout.v1`).
+- Layout is saved in local storage under a project-specific key so switching
+  distribution boards preserves the same project layout.

 ## Undo/Redo

@@ -138,8 +166,10 @@ Covered operations include:
 - insert/delete circuit
 - insert/delete row
 - edit cell values
- moves (single/bulk rows, circuit reorder)
- renumber and identifier update flows
+- moves (single/bulk rows, circuit reorder and same-category group move)
+- circuit and group renumber/identifier flows
+- component, group and protection editing
+- warned populated-group deletion and exact restoration
 - apply sorted order

 The editor toolbar exposes availability through its Undo/Redo buttons. The
@@ -16,5 +16,10 @@
 - Final electrical sizing logic is not implemented yet.
 - No full norm-compliant voltage-drop and protection-dimensioning calculation flow yet.
 - Sorting is view-only until users explicitly apply sorted order.
- Cross-section circuit drag-reorder is intentionally blocked.
- Legacy consumer UI and server endpoints are removed; retained source rows and migration mappings remain available only for upgrade traceability.
+- Complete-circuit drag supports one circuit at a time between groups of the
+  same category. Cross-category moves and multi-circuit moves across group
+  boundaries are intentionally rejected; multi-circuit reorder inside one
+  group remains supported.
+- Protection and cable values are planner-owned manual selections. The later
+  sizing/warning engine does not yet validate them against load, length or
+  voltage-drop rules.
@@ -1,90 +0,0 @@
-# Circuit List Editor Migration
-
-## Status
-
-Upgrade-only. New installations already use the Circuit-First schema and do not
-run this workflow.
-
-## Goal
-
-Migrate legacy row-first consumers into the circuit-first model without deleting legacy data.
-
-## Legacy Mapping
-
-Legacy `Consumer` rows map into:
-
- `Circuit` for shared circuit identity and circuit-level technical fields
- `CircuitDeviceRow` for per-device load rows
-
-Multiple legacy consumers can map into one circuit when they share normalized circuit identity.
-
-For one circuit list, all new circuits, device rows, trace mappings and the migration report are committed in one SQLite transaction. A failed run therefore leaves none of those prepared migration writes behind.
-
-## Grouping Strategy (`circuitNumber`)
-
-Migration groups legacy rows by normalized `circuitNumber`:
-
- valid/normalizable values become one target circuit per normalized value
- duplicates are grouped under that circuit (multiple `CircuitDeviceRow`s)
- missing/invalid values trigger generated identifiers and may fall back to `unassigned` section
-
-## Default Section Backfill
-
-Before migration, default sections are created/backfilled per circuit list.  
-This guarantees a valid target section space, including `unassigned` when no section can be inferred.
-
-## Migration Commands
-
-Run in this order for local database workflows:
-
-1. Backup:
-   - `npm run db:backup`
-2. Migrate schema:
-   - `npm run db:migrate`
-3. Verify circuit schema:
-   - `npm run db:verify:circuit-schema`
-4. Backfill missing sections:
-   - `npm run db:backfill:sections`
-5. Migrate legacy consumers:
-   - `npm run db:migrate:legacy-consumers`
-
-The migration command finishes with a cutover verification across the complete
-database. It exits with an error while any legacy consumer lacks a migration
-mapping, including consumers that cannot be migrated because they have no circuit
-list assignment. The legacy multi-list UI was removed only after this check passed;
-old `/projects/:projectId/circuit-lists` bookmarks redirect to the project page.
-
-## Validation Checks
-
-After migration, verify:
-
- tree endpoint returns sections/circuits/rows
- grouped duplicate circuit numbers are reported
- generated identifiers are reported where expected
- migrated rows include `legacyConsumerId` traceability
- no duplicate BMKs exist inside one circuit list
-
-## If Tree Endpoint Returns Empty Sections
-
-Likely causes:
-
- circuit-first tables missing (migration not run)
- sections not backfilled yet
- migrated dataset genuinely empty for selected list
-
-Actions:
-
-1. Run schema migration and verification commands.
-2. Run section backfill command.
-3. Run legacy-consumer migration command.
-4. Retry tree endpoint.
-
-## Legacy Data Retention
-
-Do not delete legacy consumers yet.
-
- legacy read/write endpoints have been removed from the application server
- migration trace tables reference old/new mapping
- retained rows allow upgrade verification and audit of the completed mapping
- a future automatic cleanup migration must migrate and verify old databases
-  before dropping these source and trace tables
@@ -9,10 +9,8 @@ Der unterstützte Editor ist Circuit-First:
 Ein Stromkreis ist nicht dasselbe wie eine Gerätezeile. BMK, Schutz- und Kabeldaten
 gehören zum Stromkreis; Last-, Raum- und Kategoriedaten gehören zur Gerätezeile.

-Die frühere Consumer-Oberfläche und ihre API sind entfernt. Die Tabelle
-`consumers` sowie Mappings und Reports bleiben ausschließlich erhalten, damit
-ältere Datenbanken über den expliziten Upgrade-Befehl migriert und geprüft werden
-können.
+Die frühere Consumer-Oberfläche, ihre API, Tabellen und Upgrade-Werkzeuge sind
+entfernt. Neue Funktionen bauen ausschließlich auf dem Circuit-First-Modell auf.

 ## Laufzeit

@@ -130,8 +128,8 @@ Datenbank-Backups gespeichert. `POST /api/projects/:projectId/snapshots`
 erzeugt bei passender erwarteter Revision transaktional einen vollständigen,
 schema-versionierten Projektzustand mit SHA-256-Prüfwert. Enthalten sind
 Projekteinstellungen, Verteiler, Stromkreislisten, Bereiche, Stromkreise und
-Gerätezeilen sowie Projektgeräte, Geschosse und Räume. Globale Geräte,
-Legacy-Consumer und Migrationsberichte sind nicht Teil des Projekt-Snapshots.
+Gerätezeilen sowie Projektgeräte, Geschosse und Räume. Globale Geräte sind nicht
+Teil des Projekt-Snapshots.
 Create/List verändern weder Projektrevision noch Undo-/Redo-Stapel.
 `kind` unterscheidet benannte und automatische Stände. Die zentrale
 Revisionspersistenz erzeugt nach jeweils 25 weiteren Projektänderungen
@@ -144,9 +142,7 @@ Prüfsumme, erwartete Revision und den unmittelbar zuvor gelesenen
 Projektzustand. Der Restore ersetzt alle unterstützten Projektdaten in einer
 Transaktion und schreibt dabei eine neue Revision mit Quelle `restore` sowie
 ein vollständiges inverses Kommando. Undo und Redo können deshalb auch einen
-Restore nach einem Neustart exakt zurücknehmen oder wiederholen. Kompatible
-Upgrade-only-Verknüpfungen und Migrationsnachweise bleiben erhalten, obwohl sie
-nicht Bestandteil des logischen Snapshots sind.
+Restore nach einem Neustart exakt zurücknehmen oder wiederholen.
 Die Projektseite bindet diese APIs in einem einklappbaren Bereich
 „Versionen und Sicherungspunkte“ ein. Dort können Benutzer Sicherungspunkte
 benennen, jeden aufgeführten benannten oder automatischen Stand nach
@@ -246,8 +242,7 @@ Store leitet das inverse Kommando aus dem gespeicherten Projekt ab und schreibt
 Werte, Revision und Historienstapel gemeinsam. `PUT /api/projects/:projectId`
 verlangt deshalb `expectedRevision`, liefert Projekt plus aktualisierten
 Historienstand und besitzt keinen separaten direkten Settings-Schreibweg mehr.
-Kommando- und Snapshot-Versionen vor dieser Erweiterung bleiben les- und
-ausführbar; fehlende Metadaten werden dabei als `null` behandelt.
+Kommando- und Snapshot-Payloads müssen dem aktuellen Baseline-Schema entsprechen.
 Die Projektseite zeigt Verteilungen, Etagen und Räume als kompakte
 Bestandsübersichten; ihre versionierten Erstellwege öffnen beschriftete Modals
 statt dauerhafter Eingabezeilen. Projektgeräte werden als durchsuchbare,
@@ -263,16 +258,16 @@ läuft über `project.restore-state` und ist dadurch eine atomare, dauerhaft
 rückgängig machbare Projektrevision. Der Modus `duplicate` ordnet Projekt-,
 Struktur-, Gruppen-, Verteilerkomponenten-, Raum-, Stromkreis- und
 Gerätezeilen-UUIDs sowie Schutzgeräte-Referenzen vollständig neu zu und legt
-die Kopie mit Revision `0` in einer Transaktion an. Upgrade-only-
-Consumer-Verweise werden nicht in die Kopie übernommen; fachliche Verknüpfungen
-innerhalb des unterstützten Laufzeitmodells bleiben erhalten. Die
+die Kopie mit Revision `0` in einer Transaktion an. Fachliche Verknüpfungen
+innerhalb des unterstützten Laufzeitmodells bleiben
+erhalten. Die
 Projektübersicht verwendet dafür den separaten Collection-Endpunkt
 `POST /api/projects/import`, der ausschließlich eine neue Kopie anlegt und
 deshalb weder eine bestehende Projekt-ID noch `expectedRevision` annimmt. Das
 Ersetzen eines Projekts bleibt auf dessen Einstellungsmodal und den
 projektgebundenen Endpunkt beschränkt.
 `distribution-board.insert` versioniert die Anlage einer Verteilung mit
-Command-Schema 3 als vollständigen Block aus Verteilung, Stromkreisliste, den
+Command-Schema 1 als vollständigen Block aus Verteilung, Stromkreisliste, den
 drei Gruppen `Beleuchtung 1`, `1-phasig 1`, `3-phasig 1`, Hauptschalter `-Q0`
 und Überspannungsableiter `-FA`.
 Alle UUIDs entstehen vor dem Command und bleiben über Undo/Redo stabil.
@@ -283,8 +278,16 @@ Controller-Schreibweg ist entfernt. Verteilungen besitzen eine optionale
 Etagenreferenz sowie eine Netzart aus dem Projektkatalog. Anlage und
 nachträgliche Bearbeitung prüfen die Projektzugehörigkeit der Etage und die
 Freigabe der Netzart in den Projekteinstellungen.
-Gespeicherte Anlage-Commands der Schemas 1 und 2 bleiben mit ihren vier
-Legacy-Abschnitten und ohne nachträglich erfundene Komponenten ausführbar.
+Bereits befüllte Verteilungen werden über
+`distribution-board.insert-subtree` und `distribution-board.delete-subtree`
+als vollständiger Unterbaum kopiert beziehungsweise gelöscht. Der Snapshot
+umfasst Verteilung, Stromkreisliste, Gruppen, Stromkreise, Gerätezeilen,
+Verteilerkomponenten und alle zugehörigen Schutzgeräte. Beim Kopieren werden
+sämtliche besitzenden UUIDs neu vergeben, während fachliche Verknüpfungen zu
+Projektgeräten und Räumen erhalten bleiben. Beide Aktionen sind atomare
+Projektrevisionen und bleiben nach einem Neustart über Undo/Redo umkehrbar. Die
+Projektseite bietet sie im Einstellungsmodal der jeweiligen Verteilung an;
+Löschen verlangt dort eine ausdrückliche Bestätigung.
 `distribution-board-component.insert` und
 `distribution-board-component.delete` sowie
 `distribution-board-component.update` versionieren Anlage, Entfernung,
@@ -296,15 +299,15 @@ einen vollständigen Zielzustand aus; ID, Eigentum, Rolle und Platzierungszone
 bleiben dabei unverändert. Projekt-, Listen- und Gruppenzugehörigkeit sowie
 veraltete Zustände werden innerhalb derselben Transaktion geprüft. Die festen
 Kopfkomponenten Hauptschalter und Überspannungsableiter sind von diesen
-allgemeinen Commands ausgeschlossen. API- und Editorintegration folgen in den
-nächsten Arbeitspaketen.
+allgemeinen Commands ausgeschlossen. Veränderliche Gruppen- und Fußkomponenten
+werden im Editor über eigene Modale und diese Commands verwaltet.
 Leere Stromkreisgruppen werden über `circuit-group.insert`,
 `circuit-group.update` und `circuit-group.delete` verwaltet. Ihr vollständiger
 Snapshot koppelt Kategorie, positive Gruppennummer und daraus abgeleiteten
 BMK-Präfix; allgemeine Updates ändern ausschließlich den Anzeigenamen.
 Löschen verlangt einen exakt unveränderten Zustand ohne Stromkreise und ohne
-Gruppenkomponenten. Das bestätigte Löschen befüllter Unterbäume bleibt ein
-eigener späterer Command.
+Gruppenkomponenten. Befüllte Gruppen verwenden getrennt davon den vollständigen
+`circuit-group.delete-subtree`-Command mit ausdrücklicher Warnung.
 `circuit-group.reorder` sortiert Gruppen als vollständige Stromkreislisten-
 Zuordnung. Jede vorhandene Gruppe muss mit erwarteter und neuer Position
 enthalten sein. Der Command verändert ausschließlich `sortOrder`; Nummern,
@@ -346,47 +349,91 @@ Teilwiederherstellungen.
 Der Circuit-Tree liefert zusätzlich `headerComponents`,
 gruppenbezogene `components` und `footerComponents`. Abschnitte enthalten
 optionale Gruppenkategorie und -nummer; Stromkreise und Gruppenkomponenten
-enthalten ihre optionale getrennte Schutzgerätekonfiguration. Die bisherigen
-flachen Stromkreis-Schutzfelder bleiben während der Übergangsphase additiv
-erhalten. Separate aktive Read-Repositories lesen Komponenten- und beide
+enthalten ihre getrennte Schutzgerätekonfiguration. Die
+1:1-Schutzgerätetabellen sind die einzige unterstützte Quelle dieser Daten.
+Separate aktive Read-Repositories lesen Komponenten- und beide
 Schutzgerätetabellen; Schreibzugriffe bleiben ausschließlich in Commands.
 `src/frontend/utils/circuit-structure-projection.ts` projiziert diesen Tree
 rein und deterministisch in die drei Zonen Kopf, vollständige Gruppen und Fuß.
 Innerhalb einer Gruppe folgen auf die Überschrift optionale Schutzkomponenten,
 vollständige Stromkreisblöcke und der freie Einfügeplatz. Leere Gruppen bleiben
 sichtbar; Komponenten werden stabil nach `sortOrder` und ID sortiert.
+`circuit-grid-projection.ts` normalisiert diese Struktur zusammen mit den
+bisherigen kompakten und mehrzeiligen Stromkreisblöcken für den Editor. Kopf-,
+Gruppen- und Fußkomponenten erscheinen als Zeilen über die volle Tabellenbreite
+und nehmen nicht an Zellauswahl oder Tastatur-Einfügen teil. Hauptschalter und
+Überspannungsableiter bleiben feste, schreibgeschützte Kopfkomponenten.
+Optionale Gruppenvorsicherungen, Gruppen-FIs und zusätzliche Verteilergeräte
+werden über beschriftete Modale angelegt, bearbeitet und nach Bestätigung
+entfernt. Der Frontend-API-Adapter serialisiert dafür die vorhandenen
+`distribution-board-component.*`-Commands; die verbindliche
+geräteabhängige Validierung und atomare Revision bleiben serverseitig.
+Neue Stromkreisgruppen erhalten im Editor die höchste vorhandene
+Gruppennummer ihrer Kategorie plus eins und ein daraus abgeleitetes Präfix.
+Das Bearbeiten ändert ausschließlich den Anzeigenamen. Nur vollständig leere
+Gruppen können über `circuit-group.delete` entfernt werden; für befüllte
+Gruppen bleibt die Aktion bis zum gesonderten Warn- und Unterbaumdialog
+gesperrt.
+`circuit-protection.update` bildet die eigene persistente Schreibgrenze für
+die neue 1:1-Stromkreisschutztabelle. Der Command vergleicht den vollständigen
+erwarteten Datensatz, validiert Typ und abhängige Felder, prüft die
+Projektzugehörigkeit und schreibt Schutzgerät, Revision und Historienübergang
+atomar. Benutzer können Schutzdaten anlegen oder ändern, aber nicht entfernen;
+Undo einer erstmaligen Anlage darf den zuvor fehlenden Datensatz exakt
+wiederherstellen.
+Der vollständige `CircuitSnapshot` enthält den zugehörigen
+`protectionDevice`-Datensatz, sofern einer vorhanden ist. Neue Stromkreise und
+durch Geräteverschiebung erzeugte Zielstromkreise verwenden die vereinbarten
+Kategorie-Standardwerte und schreiben Schutzgerät, Stromkreis sowie
+Gerätezeilen atomar. Delete/Undo erfasst denselben Datensatz vollständig.
+Im Editor sind die Schutzspalten deshalb eine
+schreibgeschützte Projektion der 1:1-Daten; Änderungen erfolgen über ein
+geräteabhängiges Schutzgeräte-Modal und `circuit-protection.update`.
+Gruppen lassen sich im Editor schrittweise nur gegenüber einer benachbarten
+Gruppe derselben Kategorie verschieben. Der Client sendet dabei immer die
+vollständige erwartete und gewünschte Sortierreihenfolge über
+`circuit-group.reorder`; Gruppennummer, Präfix und Kind-BMK bleiben unverändert.
+Eine separate, ausdrücklich bestätigte Editoraktion erzeugt dagegen einen
+vollständigen `circuit-group.renumber`-Plan für genau eine Kategorie. Sie
+nummeriert deren Gruppen gemäß aktueller Reihenfolge ab eins und ändert
+Gruppenpräfixe, optionale Gruppen-Schutz-BMK und Stromkreis-BMK gemeinsam;
+die Stromkreisnummer hinter dem letzten Punkt bleibt erhalten.
+Das vorhandene Stromkreis-Drag-Handle kann außerdem genau einen vollständigen
+Stromkreis in eine andere Gruppe derselben Kategorie verschieben. Der atomare
+`circuit.move-group`-Befehl erhält Gerätezeilen und Schutzdaten, setzt die
+Zielposition und vergibt dort die höchste vorhandene Stromkreisnummer plus eins;
+Lücken werden nicht automatisch gefüllt.
+Befüllte Gruppen werden im Editor erst nach einer Warnung mit Anzahl der
+enthaltenen Stromkreise, Gerätezeilen und Gruppenschutzgeräte gelöscht. Der
+Client sendet dafür den vollständigen aktuellen Unterbaum an
+`circuit-group.delete-subtree`; der Server vergleicht ihn innerhalb derselben
+Transaktion mit dem Datenbankstand. Undo stellt Gruppe, Schutzgeräte,
+Stromkreise, Gerätereihen und Verknüpfungs-/Override-Metadaten vollständig
+wieder her.
 `distribution-board.update` versioniert Etage, Netzart und den
 verteilerweiten Gleichzeitigkeitsfaktor gemeinsam und stellt alle Werte über
 dauerhaftes Undo/Redo wieder her. Der Faktor liegt zwischen `0` und `1` und
 ist für bestehende sowie neu angelegte Verteilungen standardmäßig `1`.
-Snapshot-Schema 6 und der portable Projekttransfer enthalten diesen Wert;
-Schema 5 und älter werden mit dem neutralen Faktor `1` hochgestuft.
-Snapshot-Schema 4 enthält bereits Etage und Netzart; Schema 1/2 sowie
-gespeicherte Version-1-Strukturcommands werden ohne erfundene Zuordnung
-hochgestuft. Snapshot-Schema 3 wird mit allen sechs Netzarten als
-Projektauswahl hochgestuft.
-Snapshot-Schema 7 ergänzt Gruppenkategorie und -nummer,
-Verteilerkomponenten sowie die getrennten 1:1-Schutzgerätedaten. Capture,
+Das aktuelle Baseline-Snapshot-Schema enthält den Gleichzeitigkeitsfaktor,
+Gruppenkategorie und -nummer, Verteilerkomponenten sowie die getrennten
+1:1-Schutzgerätedaten. Capture,
 benannte und automatische Snapshots, Wiederherstellung, Undo/Redo und beide
-JSON-Importmodi verwenden denselben vollständigen Zustand. Schema 6 und älter
-bleiben lesbar: Die drei bekannten Abschnittsschlüssel werden deterministisch
-Gruppe 1 zugeordnet, neue Komponenten- und Schutzgerätesammlungen bleiben leer
-und bestehende flache Schutzangaben unverändert erhalten.
-`project-floor.insert` und `project-room.insert` versionieren die Anlage von
-Geschossen und Räumen mit stabilen UUIDs. Die vollständigen Datensätze bilden
-jeweils die persistierte Inverse für Undo/Redo. Ein Geschoss wird durch Undo nur
+JSON-Importmodi verwenden denselben vollständigen Zustand. Vorherige
+Entwicklungsschemas werden nicht mehr eingelesen.
+Persistente Insert-, Update- und Delete-Commands versionieren Anlage,
+Bearbeitung und Löschung von Geschossen und Räumen mit stabilen UUIDs und
+exakten Vorher-/Nachher-Snapshots. Ein Geschoss wird nur
 entfernt, solange ihm weder ein Raum noch eine Verteilung zugeordnet wurde. Ein
-Raum wird nur entfernt,
-solange weder eine CircuitDeviceRow noch ein aufbewahrter Upgrade-Datensatz auf
-ihn verweist. Beide POST-Endpunkte verlangen `expectedRevision`, liefern den
-aktualisierten Historienstand und besitzen keinen direkten Create-Schreibweg
-mehr.
+Raum wird nur entfernt, solange keine CircuitDeviceRow auf ihn verweist. Alle
+Schreibendpunkte verlangen `expectedRevision` und liefern den aktualisierten
+Historienstand.

 ## Projektgeräte

-`ProjectDevice` verwendet ausschließlich die kanonischen Circuit-First-Felder:
-`phaseType`, `powerPerUnit`, `simultaneityFactor`, `cosPhi`, `remark` sowie
-optionale technische und kategorisierende Felder.
+Die Projektgerätekategorie `lighting`, `single_phase` oder `three_phase` ist die
+fachliche Klassifikation und Zielgruppe. `phaseType` ist keine separate
+Benutzereingabe, sondern wird daraus für Spannung, Verknüpfung und spätere
+Dimensionierung abgeleitet.

 Beim Einfügen entsteht eine verknüpfte `CircuitDeviceRow`. Der Anzeigename wird
 kopiert, aber nicht still synchronisiert. Spätere Änderungen am Projektgerät
@@ -400,35 +447,36 @@ Kopieren in ein Projekt erzeugt ein eigenständiges Projektgerät.

 - SQLite ist die aktuell unterstützte Datenbank.
 - Fremdschlüssel werden für jeden Datenbankkontext aktiviert.
- `npm run db:migrate` wendet Drizzle-Migrationen an.
+- `npm run db:migrate` richtet mit der einzelnen Migration `0000` das komplette
+  aktuelle Schema einer leeren Datenbank ein.
 - `npm run db:verify:circuit-schema` prüft erforderliche und entfernte Spalten.
 - `npm run db:backup` erzeugt ein konsistentes und verifiziertes Online-Backup.
- `npm run typecheck:scripts` prüft alle TypeScript-Wartungs- und
-  Upgrade-Skripte mit ihren Anwendungspfaden, ohne Code zu erzeugen.
- Angewendete Migrationen werden niemals nachträglich verändert.
- `db:migrate:legacy-consumers` ist Upgrade-Werkzeug, kein Anwendungspfad.
-  Der fachliche Migrationsdienst kennt nur schmale Reader-/Store-Ports unter
-  `src/domain/ports`; konkrete SQLite-Repositories werden ausschließlich im
-  CLI-Skript zusammengesetzt.
+- `npm run typecheck:scripts` prüft die TypeScript-Wartungsskripte, ohne Code zu
+  erzeugen.
+- Die Baseline ersetzt alle vorigen Entwicklungsmigrationen. Datenbanken,
+  Snapshots und persistierte Commands aus Vor-Baseline-Ständen werden bewusst
+  nicht unterstützt. Ab der ersten veröffentlichten Version sind angewendete
+  Migrationen unveränderlich und Änderungen erfolgen additiv.
 - Allgemeine Circuit-, Gerätezeilen-, CircuitList- und DistributionBoard-
  Repositories stellen im Anwendungspfad nur noch benötigte Leseabfragen bereit.
-  Fachliche Schreibvorgänge liegen in den typisierten Command-Repositories;
-  Upgrade-Schreibvorgänge bleiben in expliziten Migrationsadaptern.
+  Fachliche Schreibvorgänge liegen in den typisierten Command-Repositories.
 - Die vollständige Verteilungs-Testfixture liegt unter
  `tests/support/distribution-board-fixture.ts` und ist kein exportierter
  Produktions-Schreibweg.
- Migration `0024` bildet die additive relationale Grundlage für geschützte
-  Stromkreisgruppen und Verteilerkomponenten. Die drei bestehenden
-  Stromkreisabschnitte erhalten Kategorie und Gruppennummer 1. Separate
-  1:1-Tabellen halten künftig Stromkreis- und Komponenten-Schutzgeräte; die
-  bisherigen flachen Schutzfelder bleiben in dieser Übergangsphase unverändert.
+- Die Baseline bildet die relationale Grundlage für geschützte Stromkreisgruppen
+  und Verteilerkomponenten. Separate
+  1:1-Tabellen halten Stromkreis- und Komponenten-Schutzgeräte. Die früheren
+  flachen Stromkreis-Schutzfelder sind aus der Baseline entfernt.
  Ein triggergeführtes Register erzwingt bereits eine normalisierte,
  stromkreislistenweite BMK-Eindeutigkeit über Stromkreise und
  Verteilerkomponenten. Snapshot- und Transfer-Integration verwenden
-  Snapshot-Schema 7. Persistente Insert/Delete/Update-Commands für
-  veränderliche Verteilerkomponenten sowie CRUD-Commands für leere Gruppen
-  sowie vollständige Gruppensortierung sind integriert; befüllte Unterbäume
-  und UI folgen in abgegrenzten Arbeitspaketen.
+  Snapshot-Schema 1 der Baseline. Persistente Insert/Delete/Update-Commands für
+  veränderliche Verteilerkomponenten, Gruppen einschließlich befüllter
+  Unterbäume sowie vollständige Gruppensortierung sind integriert. Der Editor
+  zeigt die geschützte Struktur an und bearbeitet veränderliche Gruppen- und
+  Fußkomponenten über dedizierte Command-Modale. Gruppenanlage, -umbenennung,
+  -sortierung, explizite Neunummerierung, Same-Category-Stromkreiswechsel,
+  geschütztes Unterbaumlöschen und Stromkreisschutz sind integriert.

 PostgreSQL ist bewusst nicht implementiert. Die Domainregeln und
 Transaktionsgrenzen sollen portabel bleiben; Schema und Betriebsmodell benötigen
@@ -45,10 +45,16 @@ Projekt- oder Kundendaten versehentlich ins Repository. Für einen lokalen
 Testbestand:

 1. In der UI ein Projekt `Demo` anlegen.
-2. Im Projekt eine Verteilung `UV-01` erstellen.
+2. Im Projekt eine Verteilung `UV-01` erstellen. Die Stromkreisliste enthält
+   danach Hauptschalter, Überspannungsableiter und je eine Gruppe für
+   Beleuchtung, 1-phasige und 3-phasige Stromkreise.
 3. Ein Projektgerät mit unkritischen Fantasiewerten anlegen.
-4. Die erzeugte Stromkreisliste öffnen und das Gerät in einen passenden Bereich
+4. Die erzeugte Stromkreisliste öffnen und das Gerät in eine passende Gruppe
   ziehen.
+5. Optional eine zweite Gruppe derselben Kategorie, einen Gruppen-FI und ein
+   zusätzliches Verteilergerät anlegen. Damit lassen sich Gruppensortierung,
+   explizite Neunummerierung, Stromkreiswechsel und persistentes Undo/Redo ohne
+   reale Projekt- oder Kundendaten prüfen.

 Dateien unter `data/` und `data/backups/` dürfen nicht committed werden.

@@ -90,18 +96,19 @@ erneut direkte Schreibmethoden erhalten.

 ## Migrationen

-1. Bestehende lokale Datenbank sichern: `npm run db:backup`.
-2. Schema unter `src/db/schema/` ändern.
-3. `npm run db:generate` ausführen.
-4. Das generierte SQL vollständig prüfen; es darf nur die beabsichtigte Änderung
+1. Schema unter `src/db/schema/` ändern.
+2. `npm run db:generate` ausführen.
+3. Das generierte SQL vollständig prüfen; es darf nur die beabsichtigte Änderung
   enthalten.
-5. Upgrade-/Erhaltungstest ergänzen, wenn Spalten oder Beziehungen geändert
+4. Upgrade-/Erhaltungstest ergänzen, wenn Spalten oder Beziehungen geändert
   werden.
-6. `npm test`, `npm run db:migrate` und
+5. `npm test`, `npm run db:migrate` und
   `npm run db:verify:circuit-schema` ausführen.

-Bereits angewendete SQL-Migrationen dürfen nicht geändert oder neu sortiert
-werden. Korrekturen erfolgen immer über eine neue Migration.
+`0000` ist die saubere Baseline für leere Neuinstallationen. Vor-Baseline-
+Entwicklungsdatenbanken werden nicht aktualisiert. Nach Veröffentlichung der
+ersten Version dürfen angewendete SQL-Migrationen nicht geändert oder neu
+sortiert werden; Korrekturen erfolgen dann immer über eine neue Migration.

 ## Pull-Request-Handoff

@@ -1,137 +0,0 @@
-# Local DB Migration: Circuit-First Schema
-
-This project uses SQLite at `data/leistungsbilanz.db` and Drizzle migrations in `src/db/migrations`.
-
-This document is an upgrade runbook for databases created before the Circuit-First
-cutover. A clean installation only needs the normal `db:migrate` and schema
-verification steps documented in the main README.
-
-## Safe command order
-
-1. Backup local DB (required before schema/data migration)
-
-```bash
-npm run db:backup
-```
-
-The command uses SQLite's online backup API, so committed WAL changes are included
-even while the application is running. It opens the resulting standalone database
-and requires both `PRAGMA integrity_check` and `PRAGMA foreign_key_check` to pass.
-Database backups are operational recovery files and remain separate from the future
-user-visible project version history.
-
-2. Apply pending schema migrations (includes `0008_circuit_first_model`, the additive
-   `0009_project_device_circuit_fields` transition and the post-cutover
-   `0011_project_device_canonical_fields` cleanup)
-
-```bash
-npm run db:migrate
-```
-
-3. Verify circuit-first tables exist
-
-```bash
-npm run db:verify:circuit-schema
-```
-
-4. Backfill default sections for existing `circuit_lists`
-
-```bash
-npm run db:backfill:sections
-```
-
-5. Run legacy consumer -> circuit/device-row migration explicitly
-
-```bash
-npm run db:migrate:legacy-consumers
-```
-
-## Verification SQL
-
-Run these against `data/leistungsbilanz.db`:
-
-```sql
-SELECT name
-FROM sqlite_master
-WHERE type = 'table'
-  AND name IN (
-    'circuit_sections',
-    'circuits',
-    'circuit_device_rows',
-    'legacy_consumer_circuit_migrations',
-    'legacy_consumer_migration_reports'
-  )
-ORDER BY name;
-```
-
-The verification command also checks the circuit-first project-device columns added by migration `0009`.
-
-```sql
-SELECT circuit_list_id, key, prefix, sort_order
-FROM circuit_sections
-ORDER BY circuit_list_id, sort_order;
-```
-
-```sql
-SELECT circuit_list_id, COUNT(*) AS circuits
-FROM circuits
-GROUP BY circuit_list_id;
-```
-
-```sql
-SELECT c.circuit_list_id, COUNT(r.id) AS device_rows
-FROM circuits c
-LEFT JOIN circuit_device_rows r ON r.circuit_id = c.id
-GROUP BY c.circuit_list_id;
-```
-
-## API verification
-
-After the steps above:
-
-`GET /api/projects/:projectId/circuit-lists/:circuitListId/tree`
-
-Expected response shape:
-
-```json
-{
-  "circuitListId": "string",
-  "sections": [
-    {
-      "id": "string",
-      "key": "lighting|single_phase|three_phase|unassigned|...",
-      "displayName": "string",
-      "prefix": "-1F|-2F|-3F|-UF|...",
-      "sortOrder": 10,
-      "circuits": [
-        {
-          "id": "string",
-          "equipmentIdentifier": "-2F1",
-          "displayName": "string",
-          "sortOrder": 10,
-          "isReserve": false,
-          "circuitTotalPower": 1.23,
-          "deviceRows": [
-            {
-              "id": "string",
-              "displayName": "string",
-              "quantity": 1,
-              "powerPerUnit": 0.3,
-              "simultaneityFactor": 1,
-              "rowTotalPower": 0.3
-            }
-          ]
-        }
-      ]
-    }
-  ]
-}
-```
-
-If migrations were not applied, endpoint may return an empty fallback with a warning.
-
-## Visual verification
-
-Manual device rows and multi-device circuits can be created directly in the
-circuit-list editor. The former development scripts for direct database writes
-were removed because they bypassed project revisions and persistent undo/redo.
@@ -84,7 +84,8 @@ Implemented named-snapshot foundation:
  stores the complete project state in one SQLite transaction
 - the versioned payload contains project settings, distribution boards,
  circuit lists, sections, circuits with device rows, project devices, floors
-  and rooms while excluding global and upgrade-only data
+  and rooms while excluding the global device catalog and other
+  non-project-owned data
 - snapshot creation/listing does not create a project revision or affect
  undo/redo eligibility
 - public Create/List endpoints expose metadata but not the logical payload
@@ -93,8 +94,6 @@ Implemented named-snapshot foundation:
 - restore records a new `restore` revision containing both the selected target
  state and the complete pre-restore inverse; undo/redo therefore remains
  available after application restarts
- compatible upgrade-only Consumer links, mappings and reports are preserved
-  separately and are never imported into the logical snapshot payload
 - arbitrary restore payloads are rejected by the generic user-command
  endpoint; only server-stored snapshots can initiate a forward restore
 - the project page provides an initially collapsed snapshot/timeline panel,
@@ -6,9 +6,10 @@ This is a conceptual model for Codex. It is not a final database schema, but the

 A distribution board contains a circuit list.

-A circuit list contains sections.
+A circuit list contains circuit groups. `CircuitSection` is the persisted name
+of that group aggregate.

-A section contains circuits.
+A circuit group contains circuits of one category.

 A circuit contains zero, one or multiple device rows.

@@ -60,29 +61,28 @@ User-facing fields:
 - `section`
 - `displayName` optional
 - `circuitTotalPower`
- `protectionType`
- `protectionRatedCurrent`
- `protectionCharacteristic`
+- `protectionDevice`
 - `cableType`
 - `cableCrossSection`
 - `cableLength`
- `rcdAssignment` optional
 - `terminalDesignation` optional
- `voltage` optional
+- `voltage`, derived from project settings and phase category
 - `controlRequirement` optional, for example DALI or KNX
 - `status` optional
 - `isReserve` optional
 - `remark` optional

+`protectionDevice` is the circuit-owned one-to-one protection configuration.
+It contains the device type, rated current and only the type-dependent values
+such as trip characteristic or residual current. Newly created circuits
+receive the category default defined in the protection catalog.
+
 Circuit-level fields only:

- protection type
- protection rated current
- protection characteristic
+- protection device and all of its technical values
 - cable type
 - cable cross-section
 - cable length
- RCD assignment
 - terminal designation
 - circuit total power

@@ -342,9 +342,8 @@ Implemented foundation:
 - circuit-device-row transaction tests cover both successful commits and forced SQLite rollbacks
 - project-device row synchronization has real multi-row SQLite commit and rollback coverage
 - BMK swaps and section reorder have real SQLite commit and rollback coverage
- the legacy consumer migration service depends only on narrow domain ports;
-  all concrete repositories are composed at the script entry point
- legacy circuit, row, mapping and report writes have real late-failure rollback coverage
+- the former Consumer migration service, mappings and reports were removed with
+  the pre-release database cutover
 - circuit and device-row persistence value mapping is separated from the general repositories
 - obsolete direct Circuit, CircuitDeviceRow, CircuitList, DistributionBoard and
  Project repository writes are removed; integration fixtures live under
@@ -362,8 +361,9 @@ Implemented foundation:
  direct global SQLite access
 - TypeScript maintenance and upgrade scripts have a dedicated no-emit
  typecheck, including all referenced application modules
- the legacy consumer UI and application read/write endpoints are removed after verified data cutover
- retained legacy rows are accessible only through explicit database upgrade tooling
+- the former Consumer UI, API, tables and upgrade tooling are removed
+- migration `0000` is the clean baseline for new installations; pre-baseline
+  development databases are intentionally unsupported
 - project devices no longer persist duplicate legacy power, phase, cosPhi or remark fields

 ## Phase 12: Project Revisions and Persistent Undo / Redo
@@ -559,11 +559,11 @@ PostgreSQL should be introduced when shared multi-user operation, background job

 Goal:

-After the legacy consumer path has been removed, provide one accurate entry point for developers, contributors and LLM-assisted work.
+With the former Consumer path removed, provide one accurate entry point for developers, contributors and LLM-assisted work.

 Timing:

- perform the final rewrite after legacy cutover so the documentation describes only the supported architecture
+- keep the post-cleanup documentation limited to the supported architecture
 - update documentation incrementally during earlier phases, but do not present transitional paths as the long-term design

 README target structure:
@@ -618,7 +618,8 @@ Implemented handoff:

 - README is a concise setup and project entry point without prototype status lists
 - `docs/README.md` separates current, operational, future, specification and archived material
- current runtime, module boundaries and upgrade-only legacy data are documented explicitly
+- current runtime and module boundaries are documented without compatibility
+  paths for unsupported pre-release data formats
 - contributor workflow covers clean databases, safe demo data, migrations, tests and commits
 - development Compose is clearly separated from the currently unsupported production deployment
 - `AGENTS.md` points LLM-assisted work to supported code paths and deferred architecture
@@ -10,15 +10,15 @@ requirements and intended sequencing, not proof of implementation.

 ## Distribution Board Components and Protection Groups

- [ ] Implement the agreed protected circuit-group and distribution-board
+- [x] Implement the agreed protected circuit-group and distribution-board
  component model in phased work packages.
 - [x] Phase A: central protection catalog, validation, defaults and pure grouped
  BMK rules.
- [x] Phase B1: additive relational schema, group backfill, component/protection
-  tables and shared BMK uniqueness.
- [x] Phase B2: snapshot/transfer schema upgrade and deterministic compatibility
-  mapping.
- [x] Phase C1: versioned new-board command with three groups and fixed header
+- [x] Phase B1: relational group, component and protection tables with shared
+  BMK uniqueness.
+- [x] Phase B2: complete snapshot/transfer schema for the supported project
+  state.
+- [x] Phase C1: new-board command with three groups and fixed header
  components.
 - [x] Phase C2a1: persistent insert/delete commands for mutable group
  protection and auxiliary components.
@@ -33,9 +33,18 @@ requirements and intended sequencing, not proof of implementation.
 - [x] Phase D3b: persistent populated-group delete/restore command.
 - [x] Phase E1: tree read model for components, groups and protection devices.
 - [x] Phase E2a: pure header/group/footer structure projection.
- [ ] Phase E2b: render the structure projection in the editor grid.
- [ ] Phase E: editor projection and editing.
- [ ] Phase F: documentation and full GUI verification.
+- [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.
+- [x] Phase E3b2a: persistent circuit-protection update command.
+- [x] Phase E3b2b: circuit-protection defaults on insert and editor modal.
+- [x] Phase E4a: persistent same-category group reorder controls.
+- [x] Phase E4b: explicit group renumber, circuit moves and populated-delete warning.
+  - [x] Explicit same-category group renumbering updates prefixes and all child BMK atomically.
+  - [x] Single-circuit moves between same-category groups with automatic next-free BMK assignment.
+  - [x] Populated-group delete warning and explicit subtree deletion.
+- [x] Phase E: editor projection and editing.
+- [x] Phase F: documentation and full GUI verification.
 - [ ] Keep full electrical sizing and cable-dimensioning rules separate until
  the planner supplies the calculation requirements.
 - Detailed specification:
@@ -43,22 +52,22 @@ requirements and intended sequencing, not proof of implementation.

 ## First Release Baseline

-Complete this immediately before the first supported release, once the schema
-and initial feature set are frozen:
+The pre-release cleanup established the following compatibility boundary:

- Decide explicitly whether pre-release databases, portable JSON exports,
-  logical snapshots and persisted command histories remain supported.
- Create one clean baseline migration that builds the complete release schema
-  on an empty database.
- Replace the active development migration chain and Drizzle metadata only if
-  no released installation depends on it.
- Remove upgrade-only database, snapshot and command compatibility code only
-  for formats that are explicitly declared unsupported.
- Preserve the pre-release migration history in Git history or a release tag.
- Verify installation, migrations, application startup and core workflows
-  against a completely empty database.
- Mark the resulting compatibility boundary with the first release tag.
- Treat every migration published after that release as immutable.
+- [x] Pre-release databases, portable JSON exports, logical snapshots and
+  persisted command histories are explicitly unsupported.
+- [x] Migration `0000` builds the complete supported schema on an empty
+  database.
+- [x] The development migration chain and Drizzle metadata were replaced
+  before any supported release depended on them.
+- [x] Upgrade-only database, snapshot and command compatibility paths were
+  removed.
+- [x] Pre-cleanup development history remains available through Git history.
+- [x] Clean installation, migration, startup and core workflows were verified
+  against an empty database.
+- [ ] Mark this compatibility boundary with the first supported release tag.
+- After that release, every published migration is immutable and later schema
+  changes must use new additive migrations.

 ## Project History

@@ -100,9 +109,9 @@ and initial feature set are frozen:
  device rows with a valid phase are three-phase.
 - [x] Changing project voltage settings updates all project devices and circuits
  atomically in the same persistent Undo/Redo step.
- [x] Database migration `0019` and snapshot schema version `5` normalize older
-  stored values. Version-four and older imports remain supported and are
-  normalized while being upgraded.
+- [x] Baseline migration `0000` and project-state schema version `1` store only
+  the canonical derived values. Pre-release imports are intentionally
+  unsupported.

 ## Circuit List Power Summary

@@ -2,10 +2,10 @@

 ## Status

-This document defines the agreed target behavior for distribution-board
-components, protected circuit groups and circuit protection devices. Phase A
-and the relational Phase-B1 foundation are implemented; later sections remain
-requirements and are not proof of runtime or editor support.
+This document records the agreed and implemented behavior for
+distribution-board components, protected circuit groups and circuit
+protection devices. Delivery phases A through F are complete. The current
+runtime paths are documented in `docs/current-architecture.md`.

 Full rule-based protection and cable sizing is deliberately deferred. This
 phase establishes the structure and manually selected technical values that a
@@ -33,7 +33,7 @@ later calculation and warning engine will evaluate.
 - channel-level relationships between actors and controlled circuits
 - PostgreSQL or multi-user operation

-## Existing Model Audit
+## Implemented Model Boundary

 ### Keep

@@ -43,33 +43,28 @@ later calculation and warning engine will evaluate.
 - Circuit-level load, cable and control fields remain circuit-owned.
 - Existing stable UUIDs, project revisions, snapshots and persistent Undo/Redo
  remain authoritative.
- `CircuitSection` remains the migration starting point for a protected circuit
+- `CircuitSection` is the persisted representation of a protected circuit
  group.
 - Grid projection remains separate from persisted domain structure.

 ### Change

- A `CircuitSection` gains an explicit category and group number and represents
+- A `CircuitSection` has an explicit category and group number and represents
  one protected circuit group.
- Circuit protection changes from loosely related flat strings to an explicit
+- Circuit protection uses an explicit
  one-to-one protection-device model.
 - Distribution-board components become independent BMK-bearing list entries.
 - Equipment-identifier uniqueness covers circuits and all distribution-board
  components in the complete circuit list.
 - Moving a circuit to another group of the same category atomically assigns the
  next identifier of the target group.
- New distribution boards create three default groups rather than treating the
-  optional unassigned compatibility section as a normal fourth group.
+- New distribution boards create exactly three default groups.

-### Remove Eventually
+### Remaining Model Cleanup

- hard-coded assumptions that each category has exactly one section
- numbering that only understands `prefix + integer`
- free-text protection-device combinations that cannot be validated
- `rcdAssignment` as a substitute for an explicit group relationship
-
-Removal happens only after migrated state, snapshots, commands and the editor
-use the replacement model.
+- The older optional `rcdAssignment` circuit field still exists separately
+  from the explicit group relationship. Removing it requires its own reviewed
+  domain and UI change; it is not a compatibility path for pre-release data.

 ## Target Domain Structure

@@ -463,7 +458,7 @@ Every command must:
 - commit the domain mutation, revision and history transition atomically
 - remain undoable and redoable after application restart

-## Snapshot and Transfer Compatibility
+## Snapshot and Transfer Boundary

 The supported logical project snapshot and portable JSON transfer must include:

@@ -472,28 +467,15 @@ The supported logical project snapshot and portable JSON transfer must include:
 - circuit protection-device state
 - all new component relationships and sort positions

-Introducing the model requires a snapshot-schema version increase and explicit
-upgraders for supported older payloads.
+The clean pre-release baseline uses project-state schema version `1`. It
+contains the complete supported structure above and is shared by logical
+snapshots, restore, Undo/Redo and portable JSON transfer. Payloads from earlier
+development schemas are intentionally unsupported and rejected before any
+write.

-Database migration rules:
-
- preserve all existing stable UUIDs
- preserve existing circuit equipment identifiers during schema migration
- map the existing lighting, single-phase and three-phase sections to group 1
-  of the respective category
- preserve an existing unassigned section only when required by existing data;
-  it is not created for a new distribution board
- preserve existing flat circuit protection values when creating the new
-  one-to-one protection state
- do not silently replace an existing protection selection with a new default
- allow legacy identifiers to remain until an explicit, collision-safe
-  conversion or renumber action is approved
-
-New defaults apply to newly created circuits and boards, not as an implicit
-rewrite of existing planning data.
-
-Historical persisted commands and snapshots that remain in the supported
-compatibility window must still deserialize and execute after the migration.
+Migration `0000` creates the complete relational model on an empty database.
+New defaults apply when boards, groups or circuits are created; they never
+silently overwrite a planner's later selection.

 ## Later Sizing and Warning Engine

@@ -543,7 +525,7 @@ Acceptance:
 - invalid rating/type/field combinations are rejected
 - defaults produce the exact agreed values

-### B. Persistence and Compatibility Model
+### B. Persistence and Snapshot Model

 Status: Complete.

@@ -551,44 +533,31 @@ Status: Complete.
 - add distribution-board component persistence
 - add one-to-one circuit protection persistence
 - implement shared BMK uniqueness
- generate and inspect one additive migration
- add snapshot/transfer schema upgrade
- preserve existing identifiers and protection values
+- create the complete relational baseline schema
+- include the model in snapshots and portable transfers
+- preserve identifiers and protection values within supported project state

-Implemented in B1:
+Implemented persistence:

- additive migration `0024` adds group identity to circuit sections and maps
-  the three established sections to group 1 without changing UUIDs
+- baseline migration `0000` creates group identity, components and protection
+  state directly for clean installations
 - separate component and circuit/component protection tables preserve the
  one-to-one ownership boundaries
 - a trigger-maintained circuit-list registry rejects normalized BMK collisions
  across circuits and distribution-board components
- the existing flat circuit protection fields remain untouched until their
-  deterministic snapshot/runtime transition is implemented
- clean and populated pre-migration databases are covered by migration tests
- 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
+- snapshot schema version `1` 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,
+- snapshots reject invalid ownership, duplicate group numbers,
  cross-entity BMKs and invalid protection configurations before persistence

 Acceptance:

- a current database migrates without data loss
 - an empty database creates the complete schema
- old supported snapshots and transfers upgrade deterministically
+- unsupported pre-release snapshots and transfers are rejected before writing
 - BMK collisions across circuits and components are rejected

 ### C. Persistent Commands and Board Defaults
@@ -602,14 +571,13 @@ Status: Complete.

 Implemented in C1:

- `distribution-board.insert` schema version 3 carries stable UUIDs for three
+- `distribution-board.insert` schema version `1` 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
+- unsupported command schema versions are rejected

 Implemented in C2a1:

@@ -739,8 +707,7 @@ Acceptance:

 ### E. Editor Projection and Editing

-Status: In progress. The complete tree read model E1 and pure structural
-projection E2a are complete. Grid rendering and editing remain pending.
+Status: Complete.

 - render fixed header components
 - render group components and circuit blocks
@@ -749,7 +716,7 @@ projection E2a are complete. Grid rendering and editing remain pending.
 - add type-dependent protection editing
 - keep spreadsheet selection, keyboard and drag behavior coherent

-Implemented in E1/E2a:
+Implemented in E1/E2a/E2b/E3a:

 - the tree response exposes fixed header, group and auxiliary footer
  components plus both one-to-one protection layers
@@ -759,6 +726,43 @@ Implemented in E1/E2a:
  circuit blocks and free placeholder together
 - empty groups remain visible and circuit device rows remain owned by their
  circuit block
+- the editor renders fixed header, group protection and auxiliary footer
+  components as read-only full-width rows
+- structural component rows are excluded from spreadsheet cell navigation,
+  insertion and deletion commands until their dedicated editing controls exist
+- group headings offer at most one optional upstream protection device and one
+  optional group RCD; the agreed group-RCD default is applied only when it is
+  created
+- mutable group protection and auxiliary footer components use labeled modals,
+  type-dependent protection fields and persistent project commands
+- fixed main-switch and surge-protection header components remain read-only
+- users can create a group in any supported category; its number is the
+  category's highest existing number plus one and its prefix is generated
+- group editing changes only the display name; category, number, prefix and
+  child BMKs remain stable
+- an exactly empty group can be removed through the compact persistent group
+  command
+- `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
+- newly inserted circuits and placeholder targets carry the category-specific
+  default protection in their complete atomic snapshot
+- circuit deletion and restoration preserve the exact 1:1 protection row
+  together with the circuit and all device rows
+- the editor modal exposes only fields valid for the selected protection type;
+  the old flat protection columns now project the new 1:1 data read-only
+- group controls move a group only to the adjacent peer of the same category;
+  the complete list order is one persistent command and no number or BMK changes
+- explicit category-wide group renumbering follows the visible persisted group
+  order, updates every affected prefix and child BMK atomically and preserves
+  outgoing-circuit suffixes
+- dragging one circuit into another group of the same category moves the
+  complete circuit and assigns the highest target suffix plus one; same-group
+  multi-circuit drag remains a pure reorder
+- populated-group deletion shows the affected circuit, device-row and group
+  protection counts before sending the complete subtree to the guarded
+  delete/restore command

 Acceptance:

@@ -769,8 +773,12 @@ Acceptance:

 ### F. Documentation and Full Verification

+Status: Complete. Documentation, automated verification and the agreed GUI
+checklist are complete.
+
 - update current architecture, API and interaction documentation
- update demo/sample data
+- update the safe local demo-data instructions; no versioned customer-like
+  seed data is introduced
 - run focused domain and transaction tests
 - run the complete required test, build and type-check suite
 - perform the agreed GUI test checklist
@@ -778,13 +786,13 @@ Acceptance:
 Acceptance:

 - documentation distinguishes implemented behavior from later sizing
- clean install and migrated database both work
+- clean installation and baseline migration work
 - snapshots, JSON transfer and Undo/Redo cover all new state

 ## Risks and Mitigations

- Mixed legacy and grouped BMKs:
-  preserve old identifiers and provide an explicit conversion path.
+- Incorrect implicit BMK changes:
+  preserve identifiers during sorting and require explicit renumbering.
 - Cross-entity BMK collisions:
  enforce one transaction-level uniqueness boundary for the complete list.
 - Partial destructive writes:
@@ -795,17 +803,19 @@ Acceptance:
  use one shared typed catalog for UI, API and domain validation.
 - Silent planning changes:
  apply defaults only on creation and keep later recommendations explicit.
- Snapshot incompatibility:
-  version payloads and test every supported upgrade path.
+- Future snapshot evolution:
+  introduce a new explicit schema version and upgrader only after defining its
+  supported compatibility window.

-## Open Implementation Decisions
+## Resolved Implementation Decisions

-These decisions may be resolved during the relevant delivery phase without
-changing the agreed domain behavior:
-
- exact relational implementation of the shared BMK ownership boundary
- presentation of group ownership through indentation, headings or a column
- filter behavior for structural component rows
- explicit UI for converting retained legacy identifiers to grouped numbering
- whether fixed header components become editable beyond name and BMK in this
-  phase
+- a trigger-maintained circuit-list registry enforces shared BMK uniqueness
+  across circuits and distribution-board components
+- group headings and full-width structural rows show ownership without adding
+  a permanent group column
+- structural component rows remain outside editable-cell filtering and
+  spreadsheet navigation; circuit filtering continues to preserve complete
+  circuit blocks
+- explicit group renumbering updates grouped identifiers collision-safely
+- fixed header components remain read-only; mutable group and auxiliary
+  components use their dedicated modals
@@ -15,14 +15,12 @@
    "build:web": "next build",
    "typecheck:scripts": "tsc --noEmit -p tsconfig.scripts.json",
    "start": "node dist/server/index.js",
-    "test": "tsx --test tests/protection-device.test.ts tests/distribution-board-component.test.ts tests/distribution-board-component-schema-migration.test.ts tests/circuit-group-numbering.test.ts tests/project-device-schema.test.ts tests/project-device-schema-migration.test.ts tests/project-device-placement.service.test.ts tests/project-device-sync.service.test.ts tests/legacy-consumer-migration-planner.test.ts tests/legacy-consumer-migration.service.test.ts tests/legacy-consumer-migration.repository.test.ts tests/circuit-numbering.service.test.ts tests/circuit-power-calculation.test.ts tests/circuit-tree.controller.test.ts tests/circuit-editor-history.test.ts tests/circuit-grid-insertion.test.ts tests/circuit-grid-safety.test.ts tests/circuit-grid-model.test.ts tests/circuit-structure-command.test.ts tests/circuit-device-row-move-command.test.ts tests/circuit-section-reorder-command.test.ts tests/circuit-section-renumber-command.test.ts tests/circuit-grid-projection.test.ts tests/distribution-board-structure-project-command.repository.test.ts tests/project-location-structure-project-command.repository.test.ts tests/project-device-project-command.repository.test.ts tests/project-device-structure-project-command.repository.test.ts tests/project-device-row-sync-project-command.repository.test.ts tests/circuit-section-reorder-project-command.repository.test.ts tests/circuit-section-renumber-project-command.repository.test.ts tests/project-command.model.test.ts tests/project-revision.persistence.test.ts tests/circuit-project-command.repository.test.ts tests/circuit-structure-project-command.repository.test.ts tests/circuit-device-row-project-command.repository.test.ts tests/circuit-device-row-structure-project-command.repository.test.ts tests/circuit-device-row-move-project-command.repository.test.ts tests/project-history.repository.test.ts tests/project-history-timeline.test.ts tests/project-version-history.test.ts tests/project-overview-import.test.ts tests/project-settings-project-command.repository.test.ts tests/project-state-snapshot.test.ts tests/project-snapshot-policy.test.ts tests/project-snapshot.repository.test.ts tests/project-state-restore-command.repository.test.ts tests/project-command.service.test.ts tests/database-backup.test.ts",
-    "test:watch": "tsx --watch --test tests/protection-device.test.ts tests/distribution-board-component.test.ts tests/distribution-board-component-schema-migration.test.ts tests/circuit-group-numbering.test.ts tests/project-device-schema.test.ts tests/project-device-schema-migration.test.ts tests/project-device-placement.service.test.ts tests/project-device-sync.service.test.ts tests/legacy-consumer-migration-planner.test.ts tests/legacy-consumer-migration.service.test.ts tests/legacy-consumer-migration.repository.test.ts tests/circuit-numbering.service.test.ts tests/circuit-power-calculation.test.ts tests/circuit-tree.controller.test.ts tests/circuit-editor-history.test.ts tests/circuit-grid-insertion.test.ts tests/circuit-grid-safety.test.ts tests/circuit-grid-model.test.ts tests/circuit-structure-command.test.ts tests/circuit-device-row-move-command.test.ts tests/circuit-section-reorder-command.test.ts tests/circuit-section-renumber-command.test.ts tests/circuit-grid-projection.test.ts tests/distribution-board-structure-project-command.repository.test.ts tests/project-location-structure-project-command.repository.test.ts tests/project-device-project-command.repository.test.ts tests/project-device-structure-project-command.repository.test.ts tests/project-device-row-sync-project-command.repository.test.ts tests/circuit-section-reorder-project-command.repository.test.ts tests/circuit-section-renumber-project-command.repository.test.ts tests/project-command.model.test.ts tests/project-revision.persistence.test.ts tests/circuit-project-command.repository.test.ts tests/circuit-structure-project-command.repository.test.ts tests/circuit-device-row-project-command.repository.test.ts tests/circuit-device-row-structure-project-command.repository.test.ts tests/circuit-device-row-move-project-command.repository.test.ts tests/project-history.repository.test.ts tests/project-history-timeline.test.ts tests/project-version-history.test.ts tests/project-overview-import.test.ts tests/project-settings-project-command.repository.test.ts tests/project-state-snapshot.test.ts tests/project-snapshot-policy.test.ts tests/project-snapshot.repository.test.ts tests/project-state-restore-command.repository.test.ts tests/project-command.service.test.ts tests/database-backup.test.ts",
+    "test": "node scripts/run-tests.mjs",
+    "test:watch": "node scripts/run-tests.mjs --watch",
    "db:generate": "drizzle-kit generate",
    "db:migrate": "drizzle-kit migrate",
    "db:backup": "tsx scripts/db-backup.ts",
-    "db:verify:circuit-schema": "node scripts/db-verify-circuit-schema.js",
-    "db:backfill:sections": "tsx scripts/db-backfill-sections.ts",
-    "db:migrate:legacy-consumers": "tsx scripts/db-migrate-legacy-consumers.ts"
+    "db:verify:circuit-schema": "node scripts/db-verify-circuit-schema.js"
  },
  "keywords": [],
  "author": "",
@@ -1,26 +0,0 @@
-import { db } from "../src/db/client.js";
-import { CircuitListRepository } from "../src/db/repositories/circuit-list.repository.js";
-import { CircuitSectionRepository } from "../src/db/repositories/circuit-section.repository.js";
-import { ProjectRepository } from "../src/db/repositories/project.repository.js";
-
-const projectRepository = new ProjectRepository(db);
-const circuitListRepository = new CircuitListRepository(db);
-const circuitSectionRepository = new CircuitSectionRepository(db);
-
-async function run() {
-  const projects = await projectRepository.list();
-  let totalLists = 0;
-  for (const project of projects) {
-    const lists = await circuitListRepository.listByProject(project.id);
-    for (const list of lists) {
-      await circuitSectionRepository.createDefaults(list.id);
-      totalLists += 1;
-    }
-  }
-  console.log(`Section backfill done for ${totalLists} circuit list(s).`);
-}
-
-run().catch((error) => {
-  console.error("Section backfill failed:", error);
-  process.exit(1);
-});
@@ -1,61 +0,0 @@
-import { db } from "../src/db/client.js";
-import { CircuitRepository } from "../src/db/repositories/circuit.repository.js";
-import { CircuitListRepository } from "../src/db/repositories/circuit-list.repository.js";
-import { CircuitSectionRepository } from "../src/db/repositories/circuit-section.repository.js";
-import { LegacyConsumerMigrationRepository } from "../src/db/repositories/legacy-consumer-migration.repository.js";
-import { ProjectRepository } from "../src/db/repositories/project.repository.js";
-import { RoomRepository } from "../src/db/repositories/room.repository.js";
-import { LegacyConsumerMigrationService } from "../src/domain/services/legacy-consumer-migration.service.js";
-
-const projectRepository = new ProjectRepository(db);
-const circuitListRepository = new CircuitListRepository(db);
-const migrationRepository = new LegacyConsumerMigrationRepository(db);
-const migrationService = new LegacyConsumerMigrationService({
-  circuitListReader: circuitListRepository,
-  sectionStore: new CircuitSectionRepository(db),
-  circuitReader: new CircuitRepository(db),
-  roomReader: new RoomRepository(db),
-  migrationStore: migrationRepository,
-});
-
-async function run() {
-  const projects = await projectRepository.list();
-  const reports = [];
-
-  for (const project of projects) {
-    const lists = await circuitListRepository.listByProject(project.id);
-    for (const list of lists) {
-      const report = await migrationService.migrateCircuitList(project.id, list.id);
-      reports.push({
-        projectId: project.id,
-        circuitListId: list.id,
-        legacyConsumerCount: report.legacyConsumerCount,
-        createdCircuitCount: report.createdCircuitCount,
-        createdDeviceRowCount: report.createdDeviceRowCount,
-        generatedIdentifiers: report.generatedIdentifiers.length,
-        unassignedRows: report.unassignedRows.length,
-      });
-    }
-  }
-
-  const unmigratedConsumers =
-    await migrationRepository.listUnmigratedConsumers();
-  if (unmigratedConsumers.length > 0) {
-    const withoutCircuitList = unmigratedConsumers.filter(
-      (consumer) => !consumer.circuitListId
-    ).length;
-    throw new Error(
-      `Cutover verification failed: ${unmigratedConsumers.length} legacy consumer(s) remain unmigrated` +
-        ` (${withoutCircuitList} without a circuit list).`
-    );
-  }
-
-  console.log("Legacy consumer migration summary:");
-  console.table(reports);
-  console.log("Cutover verification passed: all legacy consumers are mapped.");
-}
-
-run().catch((error) => {
-  console.error("Legacy consumer migration failed:", error);
-  process.exit(1);
-});
@@ -12,8 +12,6 @@ const requiredTables = [
  "circuit_protection_devices",
  "distribution_board_components",
  "distribution_board_component_protection_devices",
-  "legacy_consumer_circuit_migrations",
-  "legacy_consumer_migration_reports",
 ];

 const tablePlaceholders = requiredTables.map(() => "?").join(", ");
@@ -57,6 +55,14 @@ const circuitColumns = new Set(
  db.prepare("PRAGMA table_info(circuits)").all().map((column) => column.name)
 );
 const missingCircuitColumns = requiredCircuitColumns.filter((name) => !circuitColumns.has(name));
+const removedCircuitColumns = [
+  "protection_type",
+  "protection_rated_current",
+  "protection_characteristic",
+];
+const remainingRemovedCircuitColumns = removedCircuitColumns.filter((name) =>
+  circuitColumns.has(name)
+);
 const requiredCircuitSectionColumns = ["category", "group_number"];
 const circuitSectionColumns = new Set(
  db
@@ -164,6 +170,14 @@ if (missingCircuitColumns.length > 0) {
  process.exit(1);
 }

+if (remainingRemovedCircuitColumns.length > 0) {
+  console.error(
+    "Transitional circuit protection columns still present:",
+    remainingRemovedCircuitColumns.join(", ")
+  );
+  process.exit(1);
+}
+
 if (missingCircuitSectionColumns.length > 0) {
  console.error(
    "Missing circuit-section columns:",
@@ -0,0 +1,30 @@
+import { readdirSync } from "node:fs";
+import { spawnSync } from "node:child_process";
+import path from "node:path";
+
+const testFiles = readdirSync(path.resolve("tests"), {
+  withFileTypes: true,
+})
+  .filter((entry) => entry.isFile() && entry.name.endsWith(".test.ts"))
+  .map((entry) => path.join("tests", entry.name))
+  .sort();
+
+if (testFiles.length === 0) {
+  throw new Error("No TypeScript test files found.");
+}
+
+const watch = process.argv.includes("--watch");
+const result = spawnSync(
+  process.execPath,
+  [
+    "--import",
+    "tsx",
+    "--test",
+    "--test-concurrency=1",
+    ...(watch ? ["--watch"] : []),
+    ...testFiles,
+  ],
+  { stdio: "inherit" }
+);
+
+process.exit(result.status ?? 1);
@@ -1,9 +1,303 @@
+/* Design-System "Petrol · Volt · Kupfer" v2.1 (H:\design-system-econsult.md),
+   projektübergreifendes Update für die Econsult-Familie (siehe elt-planung-suite).
+   Bootstrap bleibt Basis für Formulare/Tabellen/Modals; wir tönen die
+   vorhandenen Bootstrap-Komponenten über deren eigene --bs-btn-*-Variablen
+   um (globals.css lädt nach bootstrap.min.css, gleiche Spezifität gewinnt
+   per Ladereihenfolge) statt Bootstrap zu ersetzen. */
+:root {
+  --color-primary: #1c3f52; /* Petrol */
+  --color-primary-dark: #0f2733; /* Petrol Dark */
+  --color-primary-deep: #0a1920; /* Petrol Deep */
+  --color-accent: #4e7e93; /* Petrol Light */
+  --color-accent-pale: #9dbac9; /* Petrol Pale */
+  --color-signal: #3fa66b; /* Volt - generelle aktiv/positiv-Farbe */
+  --color-signal-dark: #237a47;
+  --color-attention: #c97a3b; /* Kupfer - bewusst selten, "braucht Aufmerksamkeit" */
+  --color-attention-dark: #9c5a26;
+  --color-ink: #182229; /* Graphite */
+  --color-ink-soft: #59666d; /* Slate */
+  --color-bg: #ffffff;
+  --color-surface: #f1f2ee; /* Fog */
+  --color-border: #dee2dc;
+  --color-danger: #b04035;
+  --color-danger-bg: #f7e6e3;
+  --color-warn: #a9791e;
+
+  --font-head: system-ui, "Segoe UI", "Helvetica Neue", sans-serif;
+  --font-body: system-ui, "Segoe UI", "Helvetica Neue", sans-serif;
+
+  --space-xs: 4px;
+  --space-sm: 8px;
+  --space-md: 16px;
+  --space-lg: 24px;
+  --space-xl: 40px;
+
+  --radius: 12px;
+}
+
+html {
+  scroll-behavior: smooth;
+}
+
 body {
-  background-color: #f5f7fb;
+  background-color: var(--color-surface);
+  color: var(--color-ink);
+}
+
+a {
+  color: var(--color-primary);
+}
+
+/* ── Bootstrap-Einfärbung auf Petrol/Volt/Kupfer ────────────────────────── */
+
+.btn-primary {
+  --bs-btn-bg: var(--color-primary);
+  --bs-btn-border-color: var(--color-primary);
+  --bs-btn-hover-bg: var(--color-primary-dark);
+  --bs-btn-hover-border-color: var(--color-primary-dark);
+  --bs-btn-active-bg: var(--color-primary-deep);
+  --bs-btn-active-border-color: var(--color-primary-deep);
+  --bs-btn-disabled-bg: var(--color-primary);
+  --bs-btn-disabled-border-color: var(--color-primary);
+}
+
+.btn-outline-primary {
+  --bs-btn-color: var(--color-primary);
+  --bs-btn-border-color: var(--color-primary);
+  --bs-btn-hover-bg: var(--color-primary);
+  --bs-btn-hover-border-color: var(--color-primary);
+  --bs-btn-active-bg: var(--color-primary-dark);
+  --bs-btn-active-border-color: var(--color-primary-dark);
+}
+
+.btn-success,
+.btn-outline-success {
+  --bs-btn-bg: var(--color-signal);
+  --bs-btn-border-color: var(--color-signal);
+  --bs-btn-color: #fff;
+  --bs-btn-hover-bg: var(--color-signal-dark);
+  --bs-btn-hover-border-color: var(--color-signal-dark);
+  --bs-btn-active-bg: var(--color-signal-dark);
+  --bs-btn-active-border-color: var(--color-signal-dark);
+}
+
+.btn-outline-success {
+  --bs-btn-bg: transparent;
+  --bs-btn-color: var(--color-signal-dark);
+  --bs-btn-hover-color: #fff;
+}
+
+.form-control:focus,
+.form-select:focus {
+  border-color: var(--color-accent);
+  box-shadow: 0 0 0 0.25rem rgba(28, 63, 82, 0.15);
+}
+
+.form-check-input:checked {
+  background-color: var(--color-primary);
+  border-color: var(--color-primary);
+}
+
+.text-bg-secondary {
+  background-color: var(--color-surface) !important;
+  color: var(--color-ink-soft) !important;
+}
+
+.alert-success {
+  --bs-alert-color: var(--color-signal-dark);
+  --bs-alert-bg: #eaf6f0;
+  --bs-alert-border-color: #b6e2ce;
+}
+
+/* ── App-Shell / Seitenleiste (nur auf der Projektseite) ────────────────── */
+
+.app-shell {
+  display: grid;
+  grid-template-columns: 260px 1fr;
+  min-height: 100vh;
+}
+
+.sidebar {
+  background: linear-gradient(
+    160deg,
+    var(--color-primary-deep) 0%,
+    var(--color-primary-dark) 45%,
+    var(--color-primary) 100%
+  );
+  color: #fff;
+  display: flex;
+  flex-direction: column;
+  position: sticky;
+  top: 0;
+  height: 100vh;
+  overflow-y: auto;
+}
+
+.sidebar-brand {
+  padding: 22px 22px 18px;
+  border-bottom: 1px solid rgba(255, 255, 255, 0.12);
+}
+
+.sidebar-wordmark {
+  font-size: 1.2rem;
+  font-weight: 700;
+  color: #fff;
+}
+
+.sidebar-bar {
+  height: 3px;
+  background: linear-gradient(90deg, var(--color-signal), var(--color-attention));
+  margin-top: 9px;
+  width: 42px;
+  border-radius: 2px;
+}
+
+.sidebar-tag {
+  font-size: 0.72rem;
+  letter-spacing: 0.13em;
+  text-transform: uppercase;
+  color: var(--color-accent-pale);
+  margin-top: 10px;
+}
+
+.sidebar-nav {
+  display: flex;
+  flex-direction: column;
+  gap: 2px;
+  padding: 12px;
+}
+
+.sidebar-section-label {
+  font-size: 0.66rem;
+  letter-spacing: 0.1em;
+  text-transform: uppercase;
+  color: rgba(199, 214, 224, 0.7);
+  padding: 16px 14px 4px;
+}
+
+.sidebar-link {
+  display: flex;
+  align-items: center;
+  gap: 10px;
+  padding: 10px 14px;
+  border-radius: 8px;
+  color: #c7d6e0;
+  text-decoration: none;
+  font-size: 0.92rem;
+  font-weight: 500;
+  border: 0;
+  background: transparent;
+  width: 100%;
+  text-align: left;
+  cursor: pointer;
+}
+
+.sidebar-link:hover {
+  background: rgba(255, 255, 255, 0.08);
+  color: #fff;
+  text-decoration: none;
+}
+
+.sidebar-link.active {
+  background: rgba(255, 255, 255, 0.14);
+  color: #fff;
+  box-shadow: inset 3px 0 0 var(--color-signal);
+}
+
+.sidebar-icon {
+  width: 1.1em;
+  display: inline-flex;
+  justify-content: center;
+}
+
+.app-shell-content {
+  width: 100%;
+  min-width: 0;
+}
+
+.page-header {
+  display: flex;
+  align-items: flex-end;
+  justify-content: space-between;
+  gap: var(--space-md);
+  margin-bottom: var(--space-lg);
+  flex-wrap: wrap;
+}
+
+.page-header h1 {
+  font-size: 1.5rem;
+  font-weight: 700;
+  color: var(--color-primary);
+}
+
+.kicker {
+  font-size: 0.72rem;
+  letter-spacing: 0.12em;
+  text-transform: uppercase;
+  color: var(--color-accent);
+  margin-bottom: 2px;
+  font-weight: 600;
+}
+
+/* ── KPI-Kacheln ─────────────────────────────────────────────────────── */
+
+.kpi-grid {
+  display: grid;
+  grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
+  gap: var(--space-md);
+  margin-bottom: var(--space-lg);
+}
+
+.kpi {
+  background: var(--color-bg);
+  border: 1px solid var(--color-border);
+  border-radius: 9px;
+  padding: 13px 15px;
+  display: block;
+  color: inherit;
+  text-decoration: none;
+  transition: box-shadow 0.15s, transform 0.15s;
+}
+
+a.kpi:hover {
+  color: inherit;
+  text-decoration: none;
+  box-shadow: 0 3px 8px rgba(15, 39, 51, 0.07), 0 16px 32px -14px rgba(15, 39, 51, 0.28);
+  transform: translateY(-1px);
+}
+
+.kpi-label {
+  font-size: 0.66rem;
+  letter-spacing: 0.06em;
+  text-transform: uppercase;
+  color: var(--color-ink-soft);
+  margin-bottom: var(--space-xs);
+  font-weight: 600;
+  display: flex;
+  align-items: center;
+  gap: 6px;
+}
+
+.kpi-value {
+  font-size: 1.2rem;
+  font-weight: 700;
+  line-height: 1.1;
+  color: var(--color-primary);
 }

 .card {
-  border-radius: 0.5rem;
+  border-radius: var(--radius);
+  border-top: 3px solid var(--color-primary);
+  box-shadow:
+    0 1px 2px rgba(15, 39, 51, 0.05),
+    0 10px 24px -14px rgba(15, 39, 51, 0.22);
+}
+
+.card-header {
+  font-weight: 700;
+  color: var(--color-primary);
+  background: var(--color-bg);
+  border-bottom: 1px solid var(--color-border);
 }

 .table td input.form-control-sm,
@@ -11,35 +305,6 @@ body {
  min-width: 8rem;
 }

-.circuit-tree-table .section-row td {
-  background: #e9eef8;
-  border-top: 2px solid #c6d3ea;
-  font-weight: 600;
-}
-
-.circuit-tree-table .summary-row td {
-  background: #f5f8fd;
-  font-weight: 600;
-}
-
-.circuit-tree-table .device-row td {
-  background: #ffffff;
-}
-
-.circuit-tree-table .reserve-row td {
-  background: #f8fbff;
-}
-
-.circuit-tree-table .placeholder-row td {
-  background: #f7f7f7;
-  color: #6c757d;
-  font-style: italic;
-}
-
-.circuit-tree-table .indented-cell {
-  padding-left: 1.5rem;
-}
-
 .tree-editor-shell {
  display: flex;
  flex-direction: column;
@@ -657,6 +922,57 @@ body {
  font-weight: 600;
 }

+.tree-grid .structure-component-row td {
+  padding: 0.38rem 0.6rem;
+  border-bottom-color: #d8dee9;
+}
+
+.tree-grid .structure-component-row.headerComponent td {
+  background: #e2e8f0;
+}
+
+.tree-grid .structure-component-row.groupComponent td {
+  background: #f8fafc;
+}
+
+.tree-grid .structure-component-row.footerComponent td {
+  background: #f1f5f9;
+}
+
+.tree-grid .structure-component-content {
+  display: flex;
+  align-items: baseline;
+  gap: 0.75rem;
+  min-width: 0;
+}
+
+.tree-grid .structure-component-content strong {
+  flex: 0 0 auto;
+  font-variant-numeric: tabular-nums;
+}
+
+.tree-grid .structure-component-protection {
+  color: #475569;
+  font-size: 0.78rem;
+}
+
+.tree-grid .structure-component-actions {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.35rem;
+  margin-left: auto;
+}
+
+.tree-grid .structure-component-actions button {
+  font-size: 0.75rem;
+  padding: 0.18rem 0.45rem;
+}
+
+.tree-grid .structure-component-fixed {
+  color: #64748b;
+  font-size: 0.75rem;
+}
+
 .tree-grid .section-drop-cell {
  padding: 0.45rem 0.6rem;
 }
@@ -707,6 +1023,20 @@ body {
  cursor: text;
 }

+.tree-grid .cell-protection-trigger {
+  color: var(--color-primary);
+  cursor: pointer;
+  font-weight: 600;
+  transition:
+    background-color 0.12s ease,
+    box-shadow 0.12s ease;
+}
+
+.tree-grid .cell-protection-trigger:hover {
+  background: #eaf6f0;
+  box-shadow: inset 0 0 0 1px var(--color-signal);
+}
+
 .tree-grid .device-drag-handle {
  cursor: grab;
 }
@@ -1,6 +1,7 @@
 import type { Metadata } from "next";
 import "bootstrap/dist/css/bootstrap.min.css";
 import "./globals.css";
+import { AppShell } from "../frontend/components/AppShell";

 export const metadata: Metadata = {
  title: "Leistungsbilanz",
@@ -10,7 +11,9 @@ export const metadata: Metadata = {
 export default function RootLayout({ children }: Readonly<{ children: React.ReactNode }>) {
  return (
    <html lang="de">
-      <body>{children}</body>
+      <body>
+        <AppShell>{children}</AppShell>
+      </body>
    </html>
  );
 }
@@ -15,12 +15,6 @@ export default function CircuitTreeEditPage() {
          <p className="text-secondary mb-0">Stromkreise und zugeordnete Geräte bearbeiten.</p>
        </div>
        <div className="d-flex gap-2">
-          <Link
-            href={`/projects/${params.projectId}/circuit-lists/${params.circuitListId}/tree`}
-            className="btn btn-outline-secondary btn-sm"
-          >
-            Strukturvorschau
-          </Link>
          <Link href={`/projects/${params.projectId}`} className="btn btn-outline-secondary btn-sm">
            Zum Projekt
          </Link>
@@ -1,38 +0,0 @@
-"use client";
-
-import Link from "next/link";
-import { useParams } from "next/navigation";
-import { CircuitTreePreview } from "../../../../../../frontend/components/circuit-tree-preview";
-
-export default function CircuitTreePreviewPage() {
-  const params = useParams<{ projectId: string; circuitListId: string }>();
-  const projectId = params.projectId;
-  const circuitListId = params.circuitListId;
-
-  return (
-    <main className="container py-4">
-      <div className="d-flex justify-content-between align-items-center mb-3">
-        <div>
-          <h1 className="h4 mb-1">Vorschau der Stromkreisstruktur</h1>
-          <p className="text-secondary mb-0">
-            Schreibgeschützte Vorschau der Bereiche, Stromkreise und Gerätezeilen.
-          </p>
-        </div>
-        <Link
-          href={`/projects/${projectId}/circuit-lists/${circuitListId}/tree-edit`}
-          className="btn btn-outline-primary btn-sm"
-        >
-          Editor öffnen
-        </Link>
-        <Link
-          href={`/projects/${projectId}`}
-          className="btn btn-outline-secondary btn-sm"
-        >
-          Zum Projekt
-        </Link>
-      </div>
-
-      <CircuitTreePreview projectId={projectId} circuitListId={circuitListId} />
-    </main>
-  );
-}
@@ -5,12 +5,16 @@ import { useParams } from "next/navigation";
 import { FormEvent, useEffect, useMemo, useState } from "react";
 import {
  copyGlobalDeviceToProject,
+  copyDistributionBoard,
  copyProjectDeviceToGlobal,
  createDistributionBoard,
  createFloor,
  createProjectDevice,
  createRoom,
+  deleteFloor,
  deleteProjectDevice,
+  deleteRoom,
+  deleteDistributionBoard,
  disconnectProjectDeviceRows,
  exportProjectTransfer,
  getProjectDeviceSyncPreview,
@@ -24,8 +28,10 @@ import {
  importProjectTransfer,
  synchronizeProjectDeviceRows,
  updateDistributionBoard,
+  updateFloor,
  updateProjectDevice,
  updateProjectSettings,
+  updateRoom,
 } from "../../../frontend/utils/api";
 import type {
  CircuitListDto,
@@ -91,10 +97,13 @@ export default function ProjectDetailPage() {
    editingBoardSimultaneityFactor,
    setEditingBoardSimultaneityFactor,
  ] = useState("1");
+  const [editingBoardCopyName, setEditingBoardCopyName] = useState("");
  const [floorName, setFloorName] = useState("");
+  const [editingFloor, setEditingFloor] = useState<FloorDto | null>(null);
  const [roomNumber, setRoomNumber] = useState("");
  const [roomName, setRoomName] = useState("");
  const [roomFloorId, setRoomFloorId] = useState("");
+  const [editingRoom, setEditingRoom] = useState<RoomDto | null>(null);
  const [isProjectSettingsOpen, setIsProjectSettingsOpen] = useState(false);
  const [structureModal, setStructureModal] = useState<
    "board" | "floor" | "room" | null
@@ -236,7 +245,7 @@ export default function ProjectDetailPage() {
    }
  }

-  async function handleCreateFloor(event: FormEvent<HTMLFormElement>) {
+  async function handleSaveFloor(event: FormEvent<HTMLFormElement>) {
    event.preventDefault();
    if (!projectId || !project || !floorName.trim()) {
      return;
@@ -244,23 +253,37 @@ export default function ProjectDetailPage() {
    setIsSaving(true);
    setError(null);
    try {
-      const result = await createFloor(
-        projectId,
-        { name: floorName.trim() },
-        project.currentRevision
+      const result = editingFloor
+        ? await updateFloor(
+            projectId,
+            editingFloor.id,
+            { name: floorName.trim() },
+            project.currentRevision
+          )
+        : await createFloor(
+            projectId,
+            { name: floorName.trim() },
+            project.currentRevision
+          );
+      setFloors((current) =>
+        editingFloor
+          ? current.map((floor) =>
+              floor.id === result.floor.id ? result.floor : floor
+            )
+          : [...current, result.floor]
      );
-      setFloors((current) => [...current, result.floor]);
      applyProjectRevision(result.history.currentRevision);
      setFloorName("");
+      setEditingFloor(null);
      setStructureModal(null);
    } catch (err) {
-      setError(err instanceof Error ? err.message : "Etage konnte nicht erstellt werden.");
+      setError(err instanceof Error ? err.message : "Etage konnte nicht gespeichert werden.");
    } finally {
      setIsSaving(false);
    }
  }

-  async function handleCreateRoom(event: FormEvent<HTMLFormElement>) {
+  async function handleSaveRoom(event: FormEvent<HTMLFormElement>) {
    event.preventDefault();
    if (
      !projectId ||
@@ -273,23 +296,34 @@ export default function ProjectDetailPage() {
    setIsSaving(true);
    setError(null);
    try {
-      const result = await createRoom(
-        projectId,
-        {
-          floorId: roomFloorId || undefined,
-          roomNumber: roomNumber.trim(),
-          roomName: roomName.trim(),
-        },
-        project.currentRevision
+      const input = {
+        floorId: roomFloorId || undefined,
+        roomNumber: roomNumber.trim(),
+        roomName: roomName.trim(),
+      };
+      const result = editingRoom
+        ? await updateRoom(
+            projectId,
+            editingRoom.id,
+            input,
+            project.currentRevision
+          )
+        : await createRoom(projectId, input, project.currentRevision);
+      setRooms((current) =>
+        editingRoom
+          ? current.map((room) =>
+              room.id === result.room.id ? result.room : room
+            )
+          : [...current, result.room]
      );
-      setRooms((current) => [...current, result.room]);
      applyProjectRevision(result.history.currentRevision);
      setRoomNumber("");
      setRoomName("");
      setRoomFloorId("");
+      setEditingRoom(null);
      setStructureModal(null);
    } catch (err) {
-      setError(err instanceof Error ? err.message : "Raum konnte nicht erstellt werden.");
+      setError(err instanceof Error ? err.message : "Raum konnte nicht gespeichert werden.");
    } finally {
      setIsSaving(false);
    }
@@ -405,6 +439,7 @@ export default function ProjectDetailPage() {
    setEditingBoardSimultaneityFactor(
      String(board.simultaneityFactor)
    );
+    setEditingBoardCopyName(`${board.name} Kopie`);
  }

  function openBoardCreator() {
@@ -463,6 +498,156 @@ export default function ProjectDetailPage() {
    }
  }

+  function openCreateFloor() {
+    setEditingFloor(null);
+    setFloorName("");
+    setStructureModal("floor");
+  }
+
+  function openEditFloor(floor: FloorDto) {
+    setEditingFloor(floor);
+    setFloorName(floor.name);
+    setStructureModal("floor");
+  }
+
+  function openCreateRoom() {
+    setEditingRoom(null);
+    setRoomNumber("");
+    setRoomName("");
+    setRoomFloorId("");
+    setStructureModal("room");
+  }
+
+  function openEditRoom(room: RoomDto) {
+    setEditingRoom(room);
+    setRoomNumber(room.roomNumber);
+    setRoomName(room.roomName);
+    setRoomFloorId(room.floorId ?? "");
+    setStructureModal("room");
+  }
+
+  async function handleDeleteFloor() {
+    if (!projectId || !project || !editingFloor) return;
+    if (!window.confirm(`Etage „${editingFloor.name}“ wirklich löschen?`)) return;
+    setIsSaving(true);
+    setError(null);
+    try {
+      const result = await deleteFloor(projectId, editingFloor.id, project.currentRevision);
+      setFloors((current) => current.filter((floor) => floor.id !== editingFloor.id));
+      applyProjectRevision(result.history.currentRevision);
+      setEditingFloor(null);
+      setFloorName("");
+      setStructureModal(null);
+    } catch (err) {
+      setError(err instanceof Error ? err.message : "Etage konnte nicht gelöscht werden.");
+    } finally {
+      setIsSaving(false);
+    }
+  }
+
+  async function handleDeleteRoom() {
+    if (!projectId || !project || !editingRoom) return;
+    if (!window.confirm(`Raum „${editingRoom.roomNumber} ${editingRoom.roomName}“ wirklich löschen?`)) return;
+    setIsSaving(true);
+    setError(null);
+    try {
+      const result = await deleteRoom(projectId, editingRoom.id, project.currentRevision);
+      setRooms((current) => current.filter((room) => room.id !== editingRoom.id));
+      applyProjectRevision(result.history.currentRevision);
+      setEditingRoom(null);
+      setRoomNumber("");
+      setRoomName("");
+      setRoomFloorId("");
+      setStructureModal(null);
+    } catch (err) {
+      setError(err instanceof Error ? err.message : "Raum konnte nicht gelöscht werden.");
+    } finally {
+      setIsSaving(false);
+    }
+  }
+
+  async function handleCopyBoard() {
+    if (
+      !projectId ||
+      !project ||
+      !editingBoard ||
+      !editingBoardCopyName.trim()
+    ) {
+      return;
+    }
+    setIsSaving(true);
+    setError(null);
+    try {
+      const result = await copyDistributionBoard(
+        projectId,
+        editingBoard.id,
+        editingBoardCopyName.trim(),
+        project.currentRevision
+      );
+      setBoards((current) => [
+        ...current,
+        result.distributionBoard,
+      ]);
+      setCircuitLists((current) => [
+        ...current,
+        result.circuitList,
+      ]);
+      applyProjectRevision(result.history.currentRevision);
+      setEditingBoard(null);
+    } catch (err) {
+      setError(
+        err instanceof Error
+          ? err.message
+          : "Verteilung konnte nicht kopiert werden."
+      );
+    } finally {
+      setIsSaving(false);
+    }
+  }
+
+  async function handleDeleteBoard() {
+    if (!projectId || !project || !editingBoard) {
+      return;
+    }
+    const confirmed = window.confirm(
+      `Verteilung „${editingBoard.name}“ wirklich löschen?\n\n` +
+        "Dabei werden die Stromkreisliste, alle Gruppen, Stromkreise, Gerätezeilen, Schutzgeräte und weiteren Verteilergeräte entfernt. " +
+        "Der Vorgang kann anschließend über die projektweite Historie rückgängig gemacht werden."
+    );
+    if (!confirmed) {
+      return;
+    }
+    setIsSaving(true);
+    setError(null);
+    try {
+      const result = await deleteDistributionBoard(
+        projectId,
+        editingBoard.id,
+        project.currentRevision
+      );
+      setBoards((current) =>
+        current.filter((board) => board.id !== result.distributionBoardId)
+      );
+      setCircuitLists((current) =>
+        current.filter(
+          (circuitList) =>
+            circuitList.distributionBoardId !==
+            result.distributionBoardId
+        )
+      );
+      applyProjectRevision(result.history.currentRevision);
+      setEditingBoard(null);
+    } catch (err) {
+      setError(
+        err instanceof Error
+          ? err.message
+          : "Verteilung konnte nicht gelöscht werden."
+      );
+    } finally {
+      setIsSaving(false);
+    }
+  }
+
  async function handleExportProject() {
    if (!project) {
      return;
@@ -661,9 +846,10 @@ export default function ProjectDetailPage() {

  return (
    <main className="container py-4">
-      <div className="d-flex flex-wrap justify-content-between align-items-center gap-3 mb-3">
+      <div className="page-header">
        <div>
-          <h1 className="h3 mb-1">{project?.name ?? "Projekt"}</h1>
+          <div className="kicker">Projekt</div>
+          <h1>{project?.name ?? "Projekt"}</h1>
          <p className="text-secondary mb-0">
            {project?.internalProjectNumber
              ? `Projektnummer ${project.internalProjectNumber} · `
@@ -688,9 +874,28 @@ export default function ProjectDetailPage() {

      {error ? <div className="alert alert-warning">{error}</div> : null}

+      <div className="kpi-grid">
+        <a className="kpi" href="#verteilungen">
+          <div className="kpi-label">Verteilungen</div>
+          <div className="kpi-value">{boardCount}</div>
+        </a>
+        <a className="kpi" href="#etagen">
+          <div className="kpi-label">Etagen</div>
+          <div className="kpi-value">{floorCount}</div>
+        </a>
+        <a className="kpi" href="#raeume">
+          <div className="kpi-label">Räume</div>
+          <div className="kpi-value">{roomCount}</div>
+        </a>
+        <a className="kpi" href="#projektgeraete">
+          <div className="kpi-label">Projektgeräte</div>
+          <div className="kpi-value">{projectDeviceCount}</div>
+        </a>
+      </div>
+
      <div className="row g-4">
        {project ? (
-          <section className="col-12">
+          <section className="col-12" id="verlauf">
            <ProjectVersionHistory
              currentRevision={project.currentRevision}
              onProjectStateChange={() => window.location.reload()}
@@ -699,7 +904,7 @@ export default function ProjectDetailPage() {
          </section>
        ) : null}

-        <section className="col-12">
+        <section className="col-12" id="verteilungen">
          <div className="card shadow-sm">
            <div className="card-header d-flex justify-content-between align-items-center">
              <div>
@@ -792,7 +997,7 @@ export default function ProjectDetailPage() {
          </div>
        </section>

-        <section className="col-12 col-lg-5">
+        <section className="col-12 col-lg-5" id="etagen">
          <div className="card shadow-sm h-100">
            <div className="card-header d-flex justify-content-between align-items-center">
              <div>
@@ -801,7 +1006,7 @@ export default function ProjectDetailPage() {
              </div>
              <button
                className="btn btn-sm btn-outline-primary"
-                onClick={() => setStructureModal("floor")}
+                onClick={openCreateFloor}
                type="button"
              >
                Hinzufügen
@@ -809,8 +1014,11 @@ export default function ProjectDetailPage() {
            </div>
            <ul className="list-group list-group-flush">
              {floors.map((floor) => (
-                <li className="list-group-item" key={floor.id}>
-                  {floor.name}
+                <li className="list-group-item d-flex justify-content-between align-items-center gap-2" key={floor.id}>
+                  <span>{floor.name}</span>
+                  <button className="btn btn-sm btn-outline-secondary" onClick={() => openEditFloor(floor)} type="button">
+                    Bearbeiten
+                  </button>
                </li>
              ))}
              {!floors.length ? (
@@ -820,7 +1028,7 @@ export default function ProjectDetailPage() {
          </div>
        </section>

-        <section className="col-12 col-lg-7">
+        <section className="col-12 col-lg-7" id="raeume">
          <div className="card shadow-sm">
            <div className="card-header d-flex justify-content-between align-items-center">
              <div>
@@ -829,7 +1037,7 @@ export default function ProjectDetailPage() {
              </div>
              <button
                className="btn btn-sm btn-outline-primary"
-                onClick={() => setStructureModal("room")}
+                onClick={openCreateRoom}
                type="button"
              >
                Hinzufügen
@@ -842,6 +1050,7 @@ export default function ProjectDetailPage() {
                    <th>Raumnummer</th>
                    <th>Raumname</th>
                    <th>Etage</th>
+                    <th className="text-end">Aktionen</th>
                  </tr>
                </thead>
                <tbody>
@@ -850,11 +1059,16 @@ export default function ProjectDetailPage() {
                      <td>{room.roomNumber}</td>
                      <td>{room.roomName}</td>
                      <td>{room.floorId ? floorById.get(room.floorId)?.name ?? "-" : "-"}</td>
+                      <td className="text-end">
+                        <button className="btn btn-sm btn-outline-secondary" onClick={() => openEditRoom(room)} type="button">
+                          Bearbeiten
+                        </button>
+                      </td>
                    </tr>
                  ))}
                  {!rooms.length ? (
                    <tr>
-                      <td colSpan={3} className="text-center text-secondary py-4">
+                      <td colSpan={4} className="text-center text-secondary py-4">
                        Noch keine Räume vorhanden.
                      </td>
                    </tr>
@@ -866,7 +1080,7 @@ export default function ProjectDetailPage() {
        </section>
      </div>

-      <section className="card shadow-sm mt-4">
+      <section className="card shadow-sm mt-4" id="projektgeraete">
        <div className="card-header d-flex flex-wrap justify-content-between align-items-center gap-2">
          <div>
            <span>Projektgeräte</span>
@@ -1091,7 +1305,7 @@ export default function ProjectDetailPage() {

      {structureModal === "board" ? (
        <FormModal
-          description="Eine Stromkreisliste mit den vier Standardbereichen wird automatisch angelegt."
+          description="Eine Stromkreisliste mit den drei Standardgruppen wird automatisch angelegt."
          isSaving={isSaving}
          onClose={() => setStructureModal(null)}
          onSubmit={handleCreateBoard}
@@ -1251,17 +1465,89 @@ export default function ProjectDetailPage() {
              </div>
            </div>
          </div>
+          <hr className="my-4" />
+          <section aria-labelledby="copy-distribution-board-heading">
+            <h3
+              className="h6"
+              id="copy-distribution-board-heading"
+            >
+              Verteilung kopieren
+            </h3>
+            <p className="text-secondary small">
+              Erstellt eine vollständige Kopie des zuletzt gespeicherten
+              Stands einschließlich Gruppen, Stromkreisen, Gerätezeilen und
+              Schutzgeräten. Noch nicht gespeicherte Änderungen oben werden
+              nicht übernommen.
+            </p>
+            <div className="row g-2 align-items-end">
+              <div className="col-12 col-md">
+                <label
+                  className="form-label"
+                  htmlFor="copy-distribution-board-name"
+                >
+                  Bezeichnung der Kopie
+                </label>
+                <input
+                  className="form-control"
+                  id="copy-distribution-board-name"
+                  maxLength={200}
+                  onChange={(event) =>
+                    setEditingBoardCopyName(event.target.value)
+                  }
+                  value={editingBoardCopyName}
+                />
+              </div>
+              <div className="col-12 col-md-auto">
+                <button
+                  className="btn btn-outline-primary"
+                  disabled={isSaving || !editingBoardCopyName.trim()}
+                  onClick={() => void handleCopyBoard()}
+                  type="button"
+                >
+                  Verteilung kopieren
+                </button>
+              </div>
+            </div>
+          </section>
+          <hr className="my-4" />
+          <section
+            aria-labelledby="delete-distribution-board-heading"
+            className="border border-danger-subtle rounded p-3"
+          >
+            <h3
+              className="h6 text-danger"
+              id="delete-distribution-board-heading"
+            >
+              Gefahrenbereich
+            </h3>
+            <p className="text-secondary small mb-3">
+              Entfernt die vollständige Verteilung. Die Aktion wird erst
+              nach einer ausdrücklichen Warnung ausgeführt und kann über die
+              projektweite Historie rückgängig gemacht werden.
+            </p>
+            <button
+              className="btn btn-outline-danger"
+              disabled={isSaving}
+              onClick={() => void handleDeleteBoard()}
+              type="button"
+            >
+              Verteilung löschen
+            </button>
+          </section>
        </FormModal>
      ) : null}

      {structureModal === "floor" ? (
        <FormModal
          isSaving={isSaving}
-          onClose={() => setStructureModal(null)}
-          onSubmit={handleCreateFloor}
+          onClose={() => {
+            setStructureModal(null);
+            setEditingFloor(null);
+          }}
+          onSubmit={handleSaveFloor}
          submitDisabled={!floorName.trim()}
-          submitLabel="Etage hinzufügen"
-          title="Etage hinzufügen"
+          submitLabel={editingFloor ? "Änderungen speichern" : "Etage hinzufügen"}
+          title={editingFloor ? "Etage bearbeiten" : "Etage hinzufügen"}
        >
          <label className="form-label" htmlFor="floor-name">
            Bezeichnung
@@ -1275,17 +1561,30 @@ export default function ProjectDetailPage() {
            required
            value={floorName}
          />
+          {editingFloor ? (
+            <div className="border-top mt-4 pt-3">
+              <p className="text-secondary small mb-2">
+                Etagen mit zugeordneten Räumen oder Verteilungen können nicht gelöscht werden.
+              </p>
+              <button className="btn btn-outline-danger" disabled={isSaving} onClick={() => void handleDeleteFloor()} type="button">
+                Etage löschen
+              </button>
+            </div>
+          ) : null}
        </FormModal>
      ) : null}

      {structureModal === "room" ? (
        <FormModal
          isSaving={isSaving}
-          onClose={() => setStructureModal(null)}
-          onSubmit={handleCreateRoom}
+          onClose={() => {
+            setStructureModal(null);
+            setEditingRoom(null);
+          }}
+          onSubmit={handleSaveRoom}
          submitDisabled={!roomNumber.trim() || !roomName.trim()}
-          submitLabel="Raum anlegen"
-          title="Raum hinzufügen"
+          submitLabel={editingRoom ? "Änderungen speichern" : "Raum anlegen"}
+          title={editingRoom ? "Raum bearbeiten" : "Raum hinzufügen"}
        >
          <div className="row g-3">
            <div className="col-12 col-md-4">
@@ -1332,6 +1631,16 @@ export default function ProjectDetailPage() {
              </select>
            </div>
          </div>
+          {editingRoom ? (
+            <div className="border-top mt-4 pt-3">
+              <p className="text-secondary small mb-2">
+                In Stromkreisen verwendete Räume können nicht gelöscht werden.
+              </p>
+              <button className="btn btn-outline-danger" disabled={isSaving} onClick={() => void handleDeleteRoom()} type="button">
+                Raum löschen
+              </button>
+            </div>
+          ) : null}
        </FormModal>
      ) : null}

@@ -8,15 +8,15 @@ import {
  deleteGlobalDevice,
  importProjectTransferAsNew,
  listGlobalDevices,
-  listProjects,
  updateGlobalDevice,
 } from "../../frontend/utils/api";
 import type {
  CreateGlobalDeviceInput,
  GlobalDeviceDto,
-  ProjectDto,
 } from "../../frontend/types";

+const PROJECTS_CHANGED_EVENT = "leistungsbilanz:projects-changed";
+
 const emptyGlobalDevice: CreateGlobalDeviceInput = {
  name: "",
  displayName: "",
@@ -38,7 +38,6 @@ function toOptionalNumber(value: string) {
 }

 export default function ProjectsPage() {
-  const [projects, setProjects] = useState<ProjectDto[]>([]);
  const [globalDevices, setGlobalDevices] = useState<GlobalDeviceDto[]>([]);
  const [projectName, setProjectName] = useState("");
  const [globalDeviceForm, setGlobalDeviceForm] = useState<Record<string, string>>({
@@ -64,12 +63,14 @@ export default function ProjectsPage() {
    projectId: string;
    name: string;
  } | null>(null);
+  const [createdProject, setCreatedProject] = useState<{
+    id: string;
+    name: string;
+  } | null>(null);

  async function loadData() {
    setError(null);
-    const [loadedProjects, loadedGlobalDevices] = await Promise.all([listProjects(), listGlobalDevices()]);
-    setProjects(loadedProjects);
-    setGlobalDevices(loadedGlobalDevices);
+    setGlobalDevices(await listGlobalDevices());
  }

  useEffect(() => {
@@ -85,10 +86,12 @@ export default function ProjectsPage() {
    }
    setIsSaving(true);
    setError(null);
+    setCreatedProject(null);
    try {
      const created = await createProject(projectName.trim());
-      setProjects((current) => [...current, created]);
+      setCreatedProject({ id: created.id, name: created.name });
      setProjectName("");
+      window.dispatchEvent(new Event(PROJECTS_CHANGED_EVENT));
    } catch (err) {
      setError(err instanceof Error ? err.message : "Projekt konnte nicht erstellt werden.");
    } finally {
@@ -123,11 +126,11 @@ export default function ProjectsPage() {
    setImportedProject(null);
    try {
      const imported = await importProjectTransferAsNew(projectImport);
-      setProjects(await listProjects());
      setImportedProject(imported);
      setProjectImport(null);
      setProjectImportFilename("");
      setProjectImportInputKey((current) => current + 1);
+      window.dispatchEvent(new Event(PROJECTS_CHANGED_EVENT));
    } catch (err) {
      setError(
        err instanceof Error
@@ -222,130 +225,107 @@ export default function ProjectsPage() {

  return (
    <main className="container py-4">
-      <div className="d-flex justify-content-between align-items-center mb-4">
+      <div className="page-header">
        <div>
-          <h1 className="h3 mb-1">Projekte</h1>
+          <div className="kicker">Leistungsbilanz</div>
+          <h1>Projekte</h1>
          <p className="text-secondary mb-0">Projektübersicht und globale Geräteverwaltung</p>
        </div>
      </div>

      {error ? <div className="alert alert-warning">{error}</div> : null}

-      <div className="row g-4">
-        <section className="col-12 col-lg-4">
-          <div className="card shadow-sm mb-4">
-            <div className="card-header">Neues Projekt</div>
-            <div className="card-body">
-              <form className="vstack gap-3" onSubmit={handleCreateProject}>
-                <div>
-                  <label className="form-label">Projektname</label>
-                  <input
-                    className="form-control"
-                    value={projectName}
-                    onChange={(event) => setProjectName(event.target.value)}
-                    placeholder="z. B. Neubau Schule"
-                  />
-                </div>
-                <button className="btn btn-primary" type="submit" disabled={isSaving}>
-                  Projekt erstellen
-                </button>
-              </form>
-            </div>
-          </div>
-          <div className="card shadow-sm">
-            <div className="card-header">Projekt importieren</div>
-            <div className="card-body">
-              <p className="text-secondary small">
-                Eine exportierte JSON-Projektdatei wird als eigenständige Kopie
-                mit neuen internen IDs angelegt.
-              </p>
-              <label className="form-label" htmlFor="project-overview-import">
-                Projektdatei auswählen
-              </label>
-              <input
-                accept=".json,application/json"
-                className="form-control"
-                disabled={isSaving}
-                id="project-overview-import"
-                key={projectImportInputKey}
-                onChange={(event) =>
-                  void handleProjectImportFile(event.target.files?.[0])
-                }
-                type="file"
-              />
-              {projectImportFilename ? (
-                <div className="form-text">
-                  {projectImportFilename} ist bereit.
-                </div>
-              ) : null}
-              {projectImportFileError ? (
-                <div className="text-danger small mt-1">
-                  {projectImportFileError}
-                </div>
-              ) : null}
-              <button
-                className="btn btn-outline-primary mt-3 w-100"
-                disabled={isSaving || projectImport === null}
-                onClick={() => void handleImportProject()}
-                type="button"
-              >
-                Als neues Projekt importieren
+      <div className="d-flex flex-column gap-4">
+        <section className="card shadow-sm">
+          <div className="card-header">Neues Projekt</div>
+          <div className="card-body" style={{ maxWidth: 480 }}>
+            <form className="vstack gap-3" onSubmit={handleCreateProject}>
+              <div>
+                <label className="form-label">Projektname</label>
+                <input
+                  className="form-control"
+                  value={projectName}
+                  onChange={(event) => setProjectName(event.target.value)}
+                  placeholder="z. B. Neubau Schule"
+                />
+              </div>
+              <button className="btn btn-primary" type="submit" disabled={isSaving}>
+                Projekt erstellen
              </button>
-              {importedProject ? (
-                <div className="alert alert-success mt-3 mb-0">
-                  <div className="small mb-2">
-                    „{importedProject.name}“ wurde angelegt.
-                  </div>
-                  <Link
-                    className="btn btn-sm btn-success"
-                    href={`/projects/${importedProject.projectId}`}
-                  >
-                    Importiertes Projekt öffnen
-                  </Link>
+            </form>
+            {createdProject ? (
+              <div className="alert alert-success mt-3 mb-0">
+                <div className="small mb-2">
+                  „{createdProject.name}“ wurde angelegt.
                </div>
-              ) : null}
-            </div>
+                <Link
+                  className="btn btn-sm btn-success"
+                  href={`/projects/${createdProject.id}`}
+                >
+                  Projekt öffnen
+                </Link>
+              </div>
+            ) : null}
          </div>
        </section>

-        <section className="col-12 col-lg-8">
-          <div className="card shadow-sm">
-            <div className="card-header">Alle Projekte</div>
-            <div className="table-responsive">
-              <table className="table table-hover align-middle mb-0">
-                <thead>
-                  <tr>
-                    <th>Projekt</th>
-                    <th className="text-end">Aktionen</th>
-                  </tr>
-                </thead>
-                <tbody>
-                  {projects.map((project) => (
-                    <tr key={project.id}>
-                      <td>{project.name}</td>
-                      <td className="text-end">
-                        <Link className="btn btn-sm btn-outline-primary" href={`/projects/${project.id}`}>
-                          Projekt öffnen
-                        </Link>
-                      </td>
-                    </tr>
-                  ))}
-                  {!projects.length ? (
-                    <tr>
-                      <td colSpan={2} className="text-center text-secondary py-4">
-                        Noch keine Projekte vorhanden.
-                      </td>
-                    </tr>
-                  ) : null}
-                </tbody>
-              </table>
-            </div>
+        <section className="card shadow-sm">
+          <div className="card-header">Projekt importieren</div>
+          <div className="card-body" style={{ maxWidth: 480 }}>
+            <p className="text-secondary small">
+              Eine exportierte JSON-Projektdatei wird als eigenständige Kopie
+              mit neuen internen IDs angelegt.
+            </p>
+            <label className="form-label" htmlFor="project-overview-import">
+              Projektdatei auswählen
+            </label>
+            <input
+              accept=".json,application/json"
+              className="form-control"
+              disabled={isSaving}
+              id="project-overview-import"
+              key={projectImportInputKey}
+              onChange={(event) =>
+                void handleProjectImportFile(event.target.files?.[0])
+              }
+              type="file"
+            />
+            {projectImportFilename ? (
+              <div className="form-text">
+                {projectImportFilename} ist bereit.
+              </div>
+            ) : null}
+            {projectImportFileError ? (
+              <div className="text-danger small mt-1">
+                {projectImportFileError}
+              </div>
+            ) : null}
+            <button
+              className="btn btn-outline-primary mt-3 w-100"
+              disabled={isSaving || projectImport === null}
+              onClick={() => void handleImportProject()}
+              type="button"
+            >
+              Als neues Projekt importieren
+            </button>
+            {importedProject ? (
+              <div className="alert alert-success mt-3 mb-0">
+                <div className="small mb-2">
+                  „{importedProject.name}“ wurde angelegt.
+                </div>
+                <Link
+                  className="btn btn-sm btn-success"
+                  href={`/projects/${importedProject.projectId}`}
+                >
+                  Importiertes Projekt öffnen
+                </Link>
+              </div>
+            ) : null}
          </div>
        </section>
-      </div>

-      <section className="card shadow-sm mt-4">
-        <div className="card-header">Globale Geräte / Verbraucher</div>
+        <section className="card shadow-sm">
+          <div className="card-header">Globale Geräte / Verbraucher</div>
        <div className="card-body border-bottom">
          <form className="row g-2" onSubmit={handleCreateGlobalDevice}>
            <div className="col-12 col-md-3">
@@ -524,6 +504,7 @@ export default function ProjectsPage() {
          </table>
        </div>
      </section>
+      </div>
    </main>
  );
 }
@@ -1,28 +0,0 @@
-CREATE TABLE `consumers` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`distribution_board_id` text,
-	`name` text NOT NULL,
-	`category` text,
-	`quantity` integer NOT NULL,
-	`installed_power_per_unit_kw` real NOT NULL,
-	`demand_factor` real NOT NULL,
-	`voltage_v` real,
-	`phase_count` integer,
-	`power_factor` real,
-	`note` text,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`distribution_board_id`) REFERENCES `distribution_boards`(`id`) ON UPDATE no action ON DELETE set null
-);
--> statement-breakpoint
-CREATE TABLE `distribution_boards` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`name` text NOT NULL,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE TABLE `projects` (
-	`id` text PRIMARY KEY NOT NULL,
-	`name` text NOT NULL
-);
@@ -0,0 +1,300 @@
+CREATE TABLE `circuit_device_rows` (
+	`id` text PRIMARY KEY NOT NULL,
+	`circuit_id` text NOT NULL,
+	`linked_project_device_id` text,
+	`sort_order` integer DEFAULT 0 NOT NULL,
+	`name` text NOT NULL,
+	`display_name` text NOT NULL,
+	`phase_type` text,
+	`connection_kind` text,
+	`cost_group` text,
+	`category` text,
+	`level` text,
+	`room_id` text,
+	`room_number_snapshot` text,
+	`room_name_snapshot` text,
+	`quantity` integer NOT NULL,
+	`power_per_unit` real NOT NULL,
+	`simultaneity_factor` real NOT NULL,
+	`cos_phi` real,
+	`remark` text,
+	`overridden_fields` text,
+	FOREIGN KEY (`circuit_id`) REFERENCES `circuits`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`linked_project_device_id`) REFERENCES `project_devices`(`id`) ON UPDATE no action ON DELETE set null,
+	FOREIGN KEY (`room_id`) REFERENCES `rooms`(`id`) ON UPDATE no action ON DELETE set null
+);
+--> statement-breakpoint
+CREATE TABLE `circuit_list_equipment_identifiers` (
+	`owner_type` text NOT NULL,
+	`owner_id` text NOT NULL,
+	`circuit_list_id` text NOT NULL,
+	`equipment_identifier` text NOT NULL,
+	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_owner_unique` ON `circuit_list_equipment_identifiers` (`owner_type`,`owner_id`);--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_list_identifier_unique` ON `circuit_list_equipment_identifiers` (`circuit_list_id`,`equipment_identifier`);--> statement-breakpoint
+CREATE TABLE `circuit_lists` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`distribution_board_id` text NOT NULL,
+	`name` text NOT NULL,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`distribution_board_id`) REFERENCES `distribution_boards`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_lists_distribution_board_id_unique` ON `circuit_lists` (`distribution_board_id`);--> statement-breakpoint
+CREATE TABLE `circuit_protection_devices` (
+	`circuit_id` text PRIMARY KEY NOT NULL,
+	`type` text NOT NULL,
+	`rated_current_a` real NOT NULL,
+	`fuse_utilization_category` text,
+	`trip_characteristic` text,
+	`rcd_type` text,
+	`rated_residual_current_ma` real,
+	FOREIGN KEY (`circuit_id`) REFERENCES `circuits`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `circuit_sections` (
+	`id` text PRIMARY KEY NOT NULL,
+	`circuit_list_id` text NOT NULL,
+	`key` text NOT NULL,
+	`display_name` text NOT NULL,
+	`prefix` text NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL,
+	`category` text,
+	`group_number` integer,
+	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_sections_list_key_unique` ON `circuit_sections` (`circuit_list_id`,`key`);--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_sections_list_prefix_unique` ON `circuit_sections` (`circuit_list_id`,`prefix`);--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_sections_list_category_group_unique` ON `circuit_sections` (`circuit_list_id`,`category`,`group_number`);--> statement-breakpoint
+CREATE TABLE `circuits` (
+	`id` text PRIMARY KEY NOT NULL,
+	`circuit_list_id` text NOT NULL,
+	`section_id` text NOT NULL,
+	`equipment_identifier` text NOT NULL,
+	`display_name` text,
+	`sort_order` integer DEFAULT 0 NOT NULL,
+	`cable_type` text,
+	`cable_cross_section` text,
+	`cable_length` real,
+	`rcd_assignment` text,
+	`terminal_designation` text,
+	`voltage` real,
+	`control_requirement` text,
+	`status` text,
+	`is_reserve` integer DEFAULT 0 NOT NULL,
+	`remark` text,
+	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`section_id`) REFERENCES `circuit_sections`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `circuits_list_equipment_identifier_unique` ON `circuits` (`circuit_list_id`,`equipment_identifier`);--> statement-breakpoint
+CREATE TABLE `distribution_board_component_protection_devices` (
+	`component_id` text PRIMARY KEY NOT NULL,
+	`type` text NOT NULL,
+	`rated_current_a` real NOT NULL,
+	`fuse_utilization_category` text,
+	`trip_characteristic` text,
+	`rcd_type` text,
+	`rated_residual_current_ma` real,
+	FOREIGN KEY (`component_id`) REFERENCES `distribution_board_components`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `distribution_board_components` (
+	`id` text PRIMARY KEY NOT NULL,
+	`circuit_list_id` text NOT NULL,
+	`section_id` text,
+	`equipment_identifier` text NOT NULL,
+	`name` text NOT NULL,
+	`role` text NOT NULL,
+	`placement` text NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL,
+	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`section_id`) REFERENCES `circuit_sections`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `distribution_board_components_list_identifier_unique` ON `distribution_board_components` (`circuit_list_id`,`equipment_identifier`);--> statement-breakpoint
+CREATE UNIQUE INDEX `distribution_board_components_section_role_unique` ON `distribution_board_components` (`section_id`,`role`);--> statement-breakpoint
+CREATE TABLE `distribution_boards` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`name` text NOT NULL,
+	`floor_id` text,
+	`supply_type` text,
+	`simultaneity_factor` real DEFAULT 1 NOT NULL,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`floor_id`) REFERENCES `floors`(`id`) ON UPDATE no action ON DELETE set null
+);
+--> statement-breakpoint
+CREATE TABLE `floors` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`name` text NOT NULL,
+	`sort_order` integer DEFAULT 0 NOT NULL,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `global_devices` (
+	`id` text PRIMARY KEY NOT NULL,
+	`name` text NOT NULL,
+	`display_name` text NOT NULL,
+	`category` text,
+	`quantity` integer NOT NULL,
+	`installed_power_per_unit_kw` real NOT NULL,
+	`demand_factor` real NOT NULL,
+	`voltage_v` real,
+	`phase_count` integer,
+	`power_factor` real,
+	`note` text
+);
+--> statement-breakpoint
+CREATE TABLE `project_change_sets` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_revision_id` text NOT NULL,
+	`command_type` text NOT NULL,
+	`payload_schema_version` integer NOT NULL,
+	`forward_payload_json` text NOT NULL,
+	`inverse_payload_json` text NOT NULL,
+	FOREIGN KEY (`project_revision_id`) REFERENCES `project_revisions`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `project_change_sets_revision_unique` ON `project_change_sets` (`project_revision_id`);--> statement-breakpoint
+CREATE TABLE `project_devices` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`name` text NOT NULL,
+	`display_name` text NOT NULL,
+	`phase_type` text DEFAULT 'single_phase' NOT NULL,
+	`connection_kind` text,
+	`cost_group` text,
+	`category` text,
+	`quantity` integer NOT NULL,
+	`power_per_unit` real DEFAULT 0 NOT NULL,
+	`simultaneity_factor` real DEFAULT 1 NOT NULL,
+	`cos_phi` real,
+	`remark` text,
+	`voltage_v` real,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE TABLE `project_history_stack_entries` (
+	`change_set_id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`stack` text NOT NULL,
+	`position` integer NOT NULL,
+	FOREIGN KEY (`change_set_id`) REFERENCES `project_change_sets`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
+	CONSTRAINT "project_history_stack_entries_stack_check" CHECK("project_history_stack_entries"."stack" in ('undo', 'redo'))
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `project_history_stack_entries_position_unique` ON `project_history_stack_entries` (`project_id`,`stack`,`position`);--> statement-breakpoint
+CREATE TABLE `project_revisions` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`revision_number` integer NOT NULL,
+	`created_at_iso` text NOT NULL,
+	`actor_id` text,
+	`source` text NOT NULL,
+	`description` text,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `project_revisions_project_number_unique` ON `project_revisions` (`project_id`,`revision_number`);--> statement-breakpoint
+CREATE TABLE `project_snapshots` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`source_revision` integer NOT NULL,
+	`schema_version` integer NOT NULL,
+	`kind` text DEFAULT 'named' NOT NULL,
+	`name` text NOT NULL,
+	`description` text,
+	`payload_json` text NOT NULL,
+	`payload_sha256` text NOT NULL,
+	`created_at_iso` text NOT NULL,
+	`created_by_actor_id` text,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX `project_snapshots_project_created_idx` ON `project_snapshots` (`project_id`,`created_at_iso`);--> statement-breakpoint
+CREATE INDEX `project_snapshots_project_kind_revision_idx` ON `project_snapshots` (`project_id`,`kind`,`source_revision`);--> statement-breakpoint
+CREATE UNIQUE INDEX `project_snapshots_project_name_unique` ON `project_snapshots` (`project_id`,`name`);--> statement-breakpoint
+CREATE TABLE `projects` (
+	`id` text PRIMARY KEY NOT NULL,
+	`name` text NOT NULL,
+	`internal_project_number` text,
+	`external_project_number` text,
+	`building_owner` text,
+	`description` text,
+	`single_phase_voltage_v` integer DEFAULT 230 NOT NULL,
+	`three_phase_voltage_v` integer DEFAULT 400 NOT NULL,
+	`enabled_distribution_board_supply_types` text DEFAULT '["AV","SV","EV","USV","MSR","SiBe"]' NOT NULL,
+	`current_revision` integer DEFAULT 0 NOT NULL
+);
+--> statement-breakpoint
+CREATE TABLE `rooms` (
+	`id` text PRIMARY KEY NOT NULL,
+	`project_id` text NOT NULL,
+	`floor_id` text,
+	`room_number` text NOT NULL,
+	`room_name` text NOT NULL,
+	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
+	FOREIGN KEY (`floor_id`) REFERENCES `floors`(`id`) ON UPDATE no action ON DELETE set null
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_normalized_unique`
+ON `circuit_list_equipment_identifiers` (`circuit_list_id`, lower(trim(`equipment_identifier`)));
+--> statement-breakpoint
+CREATE UNIQUE INDEX `distribution_board_components_fixed_role_unique`
+ON `distribution_board_components` (`circuit_list_id`, `role`)
+WHERE `role` IN ('main_switch', 'surge_protective_device');
+--> statement-breakpoint
+CREATE TRIGGER `circuits_equipment_identifier_insert`
+AFTER INSERT ON `circuits`
+BEGIN
+	INSERT INTO `circuit_list_equipment_identifiers`
+		(`owner_type`, `owner_id`, `circuit_list_id`, `equipment_identifier`)
+	VALUES ('circuit', NEW.`id`, NEW.`circuit_list_id`, NEW.`equipment_identifier`);
+END;
+--> statement-breakpoint
+CREATE TRIGGER `circuits_equipment_identifier_update`
+AFTER UPDATE OF `circuit_list_id`, `equipment_identifier` ON `circuits`
+BEGIN
+	UPDATE `circuit_list_equipment_identifiers`
+	SET `circuit_list_id` = NEW.`circuit_list_id`,
+		`equipment_identifier` = NEW.`equipment_identifier`
+	WHERE `owner_type` = 'circuit' AND `owner_id` = OLD.`id`;
+END;
+--> statement-breakpoint
+CREATE TRIGGER `circuits_equipment_identifier_delete`
+AFTER DELETE ON `circuits`
+BEGIN
+	DELETE FROM `circuit_list_equipment_identifiers`
+	WHERE `owner_type` = 'circuit' AND `owner_id` = OLD.`id`;
+END;
+--> statement-breakpoint
+CREATE TRIGGER `distribution_board_components_equipment_identifier_insert`
+AFTER INSERT ON `distribution_board_components`
+BEGIN
+	INSERT INTO `circuit_list_equipment_identifiers`
+		(`owner_type`, `owner_id`, `circuit_list_id`, `equipment_identifier`)
+	VALUES ('distribution_board_component', NEW.`id`, NEW.`circuit_list_id`, NEW.`equipment_identifier`);
+END;
+--> statement-breakpoint
+CREATE TRIGGER `distribution_board_components_equipment_identifier_update`
+AFTER UPDATE OF `circuit_list_id`, `equipment_identifier` ON `distribution_board_components`
+BEGIN
+	UPDATE `circuit_list_equipment_identifiers`
+	SET `circuit_list_id` = NEW.`circuit_list_id`,
+		`equipment_identifier` = NEW.`equipment_identifier`
+	WHERE `owner_type` = 'distribution_board_component' AND `owner_id` = OLD.`id`;
+END;
+--> statement-breakpoint
+CREATE TRIGGER `distribution_board_components_equipment_identifier_delete`
+AFTER DELETE ON `distribution_board_components`
+BEGIN
+	DELETE FROM `circuit_list_equipment_identifiers`
+	WHERE `owner_type` = 'distribution_board_component' AND `owner_id` = OLD.`id`;
+END;
@@ -1,12 +0,0 @@
-CREATE TABLE `global_devices` (
-	`id` text PRIMARY KEY NOT NULL,
-	`name` text NOT NULL,
-	`category` text,
-	`quantity` integer NOT NULL,
-	`installed_power_per_unit_kw` real NOT NULL,
-	`demand_factor` real NOT NULL,
-	`voltage_v` real,
-	`phase_count` integer,
-	`power_factor` real,
-	`note` text
-);
@@ -1,3 +0,0 @@
-ALTER TABLE `projects` ADD COLUMN `single_phase_voltage_v` integer NOT NULL DEFAULT 230;
--> statement-breakpoint
-ALTER TABLE `projects` ADD COLUMN `three_phase_voltage_v` integer NOT NULL DEFAULT 400;
@@ -1,19 +0,0 @@
-CREATE TABLE `floors` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`name` text NOT NULL,
-	`sort_order` integer NOT NULL DEFAULT 0,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE TABLE `rooms` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`floor_id` text,
-	`room_number` text NOT NULL,
-	`room_name` text NOT NULL,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`floor_id`) REFERENCES `floors`(`id`) ON UPDATE no action ON DELETE set null
-);
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `room_id` text REFERENCES `rooms`(`id`) ON UPDATE no action ON DELETE set null;
@@ -1,44 +0,0 @@
-CREATE TABLE `circuit_lists` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`distribution_board_id` text NOT NULL,
-	`name` text NOT NULL,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`distribution_board_id`) REFERENCES `distribution_boards`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_lists_distribution_board_id_unique` ON `circuit_lists` (`distribution_board_id`);
--> statement-breakpoint
-INSERT INTO `circuit_lists` (`id`, `project_id`, `distribution_board_id`, `name`)
-SELECT `id`, `project_id`, `id`, `name` || ' Stromkreisliste'
-FROM `distribution_boards`;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `circuit_list_id` text REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE set null;
--> statement-breakpoint
-UPDATE `consumers` SET `circuit_list_id` = `distribution_board_id` WHERE `distribution_board_id` IS NOT NULL;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `circuit_number` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `description` text;
--> statement-breakpoint
-UPDATE `consumers` SET `description` = `name` WHERE `description` IS NULL;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `device_type` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `phase_type` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `trade_or_cost_group` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `group_name` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `protection_type` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `protection_rated_current` real;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `protection_characteristic` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `cable_type` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `cable_cross_section` text;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `comment` text;
@@ -1,14 +0,0 @@
-CREATE TABLE `project_devices` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`name` text NOT NULL,
-	`category` text,
-	`quantity` integer NOT NULL,
-	`installed_power_per_unit_kw` real NOT NULL,
-	`demand_factor` real NOT NULL,
-	`voltage_v` real,
-	`phase_count` integer,
-	`power_factor` real,
-	`note` text,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
-);
@@ -1,7 +0,0 @@
-ALTER TABLE `global_devices` ADD COLUMN `display_name` text;
--> statement-breakpoint
-UPDATE `global_devices` SET `display_name` = `name` WHERE `display_name` IS NULL;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `display_name` text;
--> statement-breakpoint
-UPDATE `project_devices` SET `display_name` = `name` WHERE `display_name` IS NULL;
@@ -1,3 +0,0 @@
-ALTER TABLE `consumers` ADD COLUMN `project_device_id` text REFERENCES `project_devices`(`id`) ON UPDATE no action ON DELETE set null;
--> statement-breakpoint
-ALTER TABLE `consumers` ADD COLUMN `is_linked_to_device` integer NOT NULL DEFAULT 0;
@@ -1,99 +0,0 @@
-CREATE TABLE `circuit_sections` (
-	`id` text PRIMARY KEY NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`key` text NOT NULL,
-	`display_name` text NOT NULL,
-	`prefix` text NOT NULL,
-	`sort_order` integer NOT NULL DEFAULT 0,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_sections_list_key_unique` ON `circuit_sections` (`circuit_list_id`,`key`);
--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_sections_list_prefix_unique` ON `circuit_sections` (`circuit_list_id`,`prefix`);
--> statement-breakpoint
-
-CREATE TABLE `circuits` (
-	`id` text PRIMARY KEY NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`section_id` text NOT NULL,
-	`equipment_identifier` text NOT NULL,
-	`display_name` text,
-	`sort_order` integer NOT NULL DEFAULT 0,
-	`protection_type` text,
-	`protection_rated_current` real,
-	`protection_characteristic` text,
-	`cable_type` text,
-	`cable_cross_section` text,
-	`cable_length` real,
-	`rcd_assignment` text,
-	`terminal_designation` text,
-	`voltage` real,
-	`status` text,
-	`is_reserve` integer NOT NULL DEFAULT 0,
-	`remark` text,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`section_id`) REFERENCES `circuit_sections`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `circuits_list_equipment_identifier_unique` ON `circuits` (`circuit_list_id`,`equipment_identifier`);
--> statement-breakpoint
-
-CREATE TABLE `circuit_device_rows` (
-	`id` text PRIMARY KEY NOT NULL,
-	`circuit_id` text NOT NULL,
-	`linked_project_device_id` text,
-	`legacy_consumer_id` text,
-	`sort_order` integer NOT NULL DEFAULT 0,
-	`name` text NOT NULL,
-	`display_name` text NOT NULL,
-	`phase_type` text,
-	`connection_kind` text,
-	`cost_group` text,
-	`category` text,
-	`level` text,
-	`room_id` text,
-	`room_number_snapshot` text,
-	`room_name_snapshot` text,
-	`quantity` integer NOT NULL,
-	`power_per_unit` real NOT NULL,
-	`simultaneity_factor` real NOT NULL,
-	`cos_phi` real,
-	`remark` text,
-	`overridden_fields` text,
-	FOREIGN KEY (`circuit_id`) REFERENCES `circuits`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`linked_project_device_id`) REFERENCES `project_devices`(`id`) ON UPDATE no action ON DELETE set null,
-	FOREIGN KEY (`room_id`) REFERENCES `rooms`(`id`) ON UPDATE no action ON DELETE set null
-);
--> statement-breakpoint
-
-CREATE TABLE `legacy_consumer_circuit_migrations` (
-	`consumer_id` text PRIMARY KEY NOT NULL,
-	`circuit_id` text NOT NULL,
-	`circuit_device_row_id` text NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`created_at_iso` text NOT NULL,
-	FOREIGN KEY (`circuit_id`) REFERENCES `circuits`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`circuit_device_row_id`) REFERENCES `circuit_device_rows`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-
-CREATE TABLE `legacy_consumer_migration_reports` (
-	`id` text PRIMARY KEY NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`legacy_consumer_count` integer NOT NULL,
-	`created_circuit_count` integer NOT NULL,
-	`created_device_row_count` integer NOT NULL,
-	`duplicate_grouped_count` integer NOT NULL,
-	`generated_identifier_count` integer NOT NULL,
-	`unassigned_row_count` integer NOT NULL,
-	`warnings_json` text NOT NULL,
-	`generated_identifiers_json` text NOT NULL,
-	`duplicate_groups_json` text NOT NULL,
-	`created_at_iso` text NOT NULL,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `legacy_consumer_migration_reports_list_unique` ON `legacy_consumer_migration_reports` (`circuit_list_id`);
-
@@ -1,24 +0,0 @@
-ALTER TABLE `project_devices` ADD COLUMN `phase_type` text NOT NULL DEFAULT 'single_phase';
--> statement-breakpoint
-UPDATE `project_devices`
-SET `phase_type` = CASE WHEN `phase_count` = 3 THEN 'three_phase' ELSE 'single_phase' END;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `connection_kind` text;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `cost_group` text;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `power_per_unit` real NOT NULL DEFAULT 0;
--> statement-breakpoint
-UPDATE `project_devices` SET `power_per_unit` = `installed_power_per_unit_kw`;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `simultaneity_factor` real NOT NULL DEFAULT 1;
--> statement-breakpoint
-UPDATE `project_devices` SET `simultaneity_factor` = `demand_factor`;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `cos_phi` real;
--> statement-breakpoint
-UPDATE `project_devices` SET `cos_phi` = `power_factor`;
--> statement-breakpoint
-ALTER TABLE `project_devices` ADD COLUMN `remark` text;
--> statement-breakpoint
-UPDATE `project_devices` SET `remark` = `note`;
@@ -1 +0,0 @@
-ALTER TABLE `circuits` ADD COLUMN `control_requirement` text;
@@ -1,9 +0,0 @@
-ALTER TABLE `project_devices` DROP COLUMN `installed_power_per_unit_kw`;
--> statement-breakpoint
-ALTER TABLE `project_devices` DROP COLUMN `demand_factor`;
--> statement-breakpoint
-ALTER TABLE `project_devices` DROP COLUMN `phase_count`;
--> statement-breakpoint
-ALTER TABLE `project_devices` DROP COLUMN `power_factor`;
--> statement-breakpoint
-ALTER TABLE `project_devices` DROP COLUMN `note`;
@@ -1,24 +0,0 @@
-CREATE TABLE `project_change_sets` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_revision_id` text NOT NULL,
-	`command_type` text NOT NULL,
-	`payload_schema_version` integer NOT NULL,
-	`forward_payload_json` text NOT NULL,
-	`inverse_payload_json` text NOT NULL,
-	FOREIGN KEY (`project_revision_id`) REFERENCES `project_revisions`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `project_change_sets_revision_unique` ON `project_change_sets` (`project_revision_id`);--> statement-breakpoint
-CREATE TABLE `project_revisions` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`revision_number` integer NOT NULL,
-	`created_at_iso` text NOT NULL,
-	`actor_id` text,
-	`source` text NOT NULL,
-	`description` text,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `project_revisions_project_number_unique` ON `project_revisions` (`project_id`,`revision_number`);--> statement-breakpoint
-ALTER TABLE `projects` ADD `current_revision` integer DEFAULT 0 NOT NULL;
@@ -1,11 +0,0 @@
-CREATE TABLE `project_history_stack_entries` (
-	`change_set_id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`stack` text NOT NULL,
-	`position` integer NOT NULL,
-	FOREIGN KEY (`change_set_id`) REFERENCES `project_change_sets`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade,
-	CONSTRAINT "project_history_stack_entries_stack_check" CHECK("project_history_stack_entries"."stack" in ('undo', 'redo'))
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `project_history_stack_entries_position_unique` ON `project_history_stack_entries` (`project_id`,`stack`,`position`);
@@ -1,16 +0,0 @@
-CREATE TABLE `project_snapshots` (
-	`id` text PRIMARY KEY NOT NULL,
-	`project_id` text NOT NULL,
-	`source_revision` integer NOT NULL,
-	`schema_version` integer NOT NULL,
-	`name` text NOT NULL,
-	`description` text,
-	`payload_json` text NOT NULL,
-	`payload_sha256` text NOT NULL,
-	`created_at_iso` text NOT NULL,
-	`created_by_actor_id` text,
-	FOREIGN KEY (`project_id`) REFERENCES `projects`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE INDEX `project_snapshots_project_created_idx` ON `project_snapshots` (`project_id`,`created_at_iso`);--> statement-breakpoint
-CREATE UNIQUE INDEX `project_snapshots_project_name_unique` ON `project_snapshots` (`project_id`,`name`);
@@ -1,2 +0,0 @@
-ALTER TABLE `project_snapshots` ADD `kind` text DEFAULT 'named' NOT NULL;--> statement-breakpoint
-CREATE INDEX `project_snapshots_project_kind_revision_idx` ON `project_snapshots` (`project_id`,`kind`,`source_revision`);
@@ -1,4 +0,0 @@
-ALTER TABLE `projects` ADD `internal_project_number` text;--> statement-breakpoint
-ALTER TABLE `projects` ADD `external_project_number` text;--> statement-breakpoint
-ALTER TABLE `projects` ADD `building_owner` text;--> statement-breakpoint
-ALTER TABLE `projects` ADD `description` text;
@@ -1,2 +0,0 @@
-ALTER TABLE `distribution_boards` ADD `floor_id` text REFERENCES floors(id);--> statement-breakpoint
-ALTER TABLE `distribution_boards` ADD `supply_type` text;
@@ -1 +0,0 @@
-ALTER TABLE `projects` ADD `enabled_distribution_board_supply_types` text DEFAULT '["AV","SV","EV","USV","MSR","SiBe"]' NOT NULL;
@@ -1,48 +0,0 @@
-UPDATE `global_devices`
-SET `voltage_v` = NULL;
--> statement-breakpoint
-UPDATE `project_devices` AS `pd`
-SET `voltage_v` = CASE
-  WHEN `pd`.`phase_type` = 'three_phase' THEN `p`.`three_phase_voltage_v`
-  ELSE `p`.`single_phase_voltage_v`
-END
-FROM `projects` AS `p`
-WHERE `p`.`id` = `pd`.`project_id`;
--> statement-breakpoint
-WITH `derived_circuit_voltages` AS (
-  SELECT
-    `c`.`id` AS `circuit_id`,
-    CASE
-      WHEN `cs`.`key` = 'three_phase' THEN `p`.`three_phase_voltage_v`
-      WHEN `cs`.`key` IN ('lighting', 'single_phase') THEN `p`.`single_phase_voltage_v`
-      WHEN EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `three_phase_row`
-        WHERE `three_phase_row`.`circuit_id` = `c`.`id`
-          AND `three_phase_row`.`phase_type` = 'three_phase'
-      ) AND NOT EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `other_row`
-        WHERE `other_row`.`circuit_id` = `c`.`id`
-          AND `other_row`.`phase_type` = 'single_phase'
-      ) THEN `p`.`three_phase_voltage_v`
-      ELSE `p`.`single_phase_voltage_v`
-    END AS `derived_voltage`
-  FROM `circuits` AS `c`
-  INNER JOIN `circuit_lists` AS `cl`
-    ON `cl`.`id` = `c`.`circuit_list_id`
-  INNER JOIN `projects` AS `p`
-    ON `p`.`id` = `cl`.`project_id`
-  INNER JOIN `circuit_sections` AS `cs`
-    ON `cs`.`id` = `c`.`section_id`
-)
-UPDATE `circuits`
-SET `voltage` = (
-  SELECT `derived_voltage`
-  FROM `derived_circuit_voltages`
-  WHERE `circuit_id` = `circuits`.`id`
-)
-WHERE `id` IN (
-  SELECT `circuit_id`
-  FROM `derived_circuit_voltages`
-);
@@ -1,85 +0,0 @@
-UPDATE `project_devices`
-SET `phase_type` = CASE
-  WHEN LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-    IN ('1ph', '1phase', '1phasig', 'einphasig', 'singlephase')
-    THEN 'single_phase'
-  WHEN LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-    IN ('3ph', '3phase', '3phasig', 'dreiphasig', 'threephase')
-    THEN 'three_phase'
-  ELSE `phase_type`
-END
-WHERE LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-  IN (
-    '1ph',
-    '1phase',
-    '1phasig',
-    'einphasig',
-    'singlephase',
-    '3ph',
-    '3phase',
-    '3phasig',
-    'dreiphasig',
-    'threephase'
-  );
--> statement-breakpoint
-UPDATE `circuit_device_rows`
-SET `phase_type` = CASE
-  WHEN LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-    IN ('1ph', '1phase', '1phasig', 'einphasig', 'singlephase')
-    THEN 'single_phase'
-  WHEN LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-    IN ('3ph', '3phase', '3phasig', 'dreiphasig', 'threephase')
-    THEN 'three_phase'
-  ELSE `phase_type`
-END
-WHERE LOWER(REPLACE(REPLACE(TRIM(`phase_type`), '-', ''), '_', ''))
-  IN (
-    '1ph',
-    '1phase',
-    '1phasig',
-    'einphasig',
-    'singlephase',
-    '3ph',
-    '3phase',
-    '3phasig',
-    'dreiphasig',
-    'threephase'
-  );
--> statement-breakpoint
-WITH `derived_circuit_voltages` AS (
-  SELECT
-    `c`.`id` AS `circuit_id`,
-    CASE
-      WHEN `cs`.`key` = 'three_phase' THEN `p`.`three_phase_voltage_v`
-      WHEN `cs`.`key` IN ('lighting', 'single_phase') THEN `p`.`single_phase_voltage_v`
-      WHEN EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `three_phase_row`
-        WHERE `three_phase_row`.`circuit_id` = `c`.`id`
-          AND `three_phase_row`.`phase_type` = 'three_phase'
-      ) AND NOT EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `single_phase_row`
-        WHERE `single_phase_row`.`circuit_id` = `c`.`id`
-          AND `single_phase_row`.`phase_type` = 'single_phase'
-      ) THEN `p`.`three_phase_voltage_v`
-      ELSE `p`.`single_phase_voltage_v`
-    END AS `derived_voltage`
-  FROM `circuits` AS `c`
-  INNER JOIN `circuit_lists` AS `cl`
-    ON `cl`.`id` = `c`.`circuit_list_id`
-  INNER JOIN `projects` AS `p`
-    ON `p`.`id` = `cl`.`project_id`
-  INNER JOIN `circuit_sections` AS `cs`
-    ON `cs`.`id` = `c`.`section_id`
-)
-UPDATE `circuits`
-SET `voltage` = (
-  SELECT `derived_voltage`
-  FROM `derived_circuit_voltages`
-  WHERE `circuit_id` = `circuits`.`id`
-)
-WHERE `id` IN (
-  SELECT `circuit_id`
-  FROM `derived_circuit_voltages`
-);
@@ -1,75 +0,0 @@
-UPDATE `circuit_device_rows`
-SET `phase_type` = COALESCE(
-  (
-    SELECT `pd`.`phase_type`
-    FROM `project_devices` AS `pd`
-    WHERE `pd`.`id` = `circuit_device_rows`.`linked_project_device_id`
-      AND `pd`.`phase_type` IN ('single_phase', 'three_phase')
-  ),
-  (
-    SELECT CASE
-      WHEN `cs`.`key` = 'three_phase' THEN 'three_phase'
-      WHEN `cs`.`key` IN ('lighting', 'single_phase') THEN 'single_phase'
-      ELSE NULL
-    END
-    FROM `circuits` AS `c`
-    INNER JOIN `circuit_sections` AS `cs`
-      ON `cs`.`id` = `c`.`section_id`
-    WHERE `c`.`id` = `circuit_device_rows`.`circuit_id`
-  )
-)
-WHERE `phase_type` IS NULL
-  AND (
-    EXISTS (
-      SELECT 1
-      FROM `project_devices` AS `pd`
-      WHERE `pd`.`id` = `circuit_device_rows`.`linked_project_device_id`
-        AND `pd`.`phase_type` IN ('single_phase', 'three_phase')
-    )
-    OR EXISTS (
-      SELECT 1
-      FROM `circuits` AS `c`
-      INNER JOIN `circuit_sections` AS `cs`
-        ON `cs`.`id` = `c`.`section_id`
-      WHERE `c`.`id` = `circuit_device_rows`.`circuit_id`
-        AND `cs`.`key` IN ('lighting', 'single_phase', 'three_phase')
-    )
-  );
--> statement-breakpoint
-WITH `derived_circuit_voltages` AS (
-  SELECT
-    `c`.`id` AS `circuit_id`,
-    CASE
-      WHEN `cs`.`key` = 'three_phase' THEN `p`.`three_phase_voltage_v`
-      WHEN `cs`.`key` IN ('lighting', 'single_phase') THEN `p`.`single_phase_voltage_v`
-      WHEN EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `three_phase_row`
-        WHERE `three_phase_row`.`circuit_id` = `c`.`id`
-          AND `three_phase_row`.`phase_type` = 'three_phase'
-      ) AND NOT EXISTS (
-        SELECT 1
-        FROM `circuit_device_rows` AS `single_phase_row`
-        WHERE `single_phase_row`.`circuit_id` = `c`.`id`
-          AND `single_phase_row`.`phase_type` = 'single_phase'
-      ) THEN `p`.`three_phase_voltage_v`
-      ELSE `p`.`single_phase_voltage_v`
-    END AS `derived_voltage`
-  FROM `circuits` AS `c`
-  INNER JOIN `circuit_lists` AS `cl`
-    ON `cl`.`id` = `c`.`circuit_list_id`
-  INNER JOIN `projects` AS `p`
-    ON `p`.`id` = `cl`.`project_id`
-  INNER JOIN `circuit_sections` AS `cs`
-    ON `cs`.`id` = `c`.`section_id`
-)
-UPDATE `circuits`
-SET `voltage` = (
-  SELECT `derived_voltage`
-  FROM `derived_circuit_voltages`
-  WHERE `circuit_id` = `circuits`.`id`
-)
-WHERE `id` IN (
-  SELECT `circuit_id`
-  FROM `derived_circuit_voltages`
-);
@@ -1,7 +0,0 @@
-UPDATE `circuit_device_rows`
-SET `phase_type` = 'single_phase'
-WHERE `phase_type` IS NULL;
--> statement-breakpoint
-UPDATE `global_devices`
-SET `phase_count` = 1
-WHERE `phase_count` IS NULL OR `phase_count` NOT IN (1, 3);
@@ -1 +0,0 @@
-ALTER TABLE `distribution_boards` ADD `simultaneity_factor` real DEFAULT 1 NOT NULL;
@@ -1,150 +0,0 @@
-CREATE TABLE `circuit_list_equipment_identifiers` (
-	`owner_type` text NOT NULL,
-	`owner_id` text NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`equipment_identifier` text NOT NULL,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_owner_unique` ON `circuit_list_equipment_identifiers` (`owner_type`,`owner_id`);--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_list_identifier_unique` ON `circuit_list_equipment_identifiers` (`circuit_list_id`,`equipment_identifier`);--> statement-breakpoint
-CREATE TABLE `circuit_protection_devices` (
-	`circuit_id` text PRIMARY KEY NOT NULL,
-	`type` text NOT NULL,
-	`rated_current_a` real NOT NULL,
-	`fuse_utilization_category` text,
-	`trip_characteristic` text,
-	`rcd_type` text,
-	`rated_residual_current_ma` real,
-	FOREIGN KEY (`circuit_id`) REFERENCES `circuits`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE TABLE `distribution_board_component_protection_devices` (
-	`component_id` text PRIMARY KEY NOT NULL,
-	`type` text NOT NULL,
-	`rated_current_a` real NOT NULL,
-	`fuse_utilization_category` text,
-	`trip_characteristic` text,
-	`rcd_type` text,
-	`rated_residual_current_ma` real,
-	FOREIGN KEY (`component_id`) REFERENCES `distribution_board_components`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE TABLE `distribution_board_components` (
-	`id` text PRIMARY KEY NOT NULL,
-	`circuit_list_id` text NOT NULL,
-	`section_id` text,
-	`equipment_identifier` text NOT NULL,
-	`name` text NOT NULL,
-	`role` text NOT NULL,
-	`placement` text NOT NULL,
-	`sort_order` integer DEFAULT 0 NOT NULL,
-	FOREIGN KEY (`circuit_list_id`) REFERENCES `circuit_lists`(`id`) ON UPDATE no action ON DELETE cascade,
-	FOREIGN KEY (`section_id`) REFERENCES `circuit_sections`(`id`) ON UPDATE no action ON DELETE cascade
-);
--> statement-breakpoint
-CREATE UNIQUE INDEX `distribution_board_components_list_identifier_unique` ON `distribution_board_components` (`circuit_list_id`,`equipment_identifier`);--> statement-breakpoint
-CREATE UNIQUE INDEX `distribution_board_components_section_role_unique` ON `distribution_board_components` (`section_id`,`role`);--> statement-breakpoint
-ALTER TABLE `circuit_sections` ADD `category` text;--> statement-breakpoint
-ALTER TABLE `circuit_sections` ADD `group_number` integer;--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_sections_list_category_group_unique` ON `circuit_sections` (`circuit_list_id`,`category`,`group_number`);--> statement-breakpoint
-UPDATE `circuit_sections`
-SET
-	`category` = CASE `key`
-		WHEN 'lighting' THEN 'lighting'
-		WHEN 'single_phase' THEN 'single_phase'
-		WHEN 'three_phase' THEN 'three_phase'
-	END,
-	`group_number` = 1
-WHERE `key` IN ('lighting', 'single_phase', 'three_phase');--> statement-breakpoint
-INSERT INTO `circuit_list_equipment_identifiers` (
-	`owner_type`,
-	`owner_id`,
-	`circuit_list_id`,
-	`equipment_identifier`
-)
-SELECT
-	'circuit',
-	`id`,
-	`circuit_list_id`,
-	`equipment_identifier`
-FROM `circuits`;--> statement-breakpoint
-CREATE UNIQUE INDEX `circuit_list_equipment_identifiers_normalized_unique`
-ON `circuit_list_equipment_identifiers` (
-	`circuit_list_id`,
-	lower(trim(`equipment_identifier`))
-);--> statement-breakpoint
-CREATE UNIQUE INDEX `distribution_board_components_fixed_role_unique`
-ON `distribution_board_components` (`circuit_list_id`, `role`)
-WHERE `role` IN ('main_switch', 'surge_protective_device');--> statement-breakpoint
-CREATE TRIGGER `circuits_equipment_identifier_insert`
-AFTER INSERT ON `circuits`
-BEGIN
-	INSERT INTO `circuit_list_equipment_identifiers` (
-		`owner_type`,
-		`owner_id`,
-		`circuit_list_id`,
-		`equipment_identifier`
-	)
-	VALUES (
-		'circuit',
-		NEW.`id`,
-		NEW.`circuit_list_id`,
-		NEW.`equipment_identifier`
-	);
-END;--> statement-breakpoint
-CREATE TRIGGER `circuits_equipment_identifier_update`
-AFTER UPDATE OF `circuit_list_id`, `equipment_identifier` ON `circuits`
-BEGIN
-	UPDATE `circuit_list_equipment_identifiers`
-	SET
-		`circuit_list_id` = NEW.`circuit_list_id`,
-		`equipment_identifier` = NEW.`equipment_identifier`
-	WHERE
-		`owner_type` = 'circuit'
-		AND `owner_id` = OLD.`id`;
-END;--> statement-breakpoint
-CREATE TRIGGER `circuits_equipment_identifier_delete`
-AFTER DELETE ON `circuits`
-BEGIN
-	DELETE FROM `circuit_list_equipment_identifiers`
-	WHERE
-		`owner_type` = 'circuit'
-		AND `owner_id` = OLD.`id`;
-END;--> statement-breakpoint
-CREATE TRIGGER `distribution_board_components_equipment_identifier_insert`
-AFTER INSERT ON `distribution_board_components`
-BEGIN
-	INSERT INTO `circuit_list_equipment_identifiers` (
-		`owner_type`,
-		`owner_id`,
-		`circuit_list_id`,
-		`equipment_identifier`
-	)
-	VALUES (
-		'distribution_board_component',
-		NEW.`id`,
-		NEW.`circuit_list_id`,
-		NEW.`equipment_identifier`
-	);
-END;--> statement-breakpoint
-CREATE TRIGGER `distribution_board_components_equipment_identifier_update`
-AFTER UPDATE OF `circuit_list_id`, `equipment_identifier`
-ON `distribution_board_components`
-BEGIN
-	UPDATE `circuit_list_equipment_identifiers`
-	SET
-		`circuit_list_id` = NEW.`circuit_list_id`,
-		`equipment_identifier` = NEW.`equipment_identifier`
-	WHERE
-		`owner_type` = 'distribution_board_component'
-		AND `owner_id` = OLD.`id`;
-END;--> statement-breakpoint
-CREATE TRIGGER `distribution_board_components_equipment_identifier_delete`
-AFTER DELETE ON `distribution_board_components`
-BEGIN
-	DELETE FROM `circuit_list_equipment_identifiers`
-	WHERE
-		`owner_type` = 'distribution_board_component'
-		AND `owner_id` = OLD.`id`;
-END;
@@ -5,176 +5,8 @@
    {
      "idx": 0,
      "version": "6",
-      "when": 1777565414148,
-      "tag": "0000_bizarre_colossus",
-      "breakpoints": true
-    },
-    {
-      "idx": 1,
-      "version": "6",
-      "when": 1777577000000,
-      "tag": "0001_global_devices",
-      "breakpoints": true
-    },
-    {
-      "idx": 2,
-      "version": "6",
-      "when": 1777580000000,
-      "tag": "0002_project_voltage_defaults",
-      "breakpoints": true
-    },
-    {
-      "idx": 3,
-      "version": "6",
-      "when": 1777589000000,
-      "tag": "0003_project_floors_rooms",
-      "breakpoints": true
-    },
-    {
-      "idx": 4,
-      "version": "6",
-      "when": 1777594000000,
-      "tag": "0004_circuit_lists_and_entry_fields",
-      "breakpoints": true
-    },
-    {
-      "idx": 5,
-      "version": "6",
-      "when": 1777597000000,
-      "tag": "0005_project_devices",
-      "breakpoints": true
-    },
-    {
-      "idx": 6,
-      "version": "6",
-      "when": 1777652000000,
-      "tag": "0006_device_display_name",
-      "breakpoints": true
-    },
-    {
-      "idx": 7,
-      "version": "6",
-      "when": 1777680000000,
-      "tag": "0007_consumer_device_link",
-      "breakpoints": true
-    },
-    {
-      "idx": 8,
-      "version": "6",
-      "when": 1777800000000,
-      "tag": "0008_circuit_first_model",
-      "breakpoints": true
-    },
-    {
-      "idx": 9,
-      "version": "6",
-      "when": 1784743200000,
-      "tag": "0009_project_device_circuit_fields",
-      "breakpoints": true
-    },
-    {
-      "idx": 10,
-      "version": "6",
-      "when": 1784746800000,
-      "tag": "0010_circuit_control_requirement",
-      "breakpoints": true
-    },
-    {
-      "idx": 11,
-      "version": "6",
-      "when": 1784832541202,
-      "tag": "0011_project_device_canonical_fields",
-      "breakpoints": true
-    },
-    {
-      "idx": 12,
-      "version": "6",
-      "when": 1784833957929,
-      "tag": "0012_project_revision_foundation",
-      "breakpoints": true
-    },
-    {
-      "idx": 13,
-      "version": "6",
-      "when": 1784835703230,
-      "tag": "0013_project_history_stacks",
-      "breakpoints": true
-    },
-    {
-      "idx": 14,
-      "version": "6",
-      "when": 1785009799979,
-      "tag": "0014_project_snapshots",
-      "breakpoints": true
-    },
-    {
-      "idx": 15,
-      "version": "6",
-      "when": 1785014383032,
-      "tag": "0015_modern_madame_masque",
-      "breakpoints": true
-    },
-    {
-      "idx": 16,
-      "version": "6",
-      "when": 1785254079435,
-      "tag": "0016_dashing_darkstar",
-      "breakpoints": true
-    },
-    {
-      "idx": 17,
-      "version": "6",
-      "when": 1785307189539,
-      "tag": "0017_vengeful_romulus",
-      "breakpoints": true
-    },
-    {
-      "idx": 18,
-      "version": "6",
-      "when": 1785308458789,
-      "tag": "0018_fancy_argent",
-      "breakpoints": true
-    },
-    {
-      "idx": 19,
-      "version": "6",
-      "when": 1785310907349,
-      "tag": "0019_normalize_project_voltages",
-      "breakpoints": true
-    },
-    {
-      "idx": 20,
-      "version": "6",
-      "when": 1785314248007,
-      "tag": "0020_normalize_phase_types",
-      "breakpoints": true
-    },
-    {
-      "idx": 21,
-      "version": "6",
-      "when": 1785314558555,
-      "tag": "0021_fill_missing_phase_types",
-      "breakpoints": true
-    },
-    {
-      "idx": 22,
-      "version": "6",
-      "when": 1785314626476,
-      "tag": "0022_default_remaining_phase_types",
-      "breakpoints": true
-    },
-    {
-      "idx": 23,
-      "version": "6",
-      "when": 1785343645615,
-      "tag": "0023_cheerful_night_thrasher",
-      "breakpoints": true
-    },
-    {
-      "idx": 24,
-      "version": "6",
-      "when": 1785431250141,
-      "tag": "0024_damp_mister_sinister",
+      "when": 1785499119431,
+      "tag": "0000_whole_surge",
      "breakpoints": true
    }
  ]
@@ -17,6 +17,7 @@ import type {
 import type { AppDatabase } from "../database-context.js";
 import { circuitDeviceRows } from "../schema/circuit-device-rows.js";
 import { circuitLists } from "../schema/circuit-lists.js";
+import { circuitProtectionDevices } from "../schema/circuit-protection-devices.js";
 import { circuitSections } from "../schema/circuit-sections.js";
 import { circuits } from "../schema/circuits.js";
 import { executeProjectCommandTransaction } from "./project-command-transaction.persistence.js";
@@ -381,9 +382,6 @@ export class CircuitDeviceRowMoveProjectCommandRepository
        equipmentIdentifier: snapshot.equipmentIdentifier,
        displayName: snapshot.displayName,
        sortOrder: snapshot.sortOrder,
-        protectionType: snapshot.protectionType,
-        protectionRatedCurrent: snapshot.protectionRatedCurrent,
-        protectionCharacteristic: snapshot.protectionCharacteristic,
        cableType: snapshot.cableType,
        cableCrossSection: snapshot.cableCrossSection,
        cableLength: snapshot.cableLength,
@@ -396,6 +394,12 @@ export class CircuitDeviceRowMoveProjectCommandRepository
        remark: snapshot.remark,
      })
      .run();
+    if (snapshot.protectionDevice) {
+      database
+        .insert(circuitProtectionDevices)
+        .values(snapshot.protectionDevice)
+        .run();
+    }
  }

  private assertTargetCircuitUnchanged(
@@ -416,11 +420,6 @@ export class CircuitDeviceRowMoveProjectCommandRepository
        snapshot.equipmentIdentifier ||
      current.displayName !== snapshot.displayName ||
      current.sortOrder !== snapshot.sortOrder ||
-      current.protectionType !== snapshot.protectionType ||
-      current.protectionRatedCurrent !==
-        snapshot.protectionRatedCurrent ||
-      current.protectionCharacteristic !==
-        snapshot.protectionCharacteristic ||
      current.cableType !== snapshot.cableType ||
      current.cableCrossSection !== snapshot.cableCrossSection ||
      current.cableLength !== snapshot.cableLength ||
@@ -438,6 +437,27 @@ export class CircuitDeviceRowMoveProjectCommandRepository
        "Created target circuit changed before command execution."
      );
    }
+    const protectionDevice = database
+      .select()
+      .from(circuitProtectionDevices)
+      .where(eq(circuitProtectionDevices.circuitId, snapshot.id))
+      .get();
+    if (
+      snapshot.protectionDevice === undefined
+        ? protectionDevice !== undefined
+        : snapshot.protectionDevice === null
+          ? protectionDevice !== undefined
+          : !protectionDevice ||
+            Object.entries(snapshot.protectionDevice).some(
+              ([key, value]) =>
+                (protectionDevice as Record<string, unknown>)[key] !==
+                value
+            )
+    ) {
+      throw new Error(
+        "Created target circuit protection changed before command execution."
+      );
+    }

    const currentRowIds = database
      .select({ id: circuitDeviceRows.id })
@@ -77,11 +77,6 @@ export class CircuitDeviceRowStructureProjectCommandRepository
    source: ExecuteCircuitDeviceRowStructureCommandInput["source"],
    row: CircuitDeviceRowSnapshot
  ) {
-    if (source === "user" && row.legacyConsumerId !== null) {
-      throw new Error(
-        "User commands cannot assign legacy consumer ids."
-      );
-    }
    if (source === "user" && !isElectricalPhaseType(row.phaseType)) {
      throw new Error("Device-row phase type is invalid.");
    }
@@ -49,7 +49,6 @@ export function toCircuitDeviceRowSnapshot(
    id: row.id,
    circuitId: row.circuitId,
    linkedProjectDeviceId: row.linkedProjectDeviceId,
-    legacyConsumerId: row.legacyConsumerId,
    sortOrder: row.sortOrder,
    name: row.name,
    displayName: row.displayName,
@@ -44,7 +44,6 @@ export interface CircuitDeviceRowPatchInput {
 export interface CircuitDeviceRowCreateInput extends CircuitDeviceRowUpdateInput {
  circuitId: string;
  linkedProjectDeviceId?: string;
-  legacyConsumerId?: string;
  sortOrder: number;
 }

@@ -110,7 +109,6 @@ export function toCircuitDeviceRowCreateValues(
  return {
    id,
    circuitId: input.circuitId,
-    legacyConsumerId: input.legacyConsumerId ?? null,
    sortOrder: input.sortOrder,
    ...toCircuitDeviceRowUpdateValues(input),
  };
@@ -25,7 +25,6 @@ export class CircuitDeviceRowRepository {
        id: circuitDeviceRows.id,
        circuitId: circuitDeviceRows.circuitId,
        linkedProjectDeviceId: circuitDeviceRows.linkedProjectDeviceId,
-        legacyConsumerId: circuitDeviceRows.legacyConsumerId,
        sortOrder: circuitDeviceRows.sortOrder,
        name: circuitDeviceRows.name,
        displayName: circuitDeviceRows.displayName,
@@ -0,0 +1,97 @@
+import { and, eq } from "drizzle-orm";
+import {
+  assertCircuitProtectionUpdateProjectCommand,
+  createCircuitProtectionUpdateProjectCommand,
+  type CircuitProtectionSnapshot,
+} from "../../domain/models/circuit-protection-project-command.model.js";
+import type {
+  CircuitProtectionProjectCommandStore,
+  ExecuteCircuitProtectionCommandInput,
+} from "../../domain/ports/circuit-protection-project-command.store.js";
+import type { AppDatabase } from "../database-context.js";
+import { circuitLists } from "../schema/circuit-lists.js";
+import { circuitProtectionDevices } from "../schema/circuit-protection-devices.js";
+import { circuits } from "../schema/circuits.js";
+import { executeProjectCommandTransaction } from "./project-command-transaction.persistence.js";
+
+export class CircuitProtectionProjectCommandRepository
+  implements CircuitProtectionProjectCommandStore
+{
+  constructor(private readonly database: AppDatabase) {}
+
+  execute(input: ExecuteCircuitProtectionCommandInput) {
+    return executeProjectCommandTransaction(this.database, input, (tx) => {
+      assertCircuitProtectionUpdateProjectCommand(input.command);
+      const { circuitId, expected, target } = input.command.payload;
+      if (input.source === "user" && target === null) {
+        throw new Error("User commands cannot remove circuit protection.");
+      }
+      this.assertOwnership(tx, input.projectId, circuitId);
+      const actual = tx
+        .select()
+        .from(circuitProtectionDevices)
+        .where(eq(circuitProtectionDevices.circuitId, circuitId))
+        .get();
+      if (!sameNullableSnapshot(expected, actual)) {
+        throw new Error("Circuit protection changed before update.");
+      }
+      if (target === null) {
+        tx.delete(circuitProtectionDevices)
+          .where(eq(circuitProtectionDevices.circuitId, circuitId))
+          .run();
+      } else if (actual) {
+        tx.update(circuitProtectionDevices)
+          .set(target)
+          .where(eq(circuitProtectionDevices.circuitId, circuitId))
+          .run();
+      } else {
+        tx.insert(circuitProtectionDevices).values(target).run();
+      }
+      return createCircuitProtectionUpdateProjectCommand(
+        circuitId,
+        target,
+        expected
+      );
+    });
+  }
+
+  private assertOwnership(
+    database: AppDatabase,
+    projectId: string,
+    circuitId: string
+  ) {
+    const circuit = database
+      .select({ projectId: circuitLists.projectId })
+      .from(circuits)
+      .innerJoin(
+        circuitLists,
+        eq(circuitLists.id, circuits.circuitListId)
+      )
+      .where(
+        and(
+          eq(circuits.id, circuitId),
+          eq(circuitLists.projectId, projectId)
+        )
+      )
+      .get();
+    if (!circuit) {
+      throw new Error("Circuit protection does not belong to project.");
+    }
+  }
+}
+
+function sameNullableSnapshot(
+  expected: CircuitProtectionSnapshot | null,
+  actual: typeof circuitProtectionDevices.$inferSelect | undefined
+) {
+  if (expected === null) {
+    return actual === undefined;
+  }
+  if (!actual) {
+    return false;
+  }
+  return Object.entries(expected).every(
+    ([key, value]) =>
+      (actual as Record<string, unknown>)[key] === value
+  );
+}
@@ -17,6 +17,7 @@ import { isElectricalPhaseType } from "../../domain/services/project-voltage.ser
 import type { AppDatabase } from "../database-context.js";
 import { circuitDeviceRows } from "../schema/circuit-device-rows.js";
 import { circuitLists } from "../schema/circuit-lists.js";
+import { circuitProtectionDevices } from "../schema/circuit-protection-devices.js";
 import { circuitSections } from "../schema/circuit-sections.js";
 import { circuits } from "../schema/circuits.js";
 import {
@@ -132,11 +133,6 @@ export class CircuitStructureProjectCommandRepository
        throw new Error("Circuit device-row id already exists.");
      }
      for (const row of snapshot.deviceRows) {
-        if (source === "user" && row.legacyConsumerId !== null) {
-          throw new Error(
-            "User commands cannot assign legacy consumer ids."
-          );
-        }
        if (source === "user" && !isElectricalPhaseType(row.phaseType)) {
          throw new Error("Device-row phase type is invalid.");
        }
@@ -157,9 +153,6 @@ export class CircuitStructureProjectCommandRepository
        equipmentIdentifier: snapshot.equipmentIdentifier,
        displayName: snapshot.displayName,
        sortOrder: snapshot.sortOrder,
-        protectionType: snapshot.protectionType,
-        protectionRatedCurrent: snapshot.protectionRatedCurrent,
-        protectionCharacteristic: snapshot.protectionCharacteristic,
        cableType: snapshot.cableType,
        cableCrossSection: snapshot.cableCrossSection,
        cableLength: snapshot.cableLength,
@@ -175,6 +168,12 @@ export class CircuitStructureProjectCommandRepository
    if (snapshot.deviceRows.length > 0) {
      database.insert(circuitDeviceRows).values(snapshot.deviceRows).run();
    }
+    if (snapshot.protectionDevice) {
+      database
+        .insert(circuitProtectionDevices)
+        .values(snapshot.protectionDevice)
+        .run();
+    }

    return createCircuitDeleteProjectCommand(
      snapshot.id,
@@ -219,6 +218,11 @@ export class CircuitStructureProjectCommandRepository
        asc(circuitDeviceRows.id)
      )
      .all();
+    const protectionDevice = database
+      .select()
+      .from(circuitProtectionDevices)
+      .where(eq(circuitProtectionDevices.circuitId, circuit.id))
+      .get();
    const inverse = createCircuitInsertProjectCommand({
      id: circuit.id,
      circuitListId: circuit.circuitListId,
@@ -226,9 +230,6 @@ export class CircuitStructureProjectCommandRepository
      equipmentIdentifier: circuit.equipmentIdentifier,
      displayName: circuit.displayName,
      sortOrder: circuit.sortOrder,
-      protectionType: circuit.protectionType,
-      protectionRatedCurrent: circuit.protectionRatedCurrent,
-      protectionCharacteristic: circuit.protectionCharacteristic,
      cableType: circuit.cableType,
      cableCrossSection: circuit.cableCrossSection,
      cableLength: circuit.cableLength,
@@ -240,6 +241,7 @@ export class CircuitStructureProjectCommandRepository
      isReserve: Boolean(circuit.isReserve),
      remark: circuit.remark,
      deviceRows: rows.map(toCircuitDeviceRowSnapshot),
+      protectionDevice: protectionDevice ?? null,
    });

    const result = database
@@ -4,9 +4,6 @@ export interface CircuitCreatePersistenceInput {
  equipmentIdentifier: string;
  displayName?: string;
  sortOrder: number;
-  protectionType?: string;
-  protectionRatedCurrent?: number;
-  protectionCharacteristic?: string;
  cableType?: string;
  cableCrossSection?: string;
  cableLength?: number;
@@ -24,9 +21,6 @@ export interface CircuitPatchPersistenceInput {
  equipmentIdentifier?: string;
  displayName?: string | null;
  sortOrder?: number;
-  protectionType?: string | null;
-  protectionRatedCurrent?: number | null;
-  protectionCharacteristic?: string | null;
  cableType?: string | null;
  cableCrossSection?: string | null;
  cableLength?: number | null;
@@ -47,9 +41,6 @@ export function toCircuitCreateValues(id: string, input: CircuitCreatePersistenc
    equipmentIdentifier: input.equipmentIdentifier,
    displayName: input.displayName ?? null,
    sortOrder: input.sortOrder,
-    protectionType: input.protectionType ?? null,
-    protectionRatedCurrent: input.protectionRatedCurrent ?? null,
-    protectionCharacteristic: input.protectionCharacteristic ?? null,
    cableType: input.cableType ?? null,
    cableCrossSection: input.cableCrossSection ?? null,
    cableLength: input.cableLength ?? null,
@@ -74,13 +65,6 @@ export function toCircuitPatchValues(input: CircuitPatchPersistenceInput) {
  }
  if (has("displayName")) values.displayName = input.displayName ?? null;
  if (input.sortOrder !== undefined) values.sortOrder = input.sortOrder;
-  if (has("protectionType")) values.protectionType = input.protectionType ?? null;
-  if (has("protectionRatedCurrent")) {
-    values.protectionRatedCurrent = input.protectionRatedCurrent ?? null;
-  }
-  if (has("protectionCharacteristic")) {
-    values.protectionCharacteristic = input.protectionCharacteristic ?? null;
-  }
  if (has("cableType")) values.cableType = input.cableType ?? null;
  if (has("cableCrossSection")) {
    values.cableCrossSection = input.cableCrossSection ?? null;
@@ -12,7 +12,6 @@ import {
 import {
  assertDistributionBoardUpdateProjectCommand,
  createDistributionBoardUpdateProjectCommand,
-  legacyDistributionBoardUpdateCommandSchemaVersion,
  type DistributionBoardUpdateField,
  type DistributionBoardUpdatePatch,
  type DistributionBoardUpdateProjectCommand,
@@ -332,19 +331,10 @@ export class DistributionBoardStructureProjectCommandRepository
        getDistributionBoardFieldValue(current, change.field),
      ])
    ) as DistributionBoardUpdatePatch;
-    const currentInverse = createDistributionBoardUpdateProjectCommand(
+    const inverse = createDistributionBoardUpdateProjectCommand(
      current.id,
      inversePatch
    );
-    const inverse =
-      input.command.schemaVersion ===
-      legacyDistributionBoardUpdateCommandSchemaVersion
-        ? ({
-            ...currentInverse,
-            schemaVersion:
-              legacyDistributionBoardUpdateCommandSchemaVersion,
-          } as DistributionBoardUpdateProjectCommand)
-        : currentInverse;
    const updated = database
      .update(distributionBoards)
      .set(patch)
@@ -0,0 +1,432 @@
+import { and, asc, eq, inArray } from "drizzle-orm";
+import {
+  assertDistributionBoardDeleteSubtreeProjectCommand,
+  assertDistributionBoardInsertSubtreeProjectCommand,
+  createDistributionBoardDeleteSubtreeProjectCommand,
+  createDistributionBoardInsertSubtreeProjectCommand,
+  distributionBoardDeleteSubtreeCommandType,
+  distributionBoardInsertSubtreeCommandType,
+  type DistributionBoardSubtreeProjectCommand,
+} from "../../domain/models/distribution-board-subtree-project-command.model.js";
+import {
+  assertDistributionBoardSubtreeSnapshot,
+  type DistributionBoardSubtreeSnapshot,
+} from "../../domain/models/distribution-board-subtree-snapshot.model.js";
+import type {
+  DistributionBoardSubtreeProjectCommandStore,
+  ExecuteDistributionBoardSubtreeCommandInput,
+} from "../../domain/ports/distribution-board-subtree-project-command.store.js";
+import type { AppDatabase } from "../database-context.js";
+import { circuitDeviceRows } from "../schema/circuit-device-rows.js";
+import { circuitLists } from "../schema/circuit-lists.js";
+import { circuitProtectionDevices } from "../schema/circuit-protection-devices.js";
+import { circuitSections } from "../schema/circuit-sections.js";
+import { circuits } from "../schema/circuits.js";
+import { distributionBoardComponentProtectionDevices } from "../schema/distribution-board-component-protection-devices.js";
+import { distributionBoardComponents } from "../schema/distribution-board-components.js";
+import { distributionBoards } from "../schema/distribution-boards.js";
+import { floors } from "../schema/floors.js";
+import { projectDevices } from "../schema/project-devices.js";
+import { projects } from "../schema/projects.js";
+import { rooms } from "../schema/rooms.js";
+import { executeProjectCommandTransaction } from "./project-command-transaction.persistence.js";
+
+export class DistributionBoardSubtreeProjectCommandRepository
+  implements DistributionBoardSubtreeProjectCommandStore
+{
+  constructor(private readonly database: AppDatabase) {}
+
+  capture(projectId: string, distributionBoardId: string) {
+    return this.captureFrom(
+      this.database,
+      projectId,
+      distributionBoardId
+    );
+  }
+
+  execute(input: ExecuteDistributionBoardSubtreeCommandInput) {
+    if (input.command.type === distributionBoardInsertSubtreeCommandType) {
+      assertDistributionBoardInsertSubtreeProjectCommand(input.command);
+    } else {
+      assertDistributionBoardDeleteSubtreeProjectCommand(input.command);
+    }
+    return executeProjectCommandTransaction(
+      this.database,
+      input,
+      (tx) => this.applyCommand(tx, input.projectId, input.command)
+    );
+  }
+
+  private applyCommand(
+    database: AppDatabase,
+    projectId: string,
+    command: DistributionBoardSubtreeProjectCommand
+  ) {
+    if (command.type === distributionBoardInsertSubtreeCommandType) {
+      this.insert(database, projectId, command.payload.snapshot);
+      return createDistributionBoardDeleteSubtreeProjectCommand(
+        command.payload.snapshot
+      );
+    }
+    if (command.type === distributionBoardDeleteSubtreeCommandType) {
+      const current = this.captureFrom(
+        database,
+        projectId,
+        command.payload.snapshot.distributionBoard.id
+      );
+      if (!sameSnapshot(current, command.payload.snapshot)) {
+        throw new Error(
+          "Distribution-board subtree changed before deletion."
+        );
+      }
+      const deleted = database
+        .delete(distributionBoards)
+        .where(
+          and(
+            eq(
+              distributionBoards.id,
+              current.distributionBoard.id
+            ),
+            eq(distributionBoards.projectId, projectId)
+          )
+        )
+        .run();
+      if (deleted.changes !== 1) {
+        throw new Error(
+          "Distribution-board subtree could not be deleted."
+        );
+      }
+      return createDistributionBoardInsertSubtreeProjectCommand(
+        command.payload.snapshot
+      );
+    }
+    throw new Error("Unsupported distribution-board subtree command.");
+  }
+
+  private captureFrom(
+    database: AppDatabase,
+    projectId: string,
+    distributionBoardId: string
+  ): DistributionBoardSubtreeSnapshot {
+    const distributionBoard = database
+      .select()
+      .from(distributionBoards)
+      .where(
+        and(
+          eq(distributionBoards.id, distributionBoardId),
+          eq(distributionBoards.projectId, projectId)
+        )
+      )
+      .get();
+    if (!distributionBoard) {
+      throw new Error("Distribution board not found.");
+    }
+    const circuitList = database
+      .select()
+      .from(circuitLists)
+      .where(
+        and(
+          eq(circuitLists.distributionBoardId, distributionBoard.id),
+          eq(circuitLists.projectId, projectId)
+        )
+      )
+      .get();
+    if (!circuitList) {
+      throw new Error("Distribution-board circuit list not found.");
+    }
+    const sections = database
+      .select()
+      .from(circuitSections)
+      .where(eq(circuitSections.circuitListId, circuitList.id))
+      .orderBy(asc(circuitSections.sortOrder), asc(circuitSections.id))
+      .all();
+    const components = database
+      .select()
+      .from(distributionBoardComponents)
+      .where(eq(distributionBoardComponents.circuitListId, circuitList.id))
+      .orderBy(
+        asc(distributionBoardComponents.sortOrder),
+        asc(distributionBoardComponents.id)
+      )
+      .all()
+      .map((component) => ({
+        component,
+        protectionDevice:
+          database
+            .select()
+            .from(distributionBoardComponentProtectionDevices)
+            .where(
+              eq(
+                distributionBoardComponentProtectionDevices.componentId,
+                component.id
+              )
+            )
+            .get() ?? null,
+      }));
+    const circuitSnapshots = database
+      .select()
+      .from(circuits)
+      .where(eq(circuits.circuitListId, circuitList.id))
+      .orderBy(asc(circuits.sortOrder), asc(circuits.id))
+      .all()
+      .map((circuit) => {
+        const { isReserve, ...values } = circuit;
+        return {
+          ...values,
+          isReserve: Boolean(isReserve),
+          deviceRows: database
+            .select()
+            .from(circuitDeviceRows)
+            .where(eq(circuitDeviceRows.circuitId, circuit.id))
+            .orderBy(
+              asc(circuitDeviceRows.sortOrder),
+              asc(circuitDeviceRows.id)
+            )
+            .all(),
+          protectionDevice:
+            database
+              .select()
+              .from(circuitProtectionDevices)
+              .where(eq(circuitProtectionDevices.circuitId, circuit.id))
+              .get() ?? null,
+        };
+      });
+    const snapshot: DistributionBoardSubtreeSnapshot = {
+      distributionBoard,
+      circuitList,
+      sections,
+      components,
+      circuits: circuitSnapshots,
+    };
+    assertDistributionBoardSubtreeSnapshot(snapshot);
+    return snapshot;
+  }
+
+  private insert(
+    database: AppDatabase,
+    projectId: string,
+    snapshot: DistributionBoardSubtreeSnapshot
+  ) {
+    assertDistributionBoardSubtreeSnapshot(snapshot);
+    if (
+      snapshot.distributionBoard.projectId !== projectId ||
+      snapshot.circuitList.projectId !== projectId
+    ) {
+      throw new Error(
+        "Distribution-board subtree belongs to another project."
+      );
+    }
+    this.assertProjectReferences(database, projectId, snapshot);
+    this.assertIdsAvailable(database, snapshot);
+
+    database
+      .insert(distributionBoards)
+      .values(snapshot.distributionBoard)
+      .run();
+    database.insert(circuitLists).values(snapshot.circuitList).run();
+    if (snapshot.sections.length > 0) {
+      database.insert(circuitSections).values(snapshot.sections).run();
+    }
+    for (const entry of snapshot.components) {
+      database
+        .insert(distributionBoardComponents)
+        .values(entry.component)
+        .run();
+      if (entry.protectionDevice !== null) {
+        database
+          .insert(distributionBoardComponentProtectionDevices)
+          .values(entry.protectionDevice)
+          .run();
+      }
+    }
+    for (const circuit of snapshot.circuits) {
+      const { deviceRows, protectionDevice, isReserve, ...values } =
+        circuit;
+      database
+        .insert(circuits)
+        .values({ ...values, isReserve: isReserve ? 1 : 0 })
+        .run();
+      if (protectionDevice !== null && protectionDevice !== undefined) {
+        database
+          .insert(circuitProtectionDevices)
+          .values(protectionDevice)
+          .run();
+      }
+      if (deviceRows.length > 0) {
+        database.insert(circuitDeviceRows).values(deviceRows).run();
+      }
+    }
+  }
+
+  private assertProjectReferences(
+    database: AppDatabase,
+    projectId: string,
+    snapshot: DistributionBoardSubtreeSnapshot
+  ) {
+    const project = database
+      .select({
+        enabledSupplyTypes:
+          projects.enabledDistributionBoardSupplyTypes,
+      })
+      .from(projects)
+      .where(eq(projects.id, projectId))
+      .get();
+    if (!project) {
+      throw new Error("Project not found.");
+    }
+    if (
+      snapshot.distributionBoard.supplyType !== null &&
+      !project.enabledSupplyTypes.includes(
+        snapshot.distributionBoard.supplyType
+      )
+    ) {
+      throw new Error(
+        "Distribution-board subtree uses a disabled supply type."
+      );
+    }
+    if (snapshot.distributionBoard.floorId !== null) {
+      const floor = database
+        .select({ projectId: floors.projectId })
+        .from(floors)
+        .where(eq(floors.id, snapshot.distributionBoard.floorId))
+        .get();
+      if (!floor || floor.projectId !== projectId) {
+        throw new Error(
+          "Distribution-board floor does not belong to project."
+        );
+      }
+    }
+    const linkedProjectDeviceIds = uniqueStrings(
+      snapshot.circuits.flatMap((circuit) =>
+        circuit.deviceRows.flatMap((row) =>
+          row.linkedProjectDeviceId === null
+            ? []
+            : [row.linkedProjectDeviceId]
+        )
+      )
+    );
+    if (linkedProjectDeviceIds.length > 0) {
+      const references = database
+        .select({ id: projectDevices.id, projectId: projectDevices.projectId })
+        .from(projectDevices)
+        .where(inArray(projectDevices.id, linkedProjectDeviceIds))
+        .all();
+      if (
+        references.length !== linkedProjectDeviceIds.length ||
+        references.some((reference) => reference.projectId !== projectId)
+      ) {
+        throw new Error(
+          "Distribution-board project-device reference is invalid."
+        );
+      }
+    }
+    const roomIds = uniqueStrings(
+      snapshot.circuits.flatMap((circuit) =>
+        circuit.deviceRows.flatMap((row) =>
+          row.roomId === null ? [] : [row.roomId]
+        )
+      )
+    );
+    if (roomIds.length > 0) {
+      const references = database
+        .select({ id: rooms.id, projectId: rooms.projectId })
+        .from(rooms)
+        .where(inArray(rooms.id, roomIds))
+        .all();
+      if (
+        references.length !== roomIds.length ||
+        references.some((reference) => reference.projectId !== projectId)
+      ) {
+        throw new Error("Distribution-board room reference is invalid.");
+      }
+    }
+  }
+
+  private assertIdsAvailable(
+    database: AppDatabase,
+    snapshot: DistributionBoardSubtreeSnapshot
+  ) {
+    const sectionIds = snapshot.sections.map((section) => section.id);
+    const componentIds = snapshot.components.map(
+      ({ component }) => component.id
+    );
+    const circuitIds = snapshot.circuits.map((circuit) => circuit.id);
+    const deviceRowIds = snapshot.circuits.flatMap((circuit) =>
+      circuit.deviceRows.map((row) => row.id)
+    );
+    const conflicts = [
+      database
+        .select({ id: distributionBoards.id })
+        .from(distributionBoards)
+        .where(eq(distributionBoards.id, snapshot.distributionBoard.id))
+        .get(),
+      database
+        .select({ id: circuitLists.id })
+        .from(circuitLists)
+        .where(eq(circuitLists.id, snapshot.circuitList.id))
+        .get(),
+      sectionIds.length === 0
+        ? undefined
+        : database
+            .select({ id: circuitSections.id })
+            .from(circuitSections)
+            .where(inArray(circuitSections.id, sectionIds))
+            .limit(1)
+            .get(),
+      componentIds.length === 0
+        ? undefined
+        : database
+            .select({ id: distributionBoardComponents.id })
+            .from(distributionBoardComponents)
+            .where(inArray(distributionBoardComponents.id, componentIds))
+            .limit(1)
+            .get(),
+      circuitIds.length === 0
+        ? undefined
+        : database
+            .select({ id: circuits.id })
+            .from(circuits)
+            .where(inArray(circuits.id, circuitIds))
+            .limit(1)
+            .get(),
+      deviceRowIds.length === 0
+        ? undefined
+        : database
+            .select({ id: circuitDeviceRows.id })
+            .from(circuitDeviceRows)
+            .where(inArray(circuitDeviceRows.id, deviceRowIds))
+            .limit(1)
+            .get(),
+    ];
+    if (conflicts.some(Boolean)) {
+      throw new Error("Distribution-board subtree id already exists.");
+    }
+  }
+}
+
+function uniqueStrings(values: string[]) {
+  return [...new Set(values)];
+}
+
+function sameSnapshot(
+  left: DistributionBoardSubtreeSnapshot,
+  right: DistributionBoardSubtreeSnapshot
+) {
+  return canonicalJson(left) === canonicalJson(right);
+}
+
+function canonicalJson(value: unknown): string {
+  if (Array.isArray(value)) {
+    return `[${value.map(canonicalJson).join(",")}]`;
+  }
+  if (value !== null && typeof value === "object") {
+    return `{${Object.entries(value)
+      .sort(([left], [right]) => left.localeCompare(right))
+      .map(
+        ([key, child]) =>
+          `${JSON.stringify(key)}:${canonicalJson(child)}`
+      )
+      .join(",")}}`;
+  }
+  return JSON.stringify(value) ?? "null";
+}
@@ -1,4 +1,4 @@
-import { asc, eq } from "drizzle-orm";
+import { and, asc, eq } from "drizzle-orm";
 import type { AppDatabase } from "../database-context.js";
 import { floors } from "../schema/floors.js";

@@ -13,4 +13,12 @@ export class FloorRepository {
      .where(eq(floors.projectId, projectId))
      .orderBy(asc(floors.sortOrder), asc(floors.name));
  }
+
+  async findById(projectId: string, floorId: string) {
+    return this.database
+      .select()
+      .from(floors)
+      .where(and(eq(floors.projectId, projectId), eq(floors.id, floorId)))
+      .get() ?? null;
+  }
 }
@@ -1,142 +0,0 @@
-import crypto from "node:crypto";
-import { eq, inArray, isNull } from "drizzle-orm";
-import type {
-  LegacyMigrationCircuitInput,
-  LegacyMigrationReportInput,
-} from "../../domain/ports/legacy-consumer-migration.store.js";
-import type { AppDatabase } from "../database-context.js";
-import { circuitDeviceRows } from "../schema/circuit-device-rows.js";
-import { circuits } from "../schema/circuits.js";
-import { consumers } from "../schema/consumers.js";
-import { legacyConsumerCircuitMigrations } from "../schema/legacy-consumer-circuit-migrations.js";
-import { legacyConsumerMigrationReports } from "../schema/legacy-consumer-migration-report.js";
-import { toCircuitDeviceRowCreateValues } from "./circuit-device-row.persistence.js";
-import { toCircuitCreateValues } from "./circuit.persistence.js";
-
-export class LegacyConsumerMigrationRepository {
-  constructor(private readonly database: AppDatabase) {}
-
-  async listSourceConsumersByCircuitList(circuitListId: string) {
-    return this.database
-      .select()
-      .from(consumers)
-      .where(eq(consumers.circuitListId, circuitListId));
-  }
-
-  async listUnmigratedConsumers() {
-    return this.database
-      .select({
-        id: consumers.id,
-        projectId: consumers.projectId,
-        circuitListId: consumers.circuitListId,
-      })
-      .from(consumers)
-      .leftJoin(
-        legacyConsumerCircuitMigrations,
-        eq(legacyConsumerCircuitMigrations.consumerId, consumers.id)
-      )
-      .where(isNull(legacyConsumerCircuitMigrations.consumerId));
-  }
-
-  async listMigratedConsumerIds(circuitListId: string) {
-    const rows = await this.database
-      .select({ consumerId: legacyConsumerCircuitMigrations.consumerId })
-      .from(legacyConsumerCircuitMigrations)
-      .where(eq(legacyConsumerCircuitMigrations.circuitListId, circuitListId));
-    return rows.map((row) => row.consumerId);
-  }
-
-  persistCircuitListMigration(input: {
-    circuitListId: string;
-    circuits: LegacyMigrationCircuitInput[];
-    report: LegacyMigrationReportInput;
-  }) {
-    if (input.circuits.some((entry) => entry.circuit.circuitListId !== input.circuitListId)) {
-      throw new Error("All migrated circuits must belong to the target circuit list.");
-    }
-
-    const consumerIds = input.circuits.flatMap((entry) =>
-      entry.deviceRows.map((row) => row.legacyConsumerId)
-    );
-    if (new Set(consumerIds).size !== consumerIds.length) {
-      throw new Error("A legacy consumer may only be migrated once per operation.");
-    }
-
-    const preparedCircuits = input.circuits.map((entry) => {
-      const circuitId = crypto.randomUUID();
-      return {
-        circuitId,
-        circuitValues: toCircuitCreateValues(circuitId, entry.circuit),
-        rows: entry.deviceRows.map((row) => {
-          const rowId = crypto.randomUUID();
-          return {
-            consumerId: row.legacyConsumerId,
-            rowId,
-            rowValues: toCircuitDeviceRowCreateValues(rowId, {
-              ...row,
-              circuitId,
-            }),
-          };
-        }),
-      };
-    });
-    const createdAtIso = new Date().toISOString();
-
-    this.database.transaction((tx) => {
-      if (consumerIds.length > 0) {
-        const existingMappings = tx
-          .select({ consumerId: legacyConsumerCircuitMigrations.consumerId })
-          .from(legacyConsumerCircuitMigrations)
-          .where(inArray(legacyConsumerCircuitMigrations.consumerId, consumerIds))
-          .all();
-        if (existingMappings.length > 0) {
-          throw new Error("A legacy consumer was migrated before this operation completed.");
-        }
-      }
-
-      for (const preparedCircuit of preparedCircuits) {
-        tx.insert(circuits).values(preparedCircuit.circuitValues).run();
-        for (const row of preparedCircuit.rows) {
-          tx.insert(circuitDeviceRows).values(row.rowValues).run();
-          tx
-            .insert(legacyConsumerCircuitMigrations)
-            .values({
-              consumerId: row.consumerId,
-              circuitId: preparedCircuit.circuitId,
-              circuitDeviceRowId: row.rowId,
-              circuitListId: input.circuitListId,
-              createdAtIso,
-            })
-            .run();
-        }
-      }
-
-      const reportValues = {
-        ...input.report,
-        createdAtIso,
-      };
-      const existingReport = tx
-        .select({ id: legacyConsumerMigrationReports.id })
-        .from(legacyConsumerMigrationReports)
-        .where(eq(legacyConsumerMigrationReports.circuitListId, input.circuitListId))
-        .limit(1)
-        .all();
-      if (existingReport.length > 0) {
-        tx
-          .update(legacyConsumerMigrationReports)
-          .set(reportValues)
-          .where(eq(legacyConsumerMigrationReports.id, existingReport[0].id))
-          .run();
-      } else {
-        tx
-          .insert(legacyConsumerMigrationReports)
-          .values({
-            id: crypto.randomUUID(),
-            circuitListId: input.circuitListId,
-            ...reportValues,
-          })
-          .run();
-      }
-    });
-  }
-}
@@ -34,7 +34,6 @@ const circuitDeviceRowSnapshotFields = [
  "id",
  "circuitId",
  "linkedProjectDeviceId",
-  "legacyConsumerId",
  "sortOrder",
  "name",
  "displayName",
@@ -2,16 +2,22 @@ import { and, eq } from "drizzle-orm";
 import {
  assertProjectFloorDeleteProjectCommand,
  assertProjectFloorInsertProjectCommand,
+  assertProjectFloorUpdateProjectCommand,
  assertProjectRoomDeleteProjectCommand,
  assertProjectRoomInsertProjectCommand,
+  assertProjectRoomUpdateProjectCommand,
  createProjectFloorDeleteProjectCommand,
  createProjectFloorInsertProjectCommand,
+  createProjectFloorUpdateProjectCommand,
  createProjectRoomDeleteProjectCommand,
  createProjectRoomInsertProjectCommand,
+  createProjectRoomUpdateProjectCommand,
  projectFloorDeleteCommandType,
  projectFloorInsertCommandType,
+  projectFloorUpdateCommandType,
  projectRoomDeleteCommandType,
  projectRoomInsertCommandType,
+  projectRoomUpdateCommandType,
  type ProjectFloorSnapshot,
  type ProjectLocationStructureProjectCommand,
  type ProjectRoomSnapshot,
@@ -22,7 +28,6 @@ import type {
 } from "../../domain/ports/project-location-structure-project-command.store.js";
 import type { AppDatabase } from "../database-context.js";
 import { circuitDeviceRows } from "../schema/circuit-device-rows.js";
-import { consumers } from "../schema/consumers.js";
 import { floors } from "../schema/floors.js";
 import { distributionBoards } from "../schema/distribution-boards.js";
 import { projects } from "../schema/projects.js";
@@ -63,6 +68,9 @@ export class ProjectLocationStructureProjectCommandRepository
          projectId,
          command.payload.floor
        );
+      case projectFloorUpdateCommandType:
+        assertProjectFloorUpdateProjectCommand(command);
+        return this.updateFloor(database, projectId, command.payload.expected, command.payload.target);
      case projectRoomInsertCommandType:
        assertProjectRoomInsertProjectCommand(command);
        return this.insertRoom(
@@ -77,6 +85,9 @@ export class ProjectLocationStructureProjectCommandRepository
          projectId,
          command.payload.room
        );
+      case projectRoomUpdateCommandType:
+        assertProjectRoomUpdateProjectCommand(command);
+        return this.updateRoom(database, projectId, command.payload.expected, command.payload.target);
    }
  }

@@ -127,7 +138,7 @@ export class ProjectLocationStructureProjectCommandRepository
      .get();
    if (referencedRoom) {
      throw new Error(
-        "A project floor with assigned rooms cannot be removed by history."
+        "Die Etage kann nicht gelöscht werden, solange Räume zugeordnet sind."
      );
    }
    const referencedDistributionBoard = database
@@ -138,7 +149,7 @@ export class ProjectLocationStructureProjectCommandRepository
      .get();
    if (referencedDistributionBoard) {
      throw new Error(
-        "A project floor assigned to a distribution board cannot be removed by history."
+        "Die Etage kann nicht gelöscht werden, solange eine Verteilung zugeordnet ist."
      );
    }
    const deleted = database
@@ -192,6 +203,70 @@ export class ProjectLocationStructureProjectCommandRepository
    return createProjectRoomDeleteProjectCommand(room);
  }

+  private updateFloor(
+    database: AppDatabase,
+    projectId: string,
+    expected: ProjectFloorSnapshot,
+    target: ProjectFloorSnapshot
+  ) {
+    const persisted = database
+      .select()
+      .from(floors)
+      .where(and(eq(floors.id, expected.id), eq(floors.projectId, projectId)))
+      .get();
+    if (!persisted || !sameRecord(expected, persisted)) {
+      throw new Error("Project floor changed before update.");
+    }
+    const updated = database
+      .update(floors)
+      .set({ name: target.name })
+      .where(and(eq(floors.id, expected.id), eq(floors.projectId, projectId)))
+      .run();
+    if (updated.changes !== 1) {
+      throw new Error("Die Etage konnte nicht aktualisiert werden.");
+    }
+    return createProjectFloorUpdateProjectCommand(target, expected);
+  }
+
+  private updateRoom(
+    database: AppDatabase,
+    projectId: string,
+    expected: ProjectRoomSnapshot,
+    target: ProjectRoomSnapshot
+  ) {
+    const persisted = database
+      .select()
+      .from(rooms)
+      .where(and(eq(rooms.id, expected.id), eq(rooms.projectId, projectId)))
+      .get();
+    if (!persisted || !sameRecord(expected, persisted)) {
+      throw new Error("Project room changed before update.");
+    }
+    if (target.floorId) {
+      const targetFloor = database
+        .select({ id: floors.id })
+        .from(floors)
+        .where(and(eq(floors.id, target.floorId), eq(floors.projectId, projectId)))
+        .get();
+      if (!targetFloor) {
+        throw new Error("Project room references a foreign floor.");
+      }
+    }
+    const updated = database
+      .update(rooms)
+      .set({
+        floorId: target.floorId,
+        roomNumber: target.roomNumber,
+        roomName: target.roomName,
+      })
+      .where(and(eq(rooms.id, expected.id), eq(rooms.projectId, projectId)))
+      .run();
+    if (updated.changes !== 1) {
+      throw new Error("Der Raum konnte nicht aktualisiert werden.");
+    }
+    return createProjectRoomUpdateProjectCommand(target, expected);
+  }
+
  private deleteRoom(
    database: AppDatabase,
    projectId: string,
@@ -216,15 +291,9 @@ export class ProjectLocationStructureProjectCommandRepository
      .where(eq(circuitDeviceRows.roomId, expected.id))
      .limit(1)
      .get();
-    const referencedLegacyConsumer = database
-      .select({ id: consumers.id })
-      .from(consumers)
-      .where(eq(consumers.roomId, expected.id))
-      .limit(1)
-      .get();
-    if (referencedDeviceRow || referencedLegacyConsumer) {
+    if (referencedDeviceRow) {
      throw new Error(
-        "A referenced project room cannot be removed by history."
+        "Der Raum kann nicht gelöscht werden, solange er in einem Stromkreis verwendet wird."
      );
    }
    const deleted = database
@@ -2,9 +2,6 @@ import { and, eq, isNotNull } from "drizzle-orm";
 import {
  assertProjectSettingsUpdateProjectCommand,
  createProjectSettingsUpdateProjectCommand,
-  legacyProjectSettingsUpdateCommandSchemaVersion,
-  normalizeProjectSettingsValues,
-  previousProjectSettingsUpdateCommandSchemaVersion,
  type ProjectSettingsValues,
 } from "../../domain/models/project-settings-project-command.model.js";
 import type {
@@ -43,49 +40,22 @@ export class ProjectSettingsProjectCommandRepository
    if (!current) {
      throw new Error("Project not found.");
    }
-    const target = normalizeProjectSettingsValues(input.command, current);
+    const target = input.command.payload;
    if (projectSettingsEqual(current, target)) {
      throw new Error("Project settings did not change.");
    }

-    const inverse =
-      input.command.schemaVersion ===
-      legacyProjectSettingsUpdateCommandSchemaVersion
-        ? {
-            schemaVersion: legacyProjectSettingsUpdateCommandSchemaVersion,
-            type: input.command.type,
-            payload: {
-              singlePhaseVoltageV: current.singlePhaseVoltageV,
-              threePhaseVoltageV: current.threePhaseVoltageV,
-            },
-          }
-        : input.command.schemaVersion ===
-            previousProjectSettingsUpdateCommandSchemaVersion
-          ? {
-              schemaVersion:
-                previousProjectSettingsUpdateCommandSchemaVersion,
-              type: input.command.type,
-              payload: {
-                name: current.name,
-                internalProjectNumber: current.internalProjectNumber,
-                externalProjectNumber: current.externalProjectNumber,
-                buildingOwner: current.buildingOwner,
-                description: current.description,
-                singlePhaseVoltageV: current.singlePhaseVoltageV,
-                threePhaseVoltageV: current.threePhaseVoltageV,
-              },
-            }
-          : createProjectSettingsUpdateProjectCommand({
-            name: current.name,
-            internalProjectNumber: current.internalProjectNumber,
-            externalProjectNumber: current.externalProjectNumber,
-            buildingOwner: current.buildingOwner,
-            description: current.description,
-            singlePhaseVoltageV: current.singlePhaseVoltageV,
-            threePhaseVoltageV: current.threePhaseVoltageV,
-            enabledDistributionBoardSupplyTypes:
-              current.enabledDistributionBoardSupplyTypes,
-          });
+    const inverse = createProjectSettingsUpdateProjectCommand({
+      name: current.name,
+      internalProjectNumber: current.internalProjectNumber,
+      externalProjectNumber: current.externalProjectNumber,
+      buildingOwner: current.buildingOwner,
+      description: current.description,
+      singlePhaseVoltageV: current.singlePhaseVoltageV,
+      threePhaseVoltageV: current.threePhaseVoltageV,
+      enabledDistributionBoardSupplyTypes:
+        current.enabledDistributionBoardSupplyTypes,
+    });
    assertDisabledSupplyTypesAreUnused(tx, input.projectId, target);
    const updated = tx
      .update(projects)
@@ -4,14 +4,8 @@ import { ProjectRevisionConflictError } from "../../domain/errors/project-revisi
 import { ProjectSnapshotNameConflictError } from "../../domain/errors/project-snapshot-name-conflict.error.js";
 import { createProjectStateRestoreCommand } from "../../domain/models/project-state-restore-command.model.js";
 import {
-  distributionBoardProjectStateSnapshotSchemaVersion,
  deserializeProjectStateSnapshot,
-  legacyProjectStateSnapshotSchemaVersion,
-  previousProjectStateSnapshotSchemaVersion,
  projectStateSnapshotSchemaVersion,
-  simultaneityFactorProjectStateSnapshotSchemaVersion,
-  supplyTypesProjectStateSnapshotSchemaVersion,
-  voltageProjectStateSnapshotSchemaVersion,
 } from "../../domain/models/project-state-snapshot.model.js";
 import type {
  CreateNamedProjectSnapshotInput,
@@ -144,19 +138,7 @@ export class ProjectSnapshotRepository implements ProjectSnapshotStore {
    if (actualChecksum !== stored.payloadSha256) {
      throw new Error("Project snapshot checksum verification failed.");
    }
-    if (
-      stored.schemaVersion !== legacyProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !== previousProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !==
-        distributionBoardProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !==
-        supplyTypesProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !==
-        voltageProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !==
-        simultaneityFactorProjectStateSnapshotSchemaVersion &&
-      stored.schemaVersion !== projectStateSnapshotSchemaVersion
-    ) {
+    if (stored.schemaVersion !== projectStateSnapshotSchemaVersion) {
      throw new Error("Project snapshot schema version is not supported.");
    }
    const targetState = deserializeProjectStateSnapshot(stored.payloadJson);
@@ -18,13 +18,10 @@ import { circuitLists } from "../schema/circuit-lists.js";
 import { circuitProtectionDevices } from "../schema/circuit-protection-devices.js";
 import { circuitSections } from "../schema/circuit-sections.js";
 import { circuits } from "../schema/circuits.js";
-import { consumers } from "../schema/consumers.js";
 import { distributionBoardComponentProtectionDevices } from "../schema/distribution-board-component-protection-devices.js";
 import { distributionBoardComponents } from "../schema/distribution-board-components.js";
 import { distributionBoards } from "../schema/distribution-boards.js";
 import { floors } from "../schema/floors.js";
-import { legacyConsumerCircuitMigrations } from "../schema/legacy-consumer-circuit-migrations.js";
-import { legacyConsumerMigrationReports } from "../schema/legacy-consumer-migration-report.js";
 import { projectDevices } from "../schema/project-devices.js";
 import { projectChangeSets } from "../schema/project-change-sets.js";
 import { projects } from "../schema/projects.js";
@@ -186,10 +183,6 @@ function replaceProjectState(
  database: AppDatabase,
  state: ProjectStateSnapshot
 ) {
-  const upgradeOnlyData = captureUpgradeOnlyData(
-    database,
-    state.project.id
-  );
  database
    .delete(distributionBoards)
    .where(eq(distributionBoards.projectId, state.project.id))
@@ -257,136 +250,6 @@ function replaceProjectState(
    circuitDeviceRows,
    state.circuits.flatMap((circuit) => circuit.deviceRows)
  );
-  restoreCompatibleUpgradeOnlyData(database, state, upgradeOnlyData);
-}
-
-function captureUpgradeOnlyData(
-  database: AppDatabase,
-  projectId: string
-) {
-  const consumerLinks = database
-    .select({
-      id: consumers.id,
-      distributionBoardId: consumers.distributionBoardId,
-      circuitListId: consumers.circuitListId,
-      projectDeviceId: consumers.projectDeviceId,
-      roomId: consumers.roomId,
-    })
-    .from(consumers)
-    .where(eq(consumers.projectId, projectId))
-    .all();
-  const migrationMappings = database
-    .select({
-      consumerId: legacyConsumerCircuitMigrations.consumerId,
-      circuitId: legacyConsumerCircuitMigrations.circuitId,
-      circuitDeviceRowId:
-        legacyConsumerCircuitMigrations.circuitDeviceRowId,
-      circuitListId: legacyConsumerCircuitMigrations.circuitListId,
-      createdAtIso: legacyConsumerCircuitMigrations.createdAtIso,
-    })
-    .from(legacyConsumerCircuitMigrations)
-    .innerJoin(
-      circuitLists,
-      eq(
-        circuitLists.id,
-        legacyConsumerCircuitMigrations.circuitListId
-      )
-    )
-    .where(eq(circuitLists.projectId, projectId))
-    .all();
-  const migrationReports = database
-    .select({
-      id: legacyConsumerMigrationReports.id,
-      circuitListId: legacyConsumerMigrationReports.circuitListId,
-      legacyConsumerCount:
-        legacyConsumerMigrationReports.legacyConsumerCount,
-      createdCircuitCount:
-        legacyConsumerMigrationReports.createdCircuitCount,
-      createdDeviceRowCount:
-        legacyConsumerMigrationReports.createdDeviceRowCount,
-      duplicateGroupedCount:
-        legacyConsumerMigrationReports.duplicateGroupedCount,
-      generatedIdentifierCount:
-        legacyConsumerMigrationReports.generatedIdentifierCount,
-      unassignedRowCount:
-        legacyConsumerMigrationReports.unassignedRowCount,
-      warningsJson: legacyConsumerMigrationReports.warningsJson,
-      generatedIdentifiersJson:
-        legacyConsumerMigrationReports.generatedIdentifiersJson,
-      duplicateGroupsJson:
-        legacyConsumerMigrationReports.duplicateGroupsJson,
-      createdAtIso: legacyConsumerMigrationReports.createdAtIso,
-    })
-    .from(legacyConsumerMigrationReports)
-    .innerJoin(
-      circuitLists,
-      eq(circuitLists.id, legacyConsumerMigrationReports.circuitListId)
-    )
-    .where(eq(circuitLists.projectId, projectId))
-    .all();
-  return { consumerLinks, migrationMappings, migrationReports };
-}
-
-function restoreCompatibleUpgradeOnlyData(
-  database: AppDatabase,
-  state: ProjectStateSnapshot,
-  data: ReturnType<typeof captureUpgradeOnlyData>
-) {
-  const boardIds = new Set(
-    state.distributionBoards.map((entry) => entry.id)
-  );
-  const listIds = new Set(state.circuitLists.map((entry) => entry.id));
-  const deviceIds = new Set(
-    state.projectDevices.map((entry) => entry.id)
-  );
-  const roomIds = new Set(state.rooms.map((entry) => entry.id));
-  const circuitIds = new Set(state.circuits.map((entry) => entry.id));
-  const rowIds = new Set(
-    state.circuits.flatMap((circuit) =>
-      circuit.deviceRows.map((entry) => entry.id)
-    )
-  );
-
-  for (const link of data.consumerLinks) {
-    database
-      .update(consumers)
-      .set({
-        distributionBoardId:
-          link.distributionBoardId &&
-          boardIds.has(link.distributionBoardId)
-            ? link.distributionBoardId
-            : null,
-        circuitListId:
-          link.circuitListId && listIds.has(link.circuitListId)
-            ? link.circuitListId
-            : null,
-        projectDeviceId:
-          link.projectDeviceId && deviceIds.has(link.projectDeviceId)
-            ? link.projectDeviceId
-            : null,
-        roomId:
-          link.roomId && roomIds.has(link.roomId) ? link.roomId : null,
-      })
-      .where(eq(consumers.id, link.id))
-      .run();
-  }
-  insertMany(
-    database,
-    legacyConsumerCircuitMigrations,
-    data.migrationMappings.filter(
-      (entry) =>
-        listIds.has(entry.circuitListId) &&
-        circuitIds.has(entry.circuitId) &&
-        rowIds.has(entry.circuitDeviceRowId)
-    )
-  );
-  insertMany(
-    database,
-    legacyConsumerMigrationReports,
-    data.migrationReports.filter((entry) =>
-      listIds.has(entry.circuitListId)
-    )
-  );
 }

 function insertMany<TTable extends Parameters<AppDatabase["insert"]>[0]>(
@@ -145,9 +145,6 @@ export function readProjectStateSnapshot(
      equipmentIdentifier: circuits.equipmentIdentifier,
      displayName: circuits.displayName,
      sortOrder: circuits.sortOrder,
-      protectionType: circuits.protectionType,
-      protectionRatedCurrent: circuits.protectionRatedCurrent,
-      protectionCharacteristic: circuits.protectionCharacteristic,
      cableType: circuits.cableType,
      cableCrossSection: circuits.cableCrossSection,
      cableLength: circuits.cableLength,
@@ -173,7 +170,6 @@ export function readProjectStateSnapshot(
      id: circuitDeviceRows.id,
      circuitId: circuitDeviceRows.circuitId,
      linkedProjectDeviceId: circuitDeviceRows.linkedProjectDeviceId,
-      legacyConsumerId: circuitDeviceRows.legacyConsumerId,
      sortOrder: circuitDeviceRows.sortOrder,
      name: circuitDeviceRows.name,
      displayName: circuitDeviceRows.displayName,
@@ -1,4 +1,4 @@
-import { asc, eq } from "drizzle-orm";
+import { and, asc, eq } from "drizzle-orm";
 import type { AppDatabase } from "../database-context.js";
 import { rooms } from "../schema/rooms.js";

@@ -13,4 +13,12 @@ export class RoomRepository {
      .where(eq(rooms.projectId, projectId))
      .orderBy(asc(rooms.roomNumber), asc(rooms.roomName));
  }
+
+  async findById(projectId: string, roomId: string) {
+    return this.database
+      .select()
+      .from(rooms)
+      .where(and(eq(rooms.projectId, projectId), eq(rooms.id, roomId)))
+      .get() ?? null;
+  }
 }
@@ -11,7 +11,6 @@ export const circuitDeviceRows = sqliteTable("circuit_device_rows", {
  linkedProjectDeviceId: text("linked_project_device_id").references(() => projectDevices.id, {
    onDelete: "set null",
  }),
-  legacyConsumerId: text("legacy_consumer_id"),
  sortOrder: integer("sort_order").notNull().default(0),
  name: text("name").notNull(),
  displayName: text("display_name").notNull(),
@@ -15,9 +15,6 @@ export const circuits = sqliteTable(
    equipmentIdentifier: text("equipment_identifier").notNull(),
    displayName: text("display_name"),
    sortOrder: integer("sort_order").notNull().default(0),
-    protectionType: text("protection_type"),
-    protectionRatedCurrent: real("protection_rated_current"),
-    protectionCharacteristic: text("protection_characteristic"),
    cableType: text("cable_type"),
    cableCrossSection: text("cable_cross_section"),
    cableLength: real("cable_length"),
@@ -1,47 +0,0 @@
-import { integer, real, sqliteTable, text } from "drizzle-orm/sqlite-core";
-import { circuitLists } from "./circuit-lists.js";
-import { distributionBoards } from "./distribution-boards.js";
-import { projectDevices } from "./project-devices.js";
-import { projects } from "./projects.js";
-import { rooms } from "./rooms.js";
-
-export const consumers = sqliteTable("consumers", {
-  id: text("id").primaryKey(),
-  projectId: text("project_id")
-    .notNull()
-    .references(() => projects.id, { onDelete: "cascade" }),
-  distributionBoardId: text("distribution_board_id").references(() => distributionBoards.id, {
-    onDelete: "set null",
-  }),
-  circuitListId: text("circuit_list_id").references(() => circuitLists.id, {
-    onDelete: "set null",
-  }),
-  projectDeviceId: text("project_device_id").references(() => projectDevices.id, {
-    onDelete: "set null",
-  }),
-  isLinkedToDevice: integer("is_linked_to_device").notNull().default(0),
-  roomId: text("room_id").references(() => rooms.id, {
-    onDelete: "set null",
-  }),
-  circuitNumber: text("circuit_number"),
-  description: text("description"),
-  name: text("name").notNull(),
-  category: text("category"),
-  deviceType: text("device_type"),
-  phaseType: text("phase_type"),
-  tradeOrCostGroup: text("trade_or_cost_group"),
-  group: text("group_name"),
-  protectionType: text("protection_type"),
-  protectionRatedCurrent: real("protection_rated_current"),
-  protectionCharacteristic: text("protection_characteristic"),
-  cableType: text("cable_type"),
-  cableCrossSection: text("cable_cross_section"),
-  comment: text("comment"),
-  quantity: integer("quantity").notNull(),
-  installedPowerPerUnitKw: real("installed_power_per_unit_kw").notNull(),
-  demandFactor: real("demand_factor").notNull(),
-  voltageV: real("voltage_v"),
-  phaseCount: integer("phase_count"),
-  powerFactor: real("power_factor"),
-  note: text("note"),
-});
@@ -1,19 +0,0 @@
-import { sqliteTable, text } from "drizzle-orm/sqlite-core";
-import { circuitDeviceRows } from "./circuit-device-rows.js";
-import { circuitLists } from "./circuit-lists.js";
-import { circuits } from "./circuits.js";
-
-export const legacyConsumerCircuitMigrations = sqliteTable("legacy_consumer_circuit_migrations", {
-  consumerId: text("consumer_id").primaryKey(),
-  circuitId: text("circuit_id")
-    .notNull()
-    .references(() => circuits.id, { onDelete: "cascade" }),
-  circuitDeviceRowId: text("circuit_device_row_id")
-    .notNull()
-    .references(() => circuitDeviceRows.id, { onDelete: "cascade" }),
-  circuitListId: text("circuit_list_id")
-    .notNull()
-    .references(() => circuitLists.id, { onDelete: "cascade" }),
-  createdAtIso: text("created_at_iso").notNull(),
-});
-
@@ -1,24 +0,0 @@
-import { integer, sqliteTable, text, unique } from "drizzle-orm/sqlite-core";
-import { circuitLists } from "./circuit-lists.js";
-
-export const legacyConsumerMigrationReports = sqliteTable(
-  "legacy_consumer_migration_reports",
-  {
-    id: text("id").primaryKey(),
-    circuitListId: text("circuit_list_id")
-      .notNull()
-      .references(() => circuitLists.id, { onDelete: "cascade" }),
-    legacyConsumerCount: integer("legacy_consumer_count").notNull(),
-    createdCircuitCount: integer("created_circuit_count").notNull(),
-    createdDeviceRowCount: integer("created_device_row_count").notNull(),
-    duplicateGroupedCount: integer("duplicate_grouped_count").notNull(),
-    generatedIdentifierCount: integer("generated_identifier_count").notNull(),
-    unassignedRowCount: integer("unassigned_row_count").notNull(),
-    warningsJson: text("warnings_json").notNull(),
-    generatedIdentifiersJson: text("generated_identifiers_json").notNull(),
-    duplicateGroupsJson: text("duplicate_groups_json").notNull(),
-    createdAtIso: text("created_at_iso").notNull(),
-  },
-  (table) => [unique("legacy_consumer_migration_reports_list_unique").on(table.circuitListId)]
-);
-
@@ -10,7 +10,6 @@ export interface CircuitDeviceRowSnapshot {
  id: string;
  circuitId: string;
  linkedProjectDeviceId: string | null;
-  legacyConsumerId: string | null;
  sortOrder: number;
  name: string;
  displayName: string;
@@ -101,7 +100,6 @@ export function assertCircuitDeviceRowInsertProjectCommand(
  assertNonEmptyString(row.id, "row.id");
  assertNonEmptyString(row.circuitId, "row.circuitId");
  assertNullableString(row.linkedProjectDeviceId, "row.linkedProjectDeviceId");
-  assertNullableString(row.legacyConsumerId, "row.legacyConsumerId");
  assertFiniteNumber(row.sortOrder, "row.sortOrder");
  assertNonEmptyString(row.name, "row.name");
  assertNonEmptyString(row.displayName, "row.displayName");
@@ -2,7 +2,6 @@ export interface CircuitDeviceRow {
  id: string;
  circuitId: string;
  linkedProjectDeviceId?: string;
-  legacyConsumerId?: string;
  sortOrder: number;
  name: string;
  displayName: string;
@@ -8,9 +8,6 @@ export interface CircuitUpdateValues {
  equipmentIdentifier: string;
  displayName: string | null;
  sortOrder: number;
-  protectionType: string | null;
-  protectionRatedCurrent: number | null;
-  protectionCharacteristic: string | null;
  cableType: string | null;
  cableCrossSection: string | null;
  cableLength: number | null;
@@ -118,7 +115,6 @@ function assertCircuitUpdateFieldValue(
    return;
  }
  if (
-    field === "protectionRatedCurrent" ||
    field === "cableLength" ||
    field === "voltage"
  ) {
@@ -147,9 +143,6 @@ function isCircuitUpdateField(value: string): value is CircuitUpdateField {
    "equipmentIdentifier",
    "displayName",
    "sortOrder",
-    "protectionType",
-    "protectionRatedCurrent",
-    "protectionCharacteristic",
    "cableType",
    "cableCrossSection",
    "cableLength",
@@ -0,0 +1,111 @@
+import { protectionDeviceConfigurationSchema } from "../../shared/validation/protection-device.schemas.js";
+import type {
+  BreakerTripCharacteristic,
+  FuseUtilizationCategory,
+  ProtectionDeviceType,
+  RcdType,
+} from "../../shared/constants/protection-device.js";
+import type { SerializedProjectCommand } from "./project-command.model.js";
+
+export const circuitProtectionUpdateCommandType =
+  "circuit-protection.update" as const;
+export const circuitProtectionUpdateCommandSchemaVersion = 1 as const;
+
+export interface CircuitProtectionSnapshot {
+  circuitId: string;
+  type: ProtectionDeviceType;
+  ratedCurrentA: number;
+  fuseUtilizationCategory: FuseUtilizationCategory | null;
+  tripCharacteristic: BreakerTripCharacteristic | null;
+  rcdType: RcdType | null;
+  ratedResidualCurrentMa: number | null;
+}
+
+interface CircuitProtectionUpdatePayload {
+  circuitId: string;
+  expected: CircuitProtectionSnapshot | null;
+  target: CircuitProtectionSnapshot | null;
+}
+
+export interface CircuitProtectionUpdateProjectCommand
+  extends SerializedProjectCommand<CircuitProtectionUpdatePayload> {
+  schemaVersion: typeof circuitProtectionUpdateCommandSchemaVersion;
+  type: typeof circuitProtectionUpdateCommandType;
+}
+
+export function createCircuitProtectionUpdateProjectCommand(
+  circuitId: string,
+  expected: CircuitProtectionSnapshot | null,
+  target: CircuitProtectionSnapshot | null
+): CircuitProtectionUpdateProjectCommand {
+  const command: CircuitProtectionUpdateProjectCommand = {
+    schemaVersion: circuitProtectionUpdateCommandSchemaVersion,
+    type: circuitProtectionUpdateCommandType,
+    payload: { circuitId, expected, target },
+  };
+  assertCircuitProtectionUpdateProjectCommand(command);
+  return command;
+}
+
+export function assertCircuitProtectionUpdateProjectCommand(
+  command: SerializedProjectCommand<unknown>
+): asserts command is CircuitProtectionUpdateProjectCommand {
+  if (
+    command.schemaVersion !== circuitProtectionUpdateCommandSchemaVersion ||
+    command.type !== circuitProtectionUpdateCommandType ||
+    !isPlainObject(command.payload) ||
+    Object.keys(command.payload).length !== 3
+  ) {
+    throw new Error("Unsupported circuit-protection update command.");
+  }
+  const { circuitId, expected, target } = command.payload;
+  if (typeof circuitId !== "string" || !circuitId.trim()) {
+    throw new Error("Circuit protection requires a circuit id.");
+  }
+  if (expected === null && target === null) {
+    throw new Error("Circuit protection update must change state.");
+  }
+  if (expected !== null) {
+    assertCircuitProtectionSnapshot(expected, circuitId);
+  }
+  if (target !== null) {
+    assertCircuitProtectionSnapshot(target, circuitId);
+  }
+  if (JSON.stringify(expected) === JSON.stringify(target)) {
+    throw new Error("Circuit protection update must change state.");
+  }
+}
+
+export function assertCircuitProtectionSnapshot(
+  value: unknown,
+  circuitId: string
+) {
+  if (
+    !isPlainObject(value) ||
+    Object.keys(value).length !== 7 ||
+    value.circuitId !== circuitId
+  ) {
+    throw new Error("Circuit-protection snapshot is invalid.");
+  }
+  const result = protectionDeviceConfigurationSchema.safeParse({
+    type: value.type,
+    ratedCurrentA: value.ratedCurrentA,
+    ...(value.fuseUtilizationCategory === null
+      ? {}
+      : { fuseUtilizationCategory: value.fuseUtilizationCategory }),
+    ...(value.tripCharacteristic === null
+      ? {}
+      : { tripCharacteristic: value.tripCharacteristic }),
+    ...(value.rcdType === null ? {} : { rcdType: value.rcdType }),
+    ...(value.ratedResidualCurrentMa === null
+      ? {}
+      : { ratedResidualCurrentMa: value.ratedResidualCurrentMa }),
+  });
+  if (!result.success) {
+    throw new Error("Circuit-protection configuration is invalid.");
+  }
+}
+
+function isPlainObject(value: unknown): value is Record<string, unknown> {
+  return value !== null && typeof value === "object" && !Array.isArray(value);
+}
@@ -5,6 +5,10 @@ import {
  type CircuitDeviceRowSnapshot,
 } from "./circuit-device-row-structure-project-command.model.js";
 import type { SerializedProjectCommand } from "./project-command.model.js";
+import {
+  assertCircuitProtectionSnapshot,
+  type CircuitProtectionSnapshot,
+} from "./circuit-protection-project-command.model.js";

 export const circuitInsertCommandType = "circuit.insert" as const;
 export const circuitDeleteCommandType = "circuit.delete" as const;
@@ -17,9 +21,6 @@ export interface CircuitSnapshot {
  equipmentIdentifier: string;
  displayName: string | null;
  sortOrder: number;
-  protectionType: string | null;
-  protectionRatedCurrent: number | null;
-  protectionCharacteristic: string | null;
  cableType: string | null;
  cableCrossSection: string | null;
  cableLength: number | null;
@@ -31,6 +32,7 @@ export interface CircuitSnapshot {
  isReserve: boolean;
  remark: string | null;
  deviceRows: CircuitDeviceRowSnapshot[];
+  protectionDevice?: CircuitProtectionSnapshot | null;
 }

 export interface CircuitInsertCommandPayload {
@@ -110,8 +112,6 @@ export function assertCircuitInsertProjectCommand(
  assertNullableString(circuit.displayName, "circuit.displayName");
  assertFiniteNumber(circuit.sortOrder, "circuit.sortOrder");
  for (const field of [
-    "protectionType",
-    "protectionCharacteristic",
    "cableType",
    "cableCrossSection",
    "rcdAssignment",
@@ -122,10 +122,6 @@ export function assertCircuitInsertProjectCommand(
  ] as const) {
    assertNullableString(circuit[field], `circuit.${field}`);
  }
-  assertNullableNonNegativeNumber(
-    circuit.protectionRatedCurrent,
-    "circuit.protectionRatedCurrent"
-  );
  assertNullableNonNegativeNumber(
    circuit.cableLength,
    "circuit.cableLength"
@@ -142,6 +138,15 @@ export function assertCircuitInsertProjectCommand(
  if (!Array.isArray(circuit.deviceRows)) {
    throw new Error("circuit.deviceRows must be an array.");
  }
+  if (
+    circuit.protectionDevice !== undefined &&
+    circuit.protectionDevice !== null
+  ) {
+    assertCircuitProtectionSnapshot(
+      circuit.protectionDevice,
+      circuit.id as string
+    );
+  }
  if (circuit.isReserve !== (circuit.deviceRows.length === 0)) {
    throw new Error(
      "Circuit reserve state must match whether device rows exist."
@@ -1,7 +1,6 @@
 export interface CircuitTreeDeviceRow {
  id: string;
  linkedProjectDeviceId?: string;
-  legacyConsumerId?: string;
  sortOrder: number;
  name: string;
  displayName: string;
@@ -29,9 +28,6 @@ export interface CircuitTreeCircuit {
  equipmentIdentifier: string;
  displayName?: string;
  sortOrder: number;
-  protectionType?: string;
-  protectionRatedCurrent?: number;
-  protectionCharacteristic?: string;
  cableType?: string;
  cableCrossSection?: string;
  cableLength?: number;
@@ -73,17 +69,6 @@ export interface CircuitTreeResponse {
  footerComponents: CircuitTreeComponent[];
 }

-export interface LegacyMigrationReport {
-  circuitListId: string;
-  legacyConsumerCount: number;
-  createdCircuitCount: number;
-  createdDeviceRowCount: number;
-  groupedDuplicateCircuitNumbers: Array<{ normalizedCircuitNumber: string; count: number }>;
-  generatedIdentifiers: string[];
-  unassignedRows: Array<{ consumerId: string; reason: string }>;
-  warnings: string[];
-}
-
 import type { CircuitGroupCategory } from "../../shared/constants/circuit-group.js";
 import type {
  DistributionBoardComponentPlacement,
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
jappel	43a3bb0b69	Align documentation with clean baseline	2026-07-31 16:41:37 +02:00
jappel	facf788ce8	Remove circuit structure preview	2026-07-31 14:52:37 +02:00
jappel	1eed19ef6b	Add editable project floors and rooms	2026-07-31 14:46:06 +02:00
jappel	1e3c721cfa	Derive project device phases from category	2026-07-31 14:37:45 +02:00
jappel	5fb81bab04	Support decimal commas and cell units	2026-07-31 14:33:47 +02:00
jappel	734a2bcfc4	Create clean release database baseline	2026-07-31 14:07:26 +02:00
jappel	5bee3cb103	Add distribution board copy and delete controls	2026-07-31 12:03:52 +02:00
jappel	86f1d42e60	Expose distribution board copy and delete API	2026-07-31 11:59:31 +02:00
jappel	0fd564a930	Persist complete distribution board subtrees	2026-07-31 11:57:10 +02:00
jappel	13693f64b1	Model complete distribution board subtrees	2026-07-31 11:51:46 +02:00
jappel	bd8dd09f79	Open circuit protection from grid cell	2026-07-31 10:02:11 +02:00
jappel	54874f9fcb	Render circuit protection values	2026-07-31 09:56:49 +02:00
jappel	2964205a27	Show circuit protection in saved layouts	2026-07-31 09:45:58 +02:00
jappel	f4bfef9071	Merge branch 'main' into feature/multiplesections	2026-07-31 09:00:39 +02:00
jappel	4a859f31b8	Complete protected circuit group phase	2026-07-31 08:59:12 +02:00
jappel	2d97fafce9	Restore circuit drag placement	2026-07-31 08:33:41 +02:00
jappel	7c8d4a7ddf	Document protected circuit groups	2026-07-31 08:06:10 +02:00
jappel	ab989cc637	Delete populated circuit groups safely	2026-07-31 08:01:55 +02:00
jappel	93ec294759	Move circuits between groups	2026-07-31 07:58:42 +02:00
jappel	be9c6f0d52	Renumber circuit groups explicitly	2026-07-31 07:53:07 +02:00
jappel	0cb280ddb2	Reorder circuit groups	2026-07-31 07:47:45 +02:00
jappel	8898117ed4	Configure circuit protection	2026-07-31 07:45:48 +02:00
jappel	18ca5eb3d4	Persist circuit protection updates	2026-07-31 07:37:38 +02:00
jappel	0c92fbd09e	Manage circuit groups	2026-07-31 07:32:46 +02:00
jappel	756e307bd8	Manage distribution board components	2026-07-31 07:29:25 +02:00
jappel	31589875b5	Render protected circuit structure	2026-07-31 07:22:26 +02:00
Grovy311	704f4df2a8	Apply Petrol/Volt/Kupfer design system and project sidebar Bring the Econsult-family design tokens (see design-system-econsult.md) into leistungsbilanz-ts and add a persistent sidebar for the projects area, mirroring elt-planung-suite / Einsatz-Orga. The sidebar lists all projects and, inside a project, jumps to its sections; the tree editor stays sidebar-free since it needs the full width. The projects overview page is decluttered to a single stacked column (create/import/global devices) now that the project list lives in the sidebar.	2026-07-30 17:40:11 +02:00
				`@@ -1 +0,0 @@`
				ALTER TABLE `circuits` ADD COLUMN `control_requirement` text;
				`@@ -1 +0,0 @@`
				ALTER TABLE `projects` ADD `enabled_distribution_board_supply_types` text DEFAULT '["AV","SV","EV","USV","MSR","SiBe"]' NOT NULL;
				`@@ -1 +0,0 @@`
				ALTER TABLE `distribution_boards` ADD `simultaneity_factor` real DEFAULT 1 NOT NULL;