Khalim Conn-Kowlessar f326e4eb53 mapper: Elmhurst path populates roof_construction (int) for cross-mapper parity ... The gov-EPC API mapper sets BOTH roof_construction (int) and roof_construction_type (str, derived via _API_ROOF_CONSTRUCTION_TO_STR), but the Elmhurst mapper set only the string — leaving roof_construction None on every site-notes cert. The SAP cascade reads the STRING (so SAP cross-mapper parity always held), but consumers of the int (e.g. domain/sap10_ml/transform.py ML aggregates `main_dwelling_roof_ construction`) silently saw None on the Elmhurst path. New `_elmhurst_roof_construction_int` maps the Elmhurst roof-type code to the same SAP10 int the API lodges (F→1, PN→3, PA→4, PS→8, S/A→7), harvested from the committed Summary fixtures. Unlike the wall map it returns None (not a strict-raise) for unmapped codes: the int is not cascade-load-bearing, so an unknown roof must not block the cert (vaulted 5 / thatched 6 / NR omitted until a fixture surfaces them). The 6 hand-built U985 reference fixtures gain the matching roof_construction int (4/4/3 etc.) so test_from_elmhurst_site_notes_ matches_hand_built_* still asserts structural parity. SAP output is unchanged (cascade reads the string). §4 suite green (2407 passed); the two pre-existing stone-§5.6 sap10_ml failures are unrelated/out of scope. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-04 21:16:20 +00:00
..
epc	mapper: Elmhurst path populates roof_construction (int) for cross-mapper parity	2026-06-04 21:16:20 +00:00
magicplan	typing and renaming 🟪	2026-05-07 13:26:49 +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