Khalim Conn-Kowlessar 2ee1b35dca fix(modelling_e2e): persist Baseline Performance for lodged properties ... The handler wrote epc/spatial/solar/plan and marked the property modelled, but never established its Baseline Performance — so no row was created in property_baseline_performance for any property modelled through the Lambda (noticed on portfolio 796 / scenario 1268 / property 727218, a lodged property). Mirror the e2e runner: after the plan UoW commits (so the EPC is persisted for the orchestrator to re-hydrate), run PropertyBaselineOrchestrator for lodged properties. Predicted properties have no lodged figures and no persisted EPC, so they are skipped — consistent with the e2e runner and the ara_first_run Baseline stage. Verified 727218's baseline pipeline builds end-to-end in-memory (lodged_performance → CalculatorRebaseliner → bill → PropertyBaselinePerformance, reason pre_sap10). Tests: lodged path asserts the orchestrator runs once; prediction path asserts it does not. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-23 17:21:03 +00:00
..
local_handler	measured excluded plus get geospatial nearby stuff working	2026-06-22 16:12:16 +00:00
Dockerfile	move handler stuff to applications directory	2026-06-22 13:35:23 +00:00
handler.py	fix(modelling_e2e): persist Baseline Performance for lodged properties	2026-06-23 17:21:03 +00:00
modelling_e2e_trigger_body.py	process multiple properties in one message	2026-06-22 15:46:18 +00:00
requirements.txt	various fixes	2026-06-22 14:21:52 +00:00