Add editable project floors and rooms

AGENTS.md

@@ -245,7 +245,7 @@ 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
@@ -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: