Fix generate package error handling in lead cards

[adilzubair]

Closes #26

Summary

Fix the Generate Package actions in the lead cards so failed backend generation requests no longer look like successful queued actions.

Previously, the UI triggered package generation and showed a temporary queued/generating state without checking whether the backend actually accepted the request. If the backend returned a non-2xx response, users could briefly see a success-looking state instead of a useful error.

This change adds response checking and surfaces backend error details inline in both generate entry points:

• lead cards
• pipeline lead cards

Type of Change

• Scraper/source adapter
• Ranking/scoring
• Vector/profile intelligence
• Customizer/document generation
• Frontend/UI
• Backend/API/storage
• Docs/OSS hygiene
• CI/release
• Experimental automation

Testing

Commands run:

• npm run typecheck
• npm test
• npm run build
• backend/.venv/Scripts/python.exe -m pytest backend/tests
• cd src-tauri && cargo check
• Other:

Privacy And Safety

• No API keys, cookies, bearer tokens, resumes, local databases, or generated private documents are included.
• User-facing behavior is clear about what is core vs experimental.
• Ranking/filtering changes include explanations or tests where relevant.

Notes For Reviewers

This is a focused alpha UX fix for a core supported workflow. It only changes the frontend behavior around package generation failure states and does not change backend APIs.

[vercel]

@adilzubair is attempting to deploy a commit to the Vasu-Devs' projects Team on Vercel.

A member of the Team first needs to authorize it.