Khalim Conn-Kowlessar 694cdd9c23 feat(modelling): mark a Property as run via has_recommendations + updated_at ... The new pipeline left no per-Property record of a run (the old engine set property.has_recommendations and populated property_details_epc). Restore the marker: PropertyRepository.mark_modelled sets has_recommendations (true when the Plan carries measures, mirroring the old engine) and bumps updated_at, so a first-run under the new process is identifiable as updated_at >= 2026-06-01. ModellingOrchestrator marks each Property after its Scenarios (true if any Scenario yielded a measure); run_modelling_e2e's --persist path marks it too (its compute runs on in-memory fakes, so the DB UoW sets it directly). Adds the has_recommendations/updated_at columns to the PropertyRow mirror. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-16 23:34:33 +00:00
..
__init__.py	feat(property): Property aggregate + PropertyRepository (#1132)	2026-05-30 19:39:54 +00:00
prediction_target_attributes_reader.py	feat(epc-prediction): slice-5d target assembly + eligibility gate	2026-06-16 03:56:57 +00:00
property_override_postgres_repository.py	property override	2026-06-05 12:18:13 +00:00
property_override_repository.py	property override	2026-06-05 12:18:13 +00:00
property_postgres_repository.py	feat(modelling): mark a Property as run via has_recommendations + updated_at	2026-06-16 23:34:33 +00:00
property_repository.py	feat(modelling): mark a Property as run via has_recommendations + updated_at	2026-06-16 23:34:33 +00:00