docs(specs): 6-builder batch outcome — 4 capture rich per-home specs, 3 deferred (verified thin/bot-walled)

d6741529ff78516a4329f0b4a001a35f4018886b · 2026-08-03 07:09:55 -0700 · Steve Abrams

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Files touched

M collectors/SPECS-AUDIT.md

Diff

commit d6741529ff78516a4329f0b4a001a35f4018886b
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Mon Aug 3 07:09:55 2026 -0700

    docs(specs): 6-builder batch outcome — 4 capture rich per-home specs, 3 deferred (verified thin/bot-walled)
    
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 collectors/SPECS-AUDIT.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/collectors/SPECS-AUDIT.md b/collectors/SPECS-AUDIT.md
index 9f4ad0c8..ed44ae99 100644
--- a/collectors/SPECS-AUDIT.md
+++ b/collectors/SPECS-AUDIT.md
@@ -89,6 +89,22 @@ map (nulls + false-flags dropped); publisher persists it; detail page shows an
 the home Items — they live elsewhere in DRH's `var model` tree (plan-level?). A
 second extraction pass is needed to reach them. Item-level specs work today.
 
+### Capture-ready extension — 6-builder batch outcome — 2026-08-03
+Extended the proving slice to the capture-ready builders. Verified each against a
+REAL home object (the DRH lesson held every time — audit-flagged fields were often
+community-level, not on the home). All committed, all typecheck clean.
+
+**✅ Rich per-home specs captured (4):**
+- **dr-horton** — planCode, multiGen, originalPrice (Item-level)
+- **pulte** — priceDiscount ($ off list), mortgagePayment, hasBasement, isActiveAdult, discountExpiration, virtualTour, planDescription
+- **meritage** — monthlyPayment (respects hide_monthly_payment), previous_mhdc_price (was-price), moveInTimeframe, floorplanName, incentiveAvailable, virtualTour, mlsNumber
+- **perry** — discountedPrice (drop signal), promotion, description, elevation, market
+
+**⏸️ Deferred — no rich per-home extras in what we crawl (verified, not skipped blindly):**
+- **landsea** — Cloudflare bot-walled/DEGRADED; stored snapshots don't yield a clean Algolia home to verify against. Won't add unverified field names.
+- **fischer** — CombinedHome/DetailFacts carry only core + formatted duplicates; ld+json description consumed for community name only. Extra capture needs parseDetail surgery for 45 homes (low ROI).
+- **discovery** — per-home data is scraped from HTML qmi-cards (core only). NOTE: its COMMUNITY feed is very rich (tax_rate, active_adult, amenities, schools, promos, brochure PDFs) — a future COMMUNITY-enrichment opportunity, not home-specs.
+
 ### GATED — capture requires prod changes
 Beyond read-only auditing, actually CAPTURING specs needs: (a) `specs Json?`
 schema migration on the live Kamatera DB, (b) per-builder extractor edits, and

← 674ccf86 feat(specs): perry specs capture — discounted price, promoti · back to Homesonspec · docs(toll): wave-2 recon — ~298 per-community fetches not 11 f98e35a7 →