Khalim Conn-Kowlessar 0fb5da2f79 refactor(baseline): Performance.from_sap_result replaces the loose mapper ... PR feedback: the SapResult -> Performance mapping should be a method, not a free function you must know exists in the rebaseliner. Put the factory on the target as `Performance.from_sap_result`, beside its sibling `lodged_performance` and mirroring `Epc.from_sap_score` (the factory this mapping already calls). Not a `SapResult.to_performance()`: that would make the SAP calculator import `Performance` (a property_baseline type), re-introducing the engine->consumer coupling removed by the SapCalculator ABC. SapResult is a TYPE_CHECKING-only import in performance.py (the body only reads attributes), so the calculator module is not pulled in at runtime. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-02 13:59:25 +00:00
..
addresses	get rid of comments	2026-05-20 13:21:11 +00:00
fuel_rates	feat(fuel-rates): FuelRates snapshot + repository foundation (ADR-0014)	2026-06-02 09:29:07 +00:00
geospatial	feat(geospatial): GeospatialRepo — OS Open-UPRN coordinate lookup (#1131)	2026-05-30 19:55:46 +00:00
property	feat(property): Property aggregate + PropertyRepository (#1132)	2026-05-30 19:39:54 +00:00
property_baseline	refactor(baseline): Performance.from_sap_result replaces the loose mapper	2026-06-02 13:59:25 +00:00
sap10_calculator	refactor(baseline): SapCalculator ABC replaces the Calculator Protocol	2026-06-02 13:45:48 +00:00
sap10_ml	Slice S0380.109: Solid brick + insulation via §5.7 Table 13 + §5.8 Table 14 (RdSAP 10)	2026-05-30 18:10:33 +00:00
tasks	added postcode splitter rewrite to ddd	2026-05-19 16:35:09 +00:00
postcode.py	get rid of comments	2026-05-20 13:21:11 +00:00