fix(kb): close all six Zeugnis discrepancies on the user's rulings

D1/D2 - Bosch title and promotion: CONFIRMED by the user. The promotion and its
timing are correct and came from a re-grading (Neueinstufung). The Zeugnis does
not contradict it - it names DEPARTMENTS ("Ingenieur" in Fertigungstechnologie
1/2/3) rather than job titles. Separately corrected a false provenance note that
claimed official_title was "the formal combined string on the Zeugnis"; it never
came from that document, it comes from the user and LinkedIn.

D3 - part-time from 2021-09: NOT recorded, by the user's decision. Noted for
completeness that tenure wording such as "over ten years" measures elapsed time
and is unaffected; it would only matter if a document claimed FTE years, and
none does.

D4 - French and Italian: the Swisscom Zwischenzeugnis says he uses both
professionally on a regular basis. The user reviewed the sentence and confirmed
it is an ERROR IN THE DOCUMENT. DE/EN only stands. Recorded in
identity.language_note so nobody rediscovers the line and acts on it, with the
practical warning that a reader of that Zeugnis may take it at face value.

D5 - the RUAG MSSQL rule-out: the DECISION stands (user does not want it
revisited), the REASONING is corrected. Two of its four premises were wrong:
MSSQL is not 0 (Fraunhofer SCEDAS ran on Microsoft SQL Server), and "his stack
is AWS cloud-native" was too narrow - the Swisscom Zeugnis documents component
ownership for ETL into the Teradata DWH. Talend and SAP S/4HANA remain genuinely
0, and the required line reads "Aufbau UND Betrieb" while he has documented
Betrieb only - so the skip is still defensible, it was just better than its
written justification. Both RUAG decision rows now carry the correction and a
standing rule for future DWH postings.

D6 - Vizrt end date: 2018-05 stands by the user's decision.

And the follow-through that matters: the data-warehouse, MSSQL and mentoring
evidence is now IN THE BUNDLES, not only in claims.json. BS-6 showed last week
that evidence which reaches no bundle cannot be selected - this is the same
failure mode, caught the same week. The DWH entry carries its scope limit
explicitly: documented Betrieb, not Aufbau.

Validator PASS, 37/37 tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qej5SBvhcbGXHwLqNWiskM

job_scout/state/decisions.json

@@ -1842,7 +1842,7 @@
     "company": "",
     "title": "",
     "decision": "skip",
