Trade-specific scoring UX, pricing copy polish, scanner h1 clarity

[manazoid4]

Summary

• Trade-specific scoring UX: Lead score reason cards now show trade-specific job type keywords (EV charger/rewire for electrical, boiler/bathroom for plumbing, etc.) when the API returns no explicit match keywords. Added TRADE_TYPICAL_JOBS fallback map in FindJobsPage.tsx and wired tradeHint through parseTradeReasons.
• Scanner h1 clarity: Changed "FIND JOBS WORTH PRICING" → "FIND PUBLIC TENDERS NEAR YOU" — makes the product category clear in under 3 seconds; tradespeople won't mistake it for a domestic lead-gen board.
• PricingPage CTA fix: Pilot plan CTA changed from "START AFTER COVERAGE CHECK →" to "START £39/MO →" with a "No credit card required to scan first" note — removes friction and sets clear price expectation.
• PricingPage copy: Plan card body rewritten from corporate jargon ("firm-aware qualification", "delivery features activate only when...") to tradesperson-first language leading with buyer/deadline/BID/SKIP value.

Test plan

• npm run build passes clean
• npx tsc --noEmit passes clean
• Open FindJobsPage — scanner section h1 reads "FIND PUBLIC TENDERS NEAR YOU"
• Scan with electrical trade — lead cards show EV CHARGER / REWIRE / CONSUMER UNIT pills when API reasons are generic
• Open /pricing — Pilot plan CTA reads "START £39/MO →" with "No credit card required" note below
• Open /pricing — plan card body text no longer contains "firm-aware qualification" or "pilot access follows a coverage and fit check"

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
job-filter-v1	Ready	Preview	Aug 20, 2026 6:52am

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[supabase]

This pull request has been ignored for the connected project nfjwuwsuaapufmkppoeo because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[alwaysmeticulous]

✅ Meticulous spotted 0 visual differences across 169 screens tested: view results.

Meticulous evaluated ~4 hours of user flows against your PR.

_{Expected differences? Click here. Last updated for commit dd8119c [NightlyBuildAgent] Update next-env.d.ts (auto-generated by Next.js buil.... This comment will update as new commits are pushed.}