Read every older project's site again, once, and re-judge its leads

[kev1n]

What

• profile_reseed job, queued once per project at boot (2 min apart) for projects made before 2026-09-20. It reads the site again with the multi-page reader. A profile nobody touched (profileVersion == 1) is replaced whole; an edited one keeps every fact and only has empty exclusions / not-buyers filled. A changed profile queues a rescore; dropped platform searches queue a new discovery.
• Rescore now also re-judges verdicts made under an older profile version, and stores the version it judged under.
• Limits prompt asks for each kind of limit by name (what the buyer must already have, country/region/law, language, currency, price floor) and says what is not a limit (plan caps, needing an account).
• Page picker skips blog/docs/legal paths. flat() no longer lets a link cut open by the 12k homepage limit swallow the text after it (live bug from Judge leads against who can use the product; read each page for who cannot #80: valid sources were dropped on long homepages).

Measured (1,463 labelled prod posts, 79 projects)

	shown	real	wrong	real leads shown
live (#80)	422	53%	18%	225
this PR	429	51%	18%	219

Same within run-to-run noise (~14 flips). The gain is truthfulness: Opus fact-check of every limit against the site found 1 false / 10 trivial of 73 new exclusions, against 7 false / 61 trivial of 141 before.

Cost: about $0.004 per project to re-read plus about $0.01 to rescore, under $2 for all of prod, spread over about 4 hours.

Tests

New tests/profileReseed.test.ts; site-reading and prompt tests extended. tests/jobs.test.ts "seeds a scan" times out locally against the shared dev DB (passes in 7s with a longer timeout), as before.

🤖 Generated with Claude Code