-    "note": "JD read 2026-09-04. Repost of the pulled Data Lakehouse / Senior Data Platform Engineer req with the disqualifier moved into the title. Required: mehrjährige Erfahrung im Aufbau und Betrieb von ON PREMISE Data Warehouse Lösungen, plus MSSQL, Talend, SAP S/4HANA. claims.json has 0 for MSSQL, Talend and SAP; his stack is AWS cloud-native. Settles the 2026-08-31 downgrade.",
+    "note": "JD read 2026-09-04. Repost of the pulled Data Lakehouse / Senior Data Platform Engineer req with the disqualifier moved into the title. Required: mehrjährige Erfahrung im Aufbau und Betrieb von ON PREMISE Data Warehouse Lösungen, plus MSSQL, Talend, SAP S/4HANA. claims.json has 0 for MSSQL, Talend and SAP; his stack is AWS cloud-native. Settles the 2026-08-31 downgrade. *** REASONING CORRECTED 2026-09-11 - THE DECISION STANDS, TWO OF ITS PREMISES DID NOT. *** Reading the primary Arbeitszeugnisse showed: (1) 'MSSQL 0 canonical' was WRONG - Fraunhofer's SCEDAS ran on MICROSOFT SQL SERVER with C# and Entity Framework (Arbeitszeugnis 31.10.2019); (2) 'his stack is AWS cloud-native' was too narrow - the Swisscom Zwischenzeugnis (Okt 2025) documents KOMPONENTENVERANTWORTUNG for the ETL pipelines that load business-critical Fulfillment data into the TERADATA DATA WAREHOUSE (DWH), which is data-warehouse operation, and Teradata is typically on-premise. What genuinely remains 0 is TALEND and SAP S/4HANA, and the required line is 'Aufbau UND Betrieb' - he has documented Betrieb, not Aufbau. The skip is therefore still defensible, but it was better than its written justification. RULE FOR FUTURE DWH POSTINGS: he HAS documented data-warehouse experience (Teradata, as component owner) and MSSQL exposure. Do not repeat 'no DWH' or 'MSSQL 0'. Screen such roles on Aufbau-vs-Betrieb and on the named vendor stack instead.",
     "date": "2026-09-04"
   },
   "https://www.bis.org/vacancy/jr100472": {
@@ -1933,7 +1933,7 @@
     "company": "",
     "title": "",
     "decision": "skip",
-    "note": "STALE SHORTLIST from 2026-07-06, cleared 2026-09-04. The req was pulled from the board between the 08-31 and 09-04 scrapes and reposted as Senior Data Engineer (MSSQL) mit Data Lakehouse Perspektive. The 07-06 shortlist was a title-match prior; the JD is on-prem MSSQL/Talend/SAP S/4HANA, 0 canonical each. See the successor req's own decision row.",
+    "note": "STALE SHORTLIST from 2026-07-06, cleared 2026-09-04. The req was pulled from the board between the 08-31 and 09-04 scrapes and reposted as Senior Data Engineer (MSSQL) mit Data Lakehouse Perspektive. The 07-06 shortlist was a title-match prior; the JD is on-prem MSSQL/Talend/SAP S/4HANA, 0 canonical each. See the successor req's own decision row. *** REASONING CORRECTED 2026-09-11 - THE DECISION STANDS, TWO OF ITS PREMISES DID NOT. *** Reading the primary Arbeitszeugnisse showed: (1) 'MSSQL 0 canonical' was WRONG - Fraunhofer's SCEDAS ran on MICROSOFT SQL SERVER with C# and Entity Framework (Arbeitszeugnis 31.10.2019); (2) 'his stack is AWS cloud-native' was too narrow - the Swisscom Zwischenzeugnis (Okt 2025) documents KOMPONENTENVERANTWORTUNG for the ETL pipelines that load business-critical Fulfillment data into the TERADATA DATA WAREHOUSE (DWH), which is data-warehouse operation, and Teradata is typically on-premise. What genuinely remains 0 is TALEND and SAP S/4HANA, and the required line is 'Aufbau UND Betrieb' - he has documented Betrieb, not Aufbau. The skip is therefore still defensible, but it was better than its written justification. RULE FOR FUTURE DWH POSTINGS: he HAS documented data-warehouse experience (Teradata, as component owner) and MSSQL exposure. Do not repeat 'no DWH' or 'MSSQL 0'. Screen such roles on Aufbau-vs-Betrieb and on the named vendor stack instead.",
     "date": "2026-09-04"
   },
   "https://nvidia.wd5.myworkdayjobs.com/en-US/NVIDIAExternalCareerSite/job/Switzerland-Zurich/Senior-DevOps-Engineer_JR2024256": {

resume_builder/bundles/bundle_data_engineer.md

@@ -132,3 +132,22 @@ BS-6 was absent from every bundle although it has been canonical since 2026-08-2
 - **Use it when** the JD names Linux, Ansible, configuration management, IaC or platform operations — exactly the DevOps/SRE-flavoured reqs where this profile reads thin without it.
 - **Currency limit, always state it:** employer-side Linux/Ansible ended Dec 2022; `PP-3` carries the current half and is a **personal** self-hosted Debian server. Never present PP-3 as employer work or as physical-datacenter evidence.
 - **GitOps remains forbidden:** playbooks lived in Git but ran push-based from Jenkins/GitLab with no reconciliation agent. The substance is writable as “version-controlled infrastructure automation with Ansible from Git, executed through Jenkins/GitLab pipelines”.
+
+## Data-warehouse and mentoring evidence (added 2026-09-11 from the Arbeitszeugnisse)
+
+Both were documented all along and reached no bundle, so the selection paths could not see them.
+Same failure mode as BS-6 (Linux/Ansible), found the same week.
+
+- **Data warehouse (SW-2).** The Swisscom Zwischenzeugnis documents *Komponentenverantwortung* for
+  the ETL pipelines that load business-critical Fulfillment data from Oracle into the **Teradata
+  Data Warehouse (DWH)**. Use this whenever a JD names data warehousing — it was previously
+  screened as absent, which cost a correct answer on at least one posting.
+  **Scope limit:** this is documented **Betrieb** (operation) of a DWH, not **Aufbau**
+  (construction). A required line saying *"Aufbau und Betrieb von Data-Warehouse-Lösungen"* is only
+  half met — say which half.
+- **Microsoft SQL Server (FC-1).** Fraunhofer's SCEDAS ran on MSSQL with C# and Entity Framework.
+  Historical and single-project; do not present it as data-platform depth.
+- **Mentoring (BS-7).** *"Fachliche Betreuung von Studierenden, auch im Rahmen von
+  Abschlussarbeiten"* — documented technical supervision, including thesis supervision. Use it when
+  a JD asks about developing other engineers (SBB asked explicitly and the answer had to fall back
+  on team roles). **Technical supervision, NOT people management.**

resume_builder/bundles/bundle_data_platform.md

@@ -141,3 +141,22 @@ Kubernetes, Docker, AWS (S3 · Glue · Athena · Redshift · CloudFormation), Ka
 - Claiming SRE/pure DevOps title (you were a data engineer with platform ownership)
 - Overstating Terraform/Helm experience (not confirmed — do not claim)
 - Mentioning SCEDAS, maritime research, BDD, or RPA
+
+## Data-warehouse and mentoring evidence (added 2026-09-11 from the Arbeitszeugnisse)
+
+Both were documented all along and reached no bundle, so the selection paths could not see them.
+Same failure mode as BS-6 (Linux/Ansible), found the same week.
+
+- **Data warehouse (SW-2).** The Swisscom Zwischenzeugnis documents *Komponentenverantwortung* for
+  the ETL pipelines that load business-critical Fulfillment data from Oracle into the **Teradata
+  Data Warehouse (DWH)**. Use this whenever a JD names data warehousing — it was previously
+  screened as absent, which cost a correct answer on at least one posting.
+  **Scope limit:** this is documented **Betrieb** (operation) of a DWH, not **Aufbau**
+  (construction). A required line saying *"Aufbau und Betrieb von Data-Warehouse-Lösungen"* is only
+  half met — say which half.
+- **Microsoft SQL Server (FC-1).** Fraunhofer's SCEDAS ran on MSSQL with C# and Entity Framework.
+  Historical and single-project; do not present it as data-platform depth.
+- **Mentoring (BS-7).** *"Fachliche Betreuung von Studierenden, auch im Rahmen von
+  Abschlussarbeiten"* — documented technical supervision, including thesis supervision. Use it when
+  a JD asks about developing other engineers (SBB asked explicitly and the answer had to fall back
+  on team roles). **Technical supervision, NOT people management.**

resume_builder/canonical/claims.json

@@ -36,7 +36,8 @@
       "marital status",
       "gender",
       "children"
-    ]
+    ],
+    "language_note": "GERMAN (native) and ENGLISH (fluent) ONLY. The Swisscom Zwischenzeugnis of October 2025 states he also uses FRENCH and ITALIAN professionally on a regular basis - the user reviewed that line on 2026-09-11 and confirmed it is an ERROR IN THE DOCUMENT. Do not add French or Italian to any CV, cover letter or application form on the strength of that sentence, and do not re-open the question the next time someone reads the Zeugnis. Practical warning: if that Zeugnis is submitted alongside an application, a reader may take the sentence at face value and ask about French."
   },
   "education": [
     {
@@ -109,7 +110,8 @@
           "end": "2022-12"
         }
       ],
