Khalim Conn-Kowlessar ea988cfe52 feat(epc): provenance signals + effective-baseline portfolio table ... Theme 1 — EPC card provenance. New resolveProvenanceSignal (pure, unit- tested) + resolveProvenance expose provenanceSignal ("estimated" / "remodelled" / "none") and the lodged headline on property-meta. The building-passport card shows a "Lodged EPC" badge on re-modelled properties (even within-band), never on predicted ones; the existing "estimated from nearby homes" banner already covers predicted. Theme 2 — portfolio table. "Current EPC" + reporting now read the effective baseline (effectiveSapSql/effectiveEpcBandSql); a dedicated "Lodged EPC" column reads the source-gated lodged value (blank for predicted); a "Predicted" pill marks estimated rows; a provenance filter is added and the broken currentEpc/lodgedEpc filters (on null row columns) point at the effective/lodged baselines. Expected EPC now uses the default plan's post rating (expectedEpcRating, unit-tested) instead of current + Σ rec SAP, which double-counted across plans (732385: A→C); the same rec aggregate is scoped to the default plan, fixing the Cost column's 2x double-count. See ADR-0002. Pure logic covered by provenance.test.ts + expectedEpc.test.ts; SQL/query/UI verified against live properties 732385 and 729529. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-23 22:21:33 +00:00
..
epc.ts	added db filtereing	2026-01-05 17:30:58 +00:00
propertyFilters.ts	feat(epc): provenance signals + effective-baseline portfolio table	2026-06-23 22:21:33 +00:00
s3.ts	refactored with improve-code-archievture and grill-with-docs	2026-05-06 15:49:34 +00:00
sqs.ts	added trigger of sqs	2026-04-18 18:55:19 +00:00