applylisted

# Apply — Single Job or Batch Queue Two modes, one shared apply loop: - **Single-job** (argument is a URL or pasted job page): fit review → user "yes" → apply one. - **Batch** (no argument): drain `/api/queue/pending` → score → ranked table approval → apply all. User approves once up front. No per-job confirmation after that. ## Setup Follow `../shared/setup.md` to load profile, resume, credentials. ```bash JOBPILOT_API=http://localhost:8000 ``` Read `data.autoApply` for config (defaults applied per field): | Setting | Default | Notes | | ----------------------- | ------------------ | ------------------------------------------------------------------------------------------------ | | `minMatchScore` | 70 | Batch-mode threshold (0–100). Ignored in single-job mode. | | `maxApplicationsPerCampaign` | `null` (unlimited) | Sent as `config.maxApplications` when set; omit for unlimited batch. Single-job mode forces `1`. | | `defaultStartDate` | `"2 weeks notice"` | Default start-date answer. | For ATS portals (Greenhouse, Lever, Workday, etc.) the apply step lands on a domain that isn't in `/api/job-boards`. Follow `../shared/auth.md` — credentials are resolved from the `Credential.scope === <domain>` row or the `scope ===