Khalim Conn-Kowlessar fa131cca0b feat(conservatory): read §6.1 geometry through extractor + mapper ... RdSAP 10 §6.1 (PDF p.49) models a non-separated (heated) conservatory as part of the dwelling. Until now the Summary §5 block was reduced to an inert `has_conservatory` bool and the geometry (floor area, glazed perimeter, glazing, storey height) was dropped on both paths. Plumbing only — no cascade consumer yet (Slices B/C/D wire §3/§6): - ElmhurstSiteNotesExtractor reads the §5 Conservatory block into a new `Conservatory` site-notes record (scoped to §5 so the generic "Floor Area"/"Room Height" labels can't collide with §4 dimensions); - domain gains a frozen `SapConservatory` (floor area, glazed perimeter, double/single glazing, thermally-separated guard, equivalent storey count) on `EpcPropertyData.sap_conservatory`; - the Elmhurst mapper threads it through, dropping SEPARATED conservatories per §6.2 ("A separated conservatory ... is disregarded"). Verified against the simulated case-44 Summary (RefNo 001431): extracts floor_area=12.0, glazed_perimeter=9.0, double_glazed=True, 1 storey. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-16 15:37:05 +00:00
..
epc	feat(conservatory): read §6.1 geometry through extractor + mapper	2026-06-16 15:37:05 +00:00
__init__.py	further breaking up code	2023-07-20 12:24:34 +01:00
datatypes.py	further breaking up code	2023-07-20 12:24:34 +01:00
enums.py	completed build of new demo portfolio - some fixed required still	2023-11-20 14:42:16 +00:00