feat(jobs): suppress duplicate postings after skip or apply

Dedup by employer+title and description at import; cascade skip on dismiss; hide repeats in the job list. Document product scope and duplicate detection in docs.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs-site/docs/features/blocked-countries.md

@@ -15,6 +15,8 @@ Country tokens are normalized to canonical keys (for example `India` → `india`
 
 Global and remote boards often return roles tagged to countries you do not want (for example India-remote QA listings while you target Canada). This filter applies at import time so those rows never enter your **Discovered** queue.
 
+When **Search cities** (or pipeline geography) is a single country such as **Canada**, JobOps also enforces an **allow-list**: only jobs that clearly hire in that country are kept. Vague `Remote` / `Worldwide` rows with no Canada signal are dropped, as are rows that mention any other country.
+
 ## How to use it
 
 1. Open **Settings** and expand **Scoring Settings**.
@@ -26,7 +28,8 @@ Global and remote boards often return roles tagged to countries you do not want
 ### Tips
 
 - Use country names as they appear on listings: `India`, `Poland`, `United Kingdom`, or aliases `UK`, `USA`.
-- Listings with **no recognizable country** in the location field (for example `Remote` only) are **kept**, not blocked.
+- With **no** country-level search geography, listings whose location is only `Remote` / `Worldwide` with no blocked country in the text are **kept**.
+- With search geography set to a country (for example `Canada`), vague remote rows with no signal for that country are **dropped** even if they are not on the blocked list.
 - The list is capped in Settings validation (max 50 entries, each up to 100 characters).
 - Pair with **Search cities** / **country** settings to narrow what extractors query; blocked countries filter what still comes back from broad boards.
 
@@ -50,6 +53,7 @@ Global and remote boards often return roles tagged to countries you do not want
 
 ## Related pages
 
+- [Duplicate job detection](./duplicate-jobs)
 - [Company skip list](./company-skip-list)
 - [Settings](/docs/features/settings)
 - [Pipeline Run](/docs/features/pipeline-run)

docs-site/docs/features/company-skip-list.md

@@ -48,6 +48,7 @@ You may want to avoid certain agencies, staffing brands, or employers without ha
 
 ## Related pages
 
+- [Duplicate job detection](./duplicate-jobs)
 - [Blocked countries](./blocked-countries)
 - [Settings](/docs/features/settings)
 - [Pipeline Run](/docs/features/pipeline-run)

docs-site/docs/features/duplicate-jobs.md

@@ -0,0 +1,79 @@
+---
+id: duplicate-jobs
+title: Duplicate job detection
+description: How JobOps deduplicates cross-source postings and hides repeats after you skip or apply.
+sidebar_position: 8
+---
+
+## What it is
+
+JobOps treats the same role reposted on different boards as **one opportunity**, and remembers when you have already **skipped** or **applied** so you do not see it again.
+
+Duplicate detection uses normalized keys:
+
+- **Employer + title** — strips punctuation, `(Remote)`, trailing city lines, and legal suffixes (`Inc.`, `Ltd.`) so `Acme Inc.` / `SDET (Remote)` matches `Acme` / `SDET`.
+- **Employer + description** — when the job description is long enough, the same posting copy under the same company matches even if the title wording differs slightly.
+
+This runs at **import time** (pipeline) and in the **Jobs list** (UI).
+
+## Why it exists
+
+Job boards repost the same role on LinkedIn, Indeed, QAJobsBoard, and aggregators. Skipping or applying once should mean you do not wade through the same listing again on the next run.
+
+## How to use it
+
+You do not configure duplicate detection separately. It is always on for your profile.
+
+### When you skip a job
+
+1. Skip from the job detail panel or press **`s`** on the Jobs page.
+2. JobOps marks that row `skipped`.
+3. Any other **Discovered** or **Ready** jobs with the same employer+title (or same employer+description) are **auto-skipped**.
+4. Future pipeline imports that match those keys are **not imported**.
+
+### When you mark applied
+
+1. Mark the job applied from the UI.
+2. Duplicate open rows are **auto-skipped** (not marked applied) so your Applied tab stays clean.
+3. Future imports of the same role are suppressed the same way as for skips.
+
+### Cross-source import
+
+During a pipeline run, if a new posting matches an existing row by URL, source id, or content fingerprint, JobOps **does not create a second row** — the import is counted as skipped in run stats.
+
+### Jobs list
+
+Open jobs that match a prior skip or apply are **hidden** from Discovered, Ready, and All tabs so the queue stays fresh. Skipped and applied rows themselves remain visible in their statuses.
+
+## Defaults and constraints
+
+- Description matching requires at least **80 characters** of normalized text; short or empty descriptions fall back to employer+title only.
+- Matching is **per profile** (`ownerProfileId`); different login profiles do not share dedup state.
+- Dedup does **not** delete existing rows retroactively when you change skip list or country filters — run discovery again or skip manually for old data.
+- Very different titles at the same company (for example `SDET` vs `Product Designer`) are **not** collapsed.
+
+## Common problems
+
+### I still see the same job from another source
+
+- Titles or employer names may differ enough that normalization does not match (for example a staffing agency name vs the hiring company).
+- Add the employer to the [Company skip list](./company-skip-list) if it is always noise.
+- Skip one row — siblings with matching keys should auto-skip and future imports should stop.
+
+### A different role at the same company disappeared
+
+- Employer+title dedup only merges **the same normalized title**. Different roles at one company should remain separate.
+- If two titles normalize to the same string, check for overly generic titles on the board.
+
+### Skipped jobs reappear after a pipeline run
+
+- Confirm the skip saved (status `skipped` in the UI).
+- If the repost uses a new employer spelling and a new title **and** a short description, it may not match — block the employer or country instead.
+
+## Related pages
+
+- [Orchestrator](/docs/features/orchestrator)
+- [Pipeline Run](/docs/features/pipeline-run)
+- [Company skip list](./company-skip-list)
+- [Blocked countries](./blocked-countries)
+- [Keyboard Shortcuts](/docs/features/keyboard-shortcuts)

docs-site/docs/features/orchestrator.md

@@ -27,6 +27,8 @@ Job states:
 - `skipped`: explicitly excluded from active queue
 - `expired`: deadline passed
 
+When you **skip** or **mark applied**, JobOps also skips matching open duplicates (same company + title or description) and blocks re-import on future runs. See [Duplicate job detection](/docs/features/duplicate-jobs).
+
 ## Why it exists
 
 Orchestrator centralizes the transition from discovered opportunities to application-ready artifacts.
@@ -132,8 +134,15 @@ curl -X POST "http://localhost:3001/api/jobs/<jobId>/generate-pdf"
 
 - Patch `status` back to `discovered` to return the job to the active queue.
 
+### Duplicate postings
+
+- Skipping one listing auto-skips other **Discovered** / **Ready** rows that match the same normalized employer+title (or employer+description when available).
+- The Jobs list hides open rows that match a job you already skipped or applied to.
+- Details: [Duplicate job detection](/docs/features/duplicate-jobs).
+
 ## Related pages
 
+- [Duplicate job detection](/docs/features/duplicate-jobs)
 - [Pipeline Run](/docs/next/features/pipeline-run)
 - [Ghostwriter](/docs/next/features/ghostwriter)
 - [Reactive Resume](/docs/next/features/reactive-resume)

docs-site/docs/features/pipeline-run.md

@@ -102,13 +102,15 @@ When new listings are imported, JobOps does not create a second database row if
 
 - a **canonical job URL** (normalizes `http`/`https`, `www`, trailing slashes, common tracking query params, and sorts remaining query keys)
 - the pair **`source` + `source_job_id`** when the extractor provides an external id
+- a **content fingerprint** (normalized **employer + title**) so the same role from another board is not imported twice
+- **skip/apply memory** — imports that match a job you already skipped or applied are not added
 
-Existing jobs keep their stored URL; new imports use the canonical form so the same role is not added again under a slightly different link.
+See [Duplicate job detection](./duplicate-jobs) for skip cascades and description matching.
 
-To drop listings before import, use **Settings → Scoring Settings**:
+To drop listings before import, use **Settings → Scoring Settings** and pipeline geography:
 
 - [Company skip list](./company-skip-list) — blocked **employer** keywords
-- [Blocked countries](./blocked-countries) — drop jobs whose **location** mentions a country you list (for example India)
+- [Blocked countries](./blocked-countries) — block specific countries; when search geography is a country (for example Canada), enforce that country only
 
 ## Common problems