feat(app): Kongsberg Seatex DevOps & Test Infra submitted; KB gaps closed; scout triage 2026-10-08

Application
- Kongsberg Discovery / Seatex, Lead Engineer DevOps and Test Infrastructure
  (Trondheim): resume, cover letter (+ paste text), verbatim JD, session and
  critique. Submitted 2026-10-08 via EasyCruit as a deliberate cold application
  on a user override of the embedded-SW hard gate (Evidence Fit 69, Document
  Quality 84). Recorded in applications.json and decisions.json.
- Google Senior SWE Full Stack Commerce: session and verbatim JD from
  2026-10-03 (no-go on the frontend gap, held, not submitted).

Knowledge base
- claims.json: ED-1 (embedded/robotics coursework, none since studies),
  SW-9 (current unit testing, pytest), new skills (pytest, unit testing,
  embedded systems (coursework), VHDL, robotics (coursework)), and Jenkins and
  GitLab CI/CD registered from existing GN-1/FC-1/BS-6/SW-3 scopes.
- Earlier uncommitted KB work: 2026-09-18 Python frameworks / enterprise SaaS
  clarification, 2026-10-03 data-product design / no-frontend clarification,
  2026-10-06 working-model rule (3 homeoffice days baseline) in config.md and
  application_strategy.md, plus related experience/bundle/taxonomy updates.
- CLAUDE.md corrections log: 2026-10-08 entry for the three canonical gaps.

Scout
- 2026-10-08 run triaged by JD read: NVIDIA DGX Cloud Senior Production
  Engineer, Google SRE III Prod AI / Senior SRE / Staff Shopping Graph and
  Amazon RIVR DevOps logged as maybe; GenAI FDE family, Kraken AI Platform,
  PostFinance DevOps and five Kdo Cy reqs logged as skip with reasons.

Housekeeping
- .gitignore: ignore .cache/ and raw HTML page dumps under output/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

knowledge_base/extractions/2026-10-08_embedded_coursework_testing_clarification.md

@@ -0,0 +1,21 @@
+# Embedded coursework and current unit testing — user clarification
+
+Source: direct user messages, 2026-10-08, during the Kongsberg Seatex *Lead Engineer, DevOps and Test Infrastructure* fit check.
+
+Verbatim:
+
+> no embedded work since my studies. But nevertheless, lets try
+
+Answering *"What embedded work did you do during your studies? Course or project, language, hardware?"* and *"Do you write tests today? ... Which frameworks, such as pytest?"*:
+
+> 1. Embedded Systems - Using C / C++ and VHDL (with an ARM platform). We also had Robotics. 2. Unit Tests, yes - pytest is known.
+
+Established facts:
+
+- During his studies at Universität der Bundeswehr München he took **Embedded Systems**, working in **C/C++ and VHDL** with an **ARM platform**, and had **Robotics** as a subject.
+- He has done **no embedded work since his studies** — there is no professional embedded experience.
+- He **writes unit tests** today (the question asked about current practice at Swisscom), and he knows **pytest**.
+
+Not established: which degree (B.Eng. or M.Eng.) the courses belonged to; whether they were lectures, labs or a project; the specific board, FPGA or toolchain; any grade or outcome; whether pytest is the framework used at Swisscom (he named it as known, in answer to "which frameworks"); test scope, coverage or CI integration of the Swisscom unit tests.
+
+Canonical destination: claims ED-1 and SW-9, skills `embedded systems (coursework)`, `VHDL`, `robotics (coursework)`, `pytest`, `unit testing` in `resume_builder/canonical/claims.json`.