mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-07-27 23:35:01 +00:00
6c4f73cc91
5 Paxton Place (deal 507639151845, uprn 10070864419) had a STALE fixture. The same PAS Hub survey (report B74AA5A4-…, inspected 29 Jun 2026) has two accredited revisions in S3: V2 (uploaded 6 Jul, ventilation "Natural", SAP 80) and V5 (uploaded 14–15 Jul, ventilation "Mechanical Extract - Centralised", SAP 76 — the current version). Our committed fixture was the superseded V2; the portfolio-838 oracle tracks the latest V5 (76). Our engine faithfully reproduces BOTH (V2 → 80.4, V5 → 75.6) — the +4.38 miss vs the DB oracle was a fixture-version mismatch, NOT an engine over-rate (a parallel over-credit sweep found no spec-correct from_site_notes lever; every channel is faithful). Refreshed the fixture to the V5 PDF (image-stripped, text layer preserved, 6.7MB→0.27MB, per scripts/build_pashub_accuracy_fixtures.py) and set the manifest to C76. 5 Paxton flips from the cohort's largest miss to a within-0.5 hit: DB-oracle gauge 86.9%→87.4% within-0.5, MAE 0.348→0.327. Pinned via test_paxton_fixture_is_v5_resurvey_sap_76 (asserts a literal 76 against the V5 fixture) — a canary, because hubspot_deal_data.pre_sap is still stale at C80 and a fixture-builder rerun would revert the manifest. Confirmed against pashub: the current survey is SAP 76 (Khalim). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| handler | ||
| tests | ||
| __init__.py | ||
| db_writer.py | ||
| elmhurst_extractor.py | ||
| extractor.py | ||
| local_runner.py | ||
| parser.py | ||
| pdf.py | ||