-      "title_history_source": "LinkedIn-confirmed, recorded in experience_bosch.md; user-confirmed 2026-08-27 while reviewing the RUAG C5I resume. Added because claims.json previously carried only the combined official_title with no promotion date, which made a Swisscom-style 'Beforderung <date>' line unwritable from the canonical file alone."
+      "title_history_source": "LinkedIn-confirmed, recorded in experience_bosch.md; user-confirmed 2026-08-27 while reviewing the RUAG C5I resume. Added because claims.json previously carried only the combined official_title with no promotion date, which made a Swisscom-style 'Beforderung <date>' line unwritable from the canonical file alone. RE-CONFIRMED BY THE USER 2026-09-11 after the Arbeitszeugnis was read: the promotion and its timing are correct, and happened through a RE-GRADING (Neueinstufung). The Zeugnis does not contradict this - it simply names DEPARTMENTS ('Ingenieur' in Fertigungstechnologie 1/2/3) rather than job titles, and never uses the words 'Senior' or 'Data Analysis'. Do NOT expect this Zeugnis to corroborate the title string; do not 'correct' the title against it.",
+      "official_title_provenance": "NOT from the Arbeitszeugnis - that document names departments only. The title string comes from the user and from LinkedIn. Corrected 2026-09-11; an earlier note wrongly claimed the Zeugnis as its source."
     },
     {
       "id": "FRAUNHOFER",
@@ -963,50 +965,15 @@
     }
   ],
   "open_discrepancies_2026_09_11": {
-    "note": "Found by reading the primary Arbeitszeugnisse on 2026-09-11. NONE of these are resolved here: each needs the user's decision or a second document. Do not quietly pick a side when writing a document - ask.",
-    "items": [
-      {
-        "id": "D1-bosch-title",
-        "severity": "high",
-        "kb_says": "employment.BOSCH official_title 'Engineer / Senior Engineer, Data Analysis', with a note claiming this is 'the formal combined string on the Zeugnis'.",
-        "document_says": "The Bosch Arbeitszeugnis says 'Ingenieur' in the department 'Fertigungstechnologie', then 'Fertigungstechnologie 2' from 2021-06-01, then 'Fertigungstechnologie 3' from 2022-03-01. The words 'Senior' and 'Data Analysis' do NOT appear anywhere in it.",
-        "why_it_matters": "The KB note asserts a provenance the document does not support. The title may still be correct from a contract, org chart or LinkedIn - but not from this Zeugnis."
-      },
-      {
-        "id": "D2-bosch-promotion-date",
-        "severity": "medium",
-        "kb_says": "title_history: Data Engineer 2020-02 to 2021-01, Senior Data Engineer 2021-01 to 2022-12 (LinkedIn-confirmed, user-confirmed 2026-08-27).",
-        "document_says": "Department changes on 2021-06-01 and 2022-03-01, with no promotion named.",
-        "why_it_matters": "A 'Befoerderung <date>' line on a CV should match a document."
-      },
-      {
-        "id": "D3-bosch-part-time",
-        "severity": "high",
-        "kb_says": "nothing - part-time work is not recorded anywhere.",
-        "document_says": "'Seit dem 01. September 2021 arbeitete Herr Thiessen in Teilzeit.'",
-        "why_it_matters": "Bosch was PART-TIME for its final ~16 months. Any tenure or full-time-equivalent statement, including the 'over ten years' summary wording, was written without this. It does not necessarily change that phrasing, but it must be a conscious decision rather than an oversight."
-      },
-      {
-        "id": "D4-swisscom-languages",
-        "severity": "high",
-        "kb_says": "memory user_international_mobility: 'DE/EN only (no French/Mandarin)'.",
-        "document_says": "'Besonders hervorzuheben sind zudem seine sehr guten Sprachkenntnisse in Englisch, FRANZOESISCH und ITALIENISCH, welche er beruflich regelmaessig anwendet.'",
-        "why_it_matters": "This shaped targeting - French-speaking roles were screened out on the memory entry. Either the Zeugnis is generous or the memory is wrong. ASK before relying on either."
-      },
-      {
-        "id": "D5-swisscom-dwh",
-        "severity": "high",
-        "kb_says": "The RUAG 'Senior Data Engineer (MSSQL)' rule-out of 2026-09-04 treated on-premise data-warehouse work as absent.",
-        "document_says": "Swisscom: component ownership for ETL pipelines moving business-critical data into the TERADATA DATA WAREHOUSE (DWH). Fraunhofer: Microsoft SQL Server.",
-        "why_it_matters": "Two of that rule-out's premises are shakier than recorded. Talend and SAP S/4HANA remain genuinely 0 and may still carry it, but the DWH and MSSQL reasoning must not be repeated as written."
-      },
-      {
-        "id": "D6-vizrt-end-date",
-        "severity": "low",
-        "kb_says": "employment.VIZRT end 2018-05.",
-        "document_says": "'employed as a Test Automation Engineer in Vizrt from 01.07.2017 - 01.07.2018', in a letter dated 09.05.2018.",
-        "why_it_matters": "The letter may state a planned end date. Two months of tenure; low stakes, but a CV date should match a document."
-      }
-    ]
+    "note": "All six discrepancies found on 2026-09-11 are resolved; see resolved_2026_09_11. Kept as a record of what reading the primary documents actually turned up.",
+    "items": [],
+    "resolved_2026_09_11": {
+      "D1-bosch-title": "CLOSED. User re-confirmed the promotion and timing; the Zeugnis names departments, not titles. official_title_provenance corrected - it never came from that document.",
+      "D2-bosch-promotion-date": "CLOSED with D1. The 2021-01 re-grading stands.",
+      "D3-bosch-part-time": "CLOSED by user decision: part-time from 2021-09 is NOT recorded and does not belong in any document. Note for completeness: tenure wording such as 'over ten years' measures ELAPSED time and is unaffected. It would only matter if a document ever claimed full-time-equivalent years, which none does.",
+      "D4-swisscom-languages": "CLOSED. The user reviewed the sentence and confirmed it is an error in the Zeugnis. DE/EN only stands. See identity.language_note.",
+      "D6-vizrt-end-date": "CLOSED by user decision: end 2018-05 stands. The letter, written 2018-05-09, evidently stated a planned end date.",
+      "D5-swisscom-dwh": "CLOSED. User ruling: the RUAG role itself is not revisited (and a second cold application to RUAG is blocked anyway while 18027 is pending), but the reasoning IS corrected. Both RUAG decision-log rows now carry the correction. Standing rule recorded there: he has documented data-warehouse experience (Teradata, component owner) and MSSQL exposure - screen DWH roles on Aufbau-vs-Betrieb and the named vendor stack, never on 'no DWH' or 'MSSQL 0'."
+    }
   }
 }