Add public building project setting

docs/spec/06-future-sizing-and-calculations.md

@@ -14,12 +14,18 @@ Future suggestions or checks may include:
 - cable type
 - number of cores
 - cable cross-section
+- halogen-free cable or line requirement for public buildings
 - minimum cable cross-section based on current
 - maximum permissible cable length based on voltage drop
 - warning messages if cable length, cross-section or protection device do not match
 
 Users must remain able to manually override suggestions.
 
+The project-owned `isPublicBuilding` setting is the authoritative input for
+the later halogen-free selection rule. The setting is persisted now; this
+document does not yet define or implement the complete cable catalog or sizing
+algorithm.
+
 ## Initial Design Rule Examples
 
 These are common planning defaults, not a replacement for full norm-compliant calculation.

docs/spec/07-implementation-phases-todo.md

@@ -465,9 +465,9 @@ Implemented foundation:
 - ProjectDevice synchronization and disconnect endpoints also require
   `expectedRevision`; their UI undo uses project-wide persistent history and
   the obsolete direct restore/reconnect write paths are removed
-- project voltage settings use `project.update-settings`; both values, inverse,
-  revision and history transition commit atomically and the former direct
-  settings write is removed
+- project settings use `project.update-settings`; metadata, public-building
+  classification, voltage values, inverse, revision and history transition
+  commit atomically and the former direct settings write is removed
 - distribution-board setup uses `distribution-board.insert` with a complete
   stable board/list/default-section snapshot; Undo removes only an unchanged
   empty setup and the former direct controller write is removed

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

@@ -54,7 +54,7 @@ requirements and intended sequencing, not proof of implementation.
 
 The pre-release cleanup established the following compatibility boundary:
 
-- [x] Pre-release databases, portable JSON exports, logical snapshots and
+- [x] Pre-baseline 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.
@@ -109,9 +109,16 @@ The pre-release cleanup established the following compatibility boundary:
   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] Baseline migration `0000` and project-state schema version `1` store only
-  the canonical derived values. Pre-release imports are intentionally
-  unsupported.
+- [x] Baseline migration `0000` stores only canonical derived values.
+  Pre-baseline imports are intentionally unsupported.
+
+## Building Classification
+
+- [x] Store whether a project represents a public building.
+- [x] Edit the value in the project settings and preserve it through persistent
+  Undo/Redo, snapshots and portable project transfers.
+- [x] Provide the value as an explicit future sizing input for selecting
+  halogen-free cables and lines; automatic sizing remains deferred.
 
 ## Circuit List Power Summary
 

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

@@ -467,11 +467,11 @@ The supported logical project snapshot and portable JSON transfer must include:
 - circuit protection-device state
 - all new component relationships and sort positions
 
-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.
+Current project-state schema version `2` contains the complete supported
+structure above and the project building classification. It is shared by
+logical snapshots, restore, Undo/Redo and portable JSON transfer. Supported
+baseline version `1` is upgraded with the non-public default; payloads from
+before that baseline are rejected before any write.
 
 Migration `0000` creates the complete relational model on an empty database.
 New defaults apply when boards, groups or circuits are created; they never
@@ -545,7 +545,7 @@ Implemented persistence:
   one-to-one ownership boundaries
 - a trigger-maintained circuit-list registry rejects normalized BMK collisions
   across circuits and distribution-board components
-- snapshot schema version `1` includes group identity, distribution-board
+- snapshot schema version `2` 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