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": {