scan-inbox

# Scan Inbox - Review Pending Email Classify recent email and link each thread to an existing `Application` when there's a confident match. This skill does **not** write `ApplicationEvent` rows or mutate `Application.status` directly - the user approves from `/inbox`. One server-side exception: a `rejected` classification sent with `reviewStatus: "auto"` is applied on arrival (see Phase 4 rules). ## Setup Follow `../_shared/setup.md`. ## Phase 1: Confirm Mailbox Connected ```bash curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/email/account" ``` If `.connected === false`, stop: > No email account is connected. Open `/profile` → **Email** and connect a Gmail account, then re-run `scan-inbox`. ## Phase 2: Pick the Queue **One message** - an id was passed (a re-scan from the inbox table). Fetch just it and classify it again even if it's already classified or reviewed: ```bash curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/email/messages/<id>" ``` **All pending** - no argument. Sync, then pull the unscanned queue: ```bash curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" -X POST "$JOBPILOT_API/api/email/sync" curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/email/messages?reviewStatus=pending&classification=null" ``` Both list routes answer `{items, pagination}`; read `.items`. If it is empty: **"Inbox is already reviewed. Nothing new to classify."** and exit. The rest of the ...