houses: Leefbaarometer liveability per listing (PDOK geocode + LBM 2024 grid/buurt), min-score filter and sort; store every regional listing (no price caps at scrape time)

docs/house-tracker.md

@@ -26,6 +26,22 @@ numbers, so its listings are never merged. Alerts: new non-copy listings matchin
 rule go to `HOUSE_NTFY_URL` (its own topic, max 5 per night plus one summary); the first run
 of a source only seeds.
 
+No caps at scrape time: every listing in the region is stored (Kamernet city pages, Vesteda
+with an open rent range, Pararius without a price band). The €2,000 / 2-bedroom / 50 m²
+limits are only the page's default filters (clear a field to drop it) and the alert rule.
+
+Liveability: every listing gets a Leefbaarometer 3.0 score (BZK, measurement 2024, published
+July 2026; `src/lib/house-tracker/liveability.ts`). The address is geocoded with PDOK
+Locatieserver (exact address, else 6-char postcode, else street centroid → marked approx.),
+then the 100 m grid cell and the buurt containing the point are read from the official WFS
+(`geo.leefbaarometer.nl/lbm3`, layers `clippedgridscore24` / `buurtscore24`). The cell score
+is used when there is one (and the location is not street-level), else the buurt. Stored on
+the row: `lbm_class` (1-9, zeer onvoldoende … uitstekend), `lbm_onv_class` (overlast &
+onveiligheid, 1-9 where 5 = Dutch average), buurt, level, precision, year, and all
+sub-scores in `lbm_detail`. Scored by the nightly scrape (new and changed addresses), the
+CLI and the page's add form; backfill or re-score with `scripts/house-liveability.ts
+[--force]`. For a new measurement, bump `LBM_YEAR` and run it with `--force`.
+
 Manual listings: `scripts/house-listing.ts` (CLI) or the form on the page. Against prod use
 `scripts/house-db.sh <command> …`, which runs the CLI as `house_cli` (SELECT/INSERT/UPDATE/
 DELETE on house.listings, SELECT/INSERT on house.price_history, nothing else) from