Import Resume

Read an uploaded resume PDF, suggest profile fields, and store the file privately.

Suggested fields are NOT written to the profile — only the user's Save does that. The PDF itself IS stored for the owner (Apply / self-use), behind GET /api/profile/resume. Public profiles and MCP never see it.

The refusals are ordered cheapest first, and each one is a different status because each one is a different thing for the user to do:

• 413 — bigger than the cap. Nothing is parsed or stored.
• 422 — not a PDF, encrypted, damaged, or a scan with no text layer. The message comes from resume_pdf and names the fix.
• 503 — this deployment has no inference provider configured, or every configured provider failed to answer. Not the user's fault and not a permanent condition, so not a 4xx. The private PDF is still stored when the file was readable.
• 429 — monthly inference budget exhausted, theirs or the platform's. Same: the private PDF is kept.
• 422 — read fine, and the model found nothing usable in it. PDF still kept.