feat(job_scout): score the forward-deployed/field/resident lane

Adds positive keywords (forward deployed, field engineer, resident
architect/engineer, customer engineer) and title-filter entries so
vendor deploy-to-customer roles surface — the lane matched to
user_international_mobility (intl scope from Bern, travel-OK, no
relocation). Bare "resident" stays title-filter-only to avoid
re-opening the pre-sales-SA overscoring trap.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

job_scout/scout.py

@@ -85,6 +85,12 @@ POSITIVE_KEYWORDS = {
     "brokerage": 2, "commodity": 1, "execution": 1,
     # "solutions architect" (plural) already scored above; add singular + adjacent stack
     "solution architect": 2, "c#": 1, ".net": 1,
+    # Forward-deployed / field / resident-architect lane — vendor "deploy-to-customer" roles
+    # where Dennis's multi-country ramp is the differentiator (see user_international_mobility).
+    # Travel-from-Bern fits his mobility appetite; no relocation required.
+    "forward deployed": 3, "forward-deployed": 3, "field engineer": 3,
+    "resident architect": 3, "resident engineer": 3, "resident solutions architect": 3,
+    "customer engineer": 2,
     "senior": 1, "staff": 1, "lead": 1, "principal": 1,
 }
 
@@ -112,6 +118,10 @@ ENG_TITLE_FILTER = [
     "site reliability", "sre", "backend engineer", "back-end engineer",
     "devops engineer", "cloud engineer", "software engineer", "infrastructure engineer",
     "kafka", "streaming", "big data", "quantitative developer", "quant developer",
+    # Forward-deployed / field / resident lane (vendor boards) — see user_international_mobility.
+    # "resident" alone catches Resident Solutions Architect/Engineer without opening the gate to
+    # all pre-sales SAs (the overscoring trap); "customer engineer" is Google's field-eng term.
+    "forward deployed", "forward-deployed", "field engineer", "resident", "customer engineer",
 ]
 
 # id, display, adapter, adapter_args