fix: clarify the Bosch 24/7 constraint; tidy build artefacts

BS-1 operating constraint - the F07 open item, resolved by the user
The user clarified what the 24/7 constraint actually is: a defect in the
software could, worst case, halt production - an outcome that must never occur.

That is a FAILURE-CONSEQUENCE constraint, and the submitted NVIDIA cover letter
states something different: "a production line that could not be stopped for a
deployment" describes a scheduling window. The distinction matters in both
directions - the letter is inaccurate, and the truth is the stronger claim.

- BS-1 scope now records the real constraint and how to write it.
- Both variants of the letter's phrasing are added to BS-1 `forbidden`, so the
  scanner catches them. Verified: it now flags the submitted letter.
- BS-1 evidence filled from a real source (this clarification) rather than left
  unrecorded, including ownership - integration and operation, not model work.
- The submitted letter is NOT rewritten (F17). experience_bosch.md records the
  resolution and the wording to use instead.

Scanner false positive fixed: the employer-date check now runs on CVs only. A
cover letter naming an employer in prose is not claiming a date.

Cleanup, authorised by the user
- 136 LaTeX build artefacts removed (already gitignored, regenerable).
- 7 superseded intermediate QA renders removed, 6 of them in NATO_AI_ENGINEER
  which carried nine PDFs for two documents.
- Nothing evidential touched: 36 submitted PDFs, 41 e2e deliverables, 44 sources,
  54 session/critique files and 20 JD files are intact. The Kraken PDF was
  checked before deleting and turned out to be the saved job description, not a
  render.
- output/ 16M -> 13M.

37/37 tests pass.

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

resume_builder/experience/experience_bosch.md

@@ -36,14 +36,18 @@ This domain expertise is rare in data engineering candidates and is a strong dif
 **User's role:** Primary developer / strategy owner ("Erarbeitung und Durchführung" = designed AND executed)
 **Status:** Deployed to production
 
-> **OPEN ITEM — confirm before reusing (review F07, 2026-09-11).** The NVIDIA and RUAG cover
-> letters state that the production line could not be stopped for a deployment. That is a
-> *stronger* claim than the canonical record, which establishes a continuously operating 24/7 fab
-> but not a no-stop deployment constraint. **It is not declared false** — it is plausible and may
-> well be accurate. Both documents are already submitted and are NOT rewritten (F17: archives are
-> preserved). **Before any new package repeats this framing, ask the user to confirm it and record
-> the answer in `claims.json`.** Until then write the constraint as "integrated into a continuously
-> operating production environment".
+> **RESOLVED 2026-09-11 by the user** (was an open item from review F07). The real constraint is
+> a FAILURE CONSEQUENCE, not a deployment window: *"Bei einem Fehler (also Defekt in der Software)
+> kann es zu einem Produktionsstopp im worst-case kommen, was natürlich nie passieren darf."*
+>
+> The submitted NVIDIA cover letter says *"a production line that could not be stopped for a
+> deployment"* — that is a **different and inaccurate** claim. It describes a scheduling
+> constraint; the truth is about the blast radius of a bug. **That exact phrasing is now
+> `forbidden` on BS-1** and must not be reused. The letter itself is not rewritten (F17).
+>
+> **Write it as:** "integrated containerized ML inference into a continuously operating
+> semiconductor fab, where a software defect could have halted production" — which is a stronger
+> statement than the one that was sent, and true.
 
 **Context:** 300mm semiconductor fab runs continuously. Manual image classification for wafer defect detection created a bottleneck for line engineers in the Defect Management domain. Dennis designed and implemented the strategy to containerize and orchestrate ML inference into the live production pipeline, automating image-based defect classification and substantially reducing manual inspection work. **Scope limit (canonical BS-1):** the reduction is source-backed but its size is unverified — do not claim elimination, “no manual intervention” or unattended operation, and never claim model development.