_valid_phone() rejects all-same-digit numbers (999-999-9999, 000-000-0000)
that call-tracking widgets emit before they are wired; _phone_from_text now
scans past an invalid first match instead of returning it. Selftest covers
placeholder rejection and visible-text-wins-over-tel: semantics.
- website surface: Jina Reader re-render when direct HTML lacks a visible
phone (bot-walled 403 or client-side rendered phone) — the NAP
cross-check no longer loses its third source
- phone regex: lookarounds reject phone-like substrings glued to other
digits (JS artifact numbers from raw HTML)
- renderer: jina_reader provenance key when fallback fires
- --selftest mode (offline check of phone extraction)
- VALIDATION.md: gate re-run timestamp (PASS unchanged)
- Add _looks_like_match() gate in scrape_google(): rejects search-page
titles and names sharing no >=4-char token with the query, so the scraper
no longer ingests a wrong entity (e.g. name='Hours', or 'RK Mechanical'
for an 'Aire Serv' search).
- Strip BMP PUA glyphs (U+E000-U+F8FF, e.g. the \ue0b0 map-pin) from GBP
address + phone. Old regex only covered the Supplementary PUA plane
(\U000E0000-\U000EFFFF) so the glyph leaked into the contract and broke
downstream phone normalization.
- Also: Apple Maps fallback path when GBP is rejected, and makedirs for the
optional 3rd-arg output dir.
Leonard
tonyjbala
tonyjbala