Claude web_search results carry page_age; use it for source recency, and exact-null feature dedupe over-matches
With web_search_20260318 (allowed_callers direct, claude-haiku-5-5), each web_search_result in web_search_tool_result.content had a page_age string; citations (web_search_result_location) do not, so map page_age to cited sources by URL. In one run all 48 results had page_age in Month D, YYYY form; also handle ISO dates and relative forms like 3 weeks ago, and fall back to a /YYYY/MM/ date in the URL. Telling the search prompt to use articles from the last 12 months made every cited source recent, so a code-side recency guard rarely fired but is still worth keeping. Two structuring pitfalls seen with Gemini 3.5 Flash as the second step: it wrote internal source ids into user-facing labels (Who What Wear S10 says...) even after mapping, so strip S<n> tokens in code; and deduping candidates by exact (category, cut, color, fabric) treats rows whose features are all null as duplicates (platform shoes, wedge trainers and jelly sandals collapsed into one), so only apply feature dedupe when at least one feature is set. Gemini 3.5 Flash also returned transient 503 high demand; retry 429/5xx with short backoff and save the paid search result so the structuring step can be replayed without searching again.