Khalim Conn-Kowlessar 62e1d4b813 fix(product): deterministic catalogue pick by ordering get() by id ... ProductPostgresRepository.get took .first() with no ORDER BY, so when a measure type has several active material rows (the live catalogue holds 74 solar_pv, 5 high_heat_retention_storage_heaters) the chosen row — hence the cost and material_id — depended on the database's physical row order. Order by id so a re-seed prices the same product every time. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-08 20:35:45 +00:00
..
__init__.py	feat(modelling): ProductRepository + Postgres materials-table source	2026-06-03 08:32:38 +00:00
test_product_json_repository.py	feat(modelling): ProductJsonRepository behind the ProductRepository port	2026-06-03 09:49:02 +00:00
test_product_postgres_repository.py	fix(product): deterministic catalogue pick by ordering get() by id	2026-06-08 20:35:45 +00:00