Khalim Conn-Kowlessar edf1003dcf fix(epc): hydrate recorded performance, RHI, and dates on read ... The Baseline stage is the first consumer to read these off a persisted EPC end-to-end, surfacing three gaps that only manifest on real API data: - Only the 21.0.1 mapper copied through the recorded current-performance scalars (SAP rating, CO2, PEUI) and *no* mapper mapped the EPC band, so Lodged Performance raised for 17.x/18.0/19.0/20.0.0 certs. Overlay all four from the raw payload in `from_api_response`, once, for every schema version. - Likewise the `renewable_heat_incentive` block (baseline space/water-heating kWh) was only mapped by the 21.x paths. Gap-fill it centrally from the raw payload when a mapper left it unset. - The FE-owned `epc_property` date columns are Postgres `timestamp`s while the SQLModel mirror types them `str`, so a read hands back a `datetime` and `date.fromisoformat()` raised. Normalise via `_as_date()`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-17 01:45:18 +00:00
..
__init__.py	feat(epc): EPC persistence round-trip fidelity + JSONB code columns (Slice 1 #1129)	2026-05-30 19:26:18 +00:00
epc_postgres_repository.py	fix(epc): hydrate recorded performance, RHI, and dates on read	2026-06-17 01:45:18 +00:00
epc_repository.py	feat(epc-prediction): slice-5c predicted-EPC persistence slot	2026-06-16 03:50:19 +00:00