2 Commits (629554e6f6cbbca2f21224df7f3bd1bb9ccd222e)

Author	SHA1	Message	Date
Talha Ahmed	cec3be73fb	Title tier of relevance_score accepts token containment ... Live case: the job titled "Generative Engineer" sourced a pool titled "Generative AI Engineer" -- the exact phrase never occurs in that title, so every genuine match fell through to the scattered 35 tier and the whole pool compressed into the 40s. A current title containing every job-title token now earns the full 55. The headline tier stays phrase-only so keyword-stuffed headlines still cap at the 35 tier. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-25 19:46:34 +05:00
Talha Ahmed	e1bd8526f3	Talent tab: LinkedIn sourcing per job via Apify ... New backend/talent/ module (runs + profiles tables, RBAC talent.* seed, frontend-polled run lifecycle) and frontend Talent screen: job + location pickers, paid-search confirm, big loader, ranked profile cards with match ring, profile detail modal, show-10-then-more, next-page re-search. Sourcing quality: current-title facet + skills-only keyword query, experience-range facet, thin-result broadening ladder, Utopia Brands/Deals current employees excluded actor-side and server-side, graded 0-100 relevance score (title phrase over keyword stuffing). Also narrows the overbroad **_**_**.py gitignore rule to alembic versions; it was silently swallowing app/tests __init__.py files, the engine smoke script, and the new talent plugin tests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-20 22:27:18 +05:00