diff --git a/backend/config.py b/backend/config.py
index 94357e0..4921fb9 100644
--- a/backend/config.py
+++ b/backend/config.py
@@ -150,7 +150,7 @@ EVIDENCE_CTX_LINES = 15          # context lines around a cited source position
 # Registry mit Suchraum: backend/train_params.py). QA-/Detektor-Konstanten bleiben bewusst in
 # qa.py/guide_qa.py — die Messlatte darf nie Teil des Suchraums sein. ─────────────────────────
 SUBBLOCK_MAX = 40          # chunk cap
-RESEARCH_BATCH = 20        # crawl pages per batch
+RESEARCH_BATCH = 1         # eine Seite pro Reader — er kann nichts übersehen (Vollständigkeit)
 RESEARCH_READERS = 2       # reader agents per batch/section (consensus ≥2)
 RESEARCH_THEMA_AGENTS = 5  # web mode (source "thema")
 RESEARCH_SECTION_CHARS = 12000  # uni/projekt section size (lost-in-the-middle guard)
diff --git a/backend/qa.py b/backend/qa.py
index 2d05010..fdf9ca4 100644
--- a/backend/qa.py
+++ b/backend/qa.py
@@ -97,9 +97,15 @@ def _corpus_texts(topic: str) -> dict[str, str]:
     out = {}
     for f in sorted(folder.glob("*.txt")):
         try:
-            out[f.name] = f.read_text(encoding="utf-8")
+            text = f.read_text(encoding="utf-8")
         except OSError:
             continue
+        # QUELLE:-Header (Metadata, kein Lerninhalt) strippen — sonst bildet er bei großen
+        # Seiten einen isolierten, block-losen Abschnitt = False-Positive-Lücke.
+        lines = text.splitlines()
+        if lines and lines[0].startswith("QUELLE:"):
+            text = "\n".join(lines[1:]).lstrip("\n")
+        out[f.name] = text
     return out
 
 
diff --git a/frontend/src/components/BlockFocus.vue b/frontend/src/components/BlockFocus.vue
index 6d4d297..63dc087 100644
--- a/frontend/src/components/BlockFocus.vue
+++ b/frontend/src/components/BlockFocus.vue
@@ -200,8 +200,6 @@ watch(() => `${props.block.title}|${props.block.md}|${props.block.compact || ''}
           <template v-for="(seg, si) in segments" :key="si">
             <div :class="{ 'sub-stufe': !!seg.level }"
                  :style="seg.level ? { '--stufe-farbe': VIEW_FARBE[SUB_RANK[seg.level] || 1] } : null">
-              <span v-if="seg.level" class="sub-stufe-badge"
-                    :title="`Stufe ${VIEW_KURZ[SUB_RANK[seg.level] || 1]}`">{{ VIEW_KURZ[SUB_RANK[seg.level] || 1] }}</span>
               <template v-for="b in seg.blocks" :key="b.i">
                 <div class="md-block" v-html="b.html" @contextmenu.prevent="blockMenu(b.i, $event)"></div>
                 <div v-if="suggestions[b.i]" class="block-vorschlag">
diff --git a/frontend/src/components/GenerationView.vue b/frontend/src/components/GenerationView.vue
index c37e648..c084668 100644
--- a/frontend/src/components/GenerationView.vue
+++ b/frontend/src/components/GenerationView.vue
@@ -222,7 +222,7 @@ function removeArtefactsClick() {
       <ProgressBar v-if="artefactProgress.total" :value="artefactProgress.value"
                    :label="`${artefactProgress.done}/${artefactProgress.total} Karten fertig · ${Math.round(artefactProgress.value * 100)} %`"
                    :hint="scopeGrowing ? 'Umfang wächst noch' : ''" />
-      <KanbanBoard :columns="artefactCols" :agents="board?.agents || []" :generating="generating" />
+      <KanbanBoard :columns="artefactCols" :generating="generating" />
     </section>
 
     <section class="gen-section">
diff --git a/frontend/src/components/TopicDetail.vue b/frontend/src/components/TopicDetail.vue
index ee242c6..12efc3f 100644
--- a/frontend/src/components/TopicDetail.vue
+++ b/frontend/src/components/TopicDetail.vue
@@ -57,11 +57,11 @@ function htmlFor(s) {
       if (rank > lvl) continue
       const body = renderMarkdown(compact ? (sub.compact || sub.md) : (sub.md || sub.compact))
       if (props.stufeAnsicht === 'auto' && rank > 1 && rank === lvl) {
-        // gerade neu freigeschaltete Stufe: kräftiger hervorheben
-        parts.push(`<div class="sub-neu" style="--neu-farbe:${VIEW_FARBE[rank]}"><span class="sub-neu-badge" title="Neu ab Stufe ${VIEW_KURZ[rank]}">${VIEW_KURZ[rank]}</span>${body}</div>`)
+        // gerade neu freigeschaltete Stufe: kräftigere Färbung (Rand), ohne Badge
+        parts.push(`<div class="sub-neu" style="--neu-farbe:${VIEW_FARBE[rank]}">${body}</div>`)
       } else {
-        // jede Stufe A/F/E/V leicht in ihrer Farbe kennzeichnen (Rand + Färbung + Badge)
-        parts.push(`<div class="sub-stufe" style="--stufe-farbe:${VIEW_FARBE[rank]}"><span class="sub-stufe-badge" title="Stufe ${VIEW_KURZ[rank]}">${VIEW_KURZ[rank]}</span>${body}</div>`)
+        // jede Stufe A/F/E/V leicht in ihrer Farbe kennzeichnen (Rand + Färbung), ohne Badge
+        parts.push(`<div class="sub-stufe" style="--stufe-farbe:${VIEW_FARBE[rank]}">${body}</div>`)
       }
     }
     h = parts.join('')
diff --git a/templates/Prompt/Blocks-Gruppierung.md b/templates/Prompt/Blocks-Gruppierung.md
index 0733676..6060cc5 100644
--- a/templates/Prompt/Blocks-Gruppierung.md
+++ b/templates/Prompt/Blocks-Gruppierung.md
@@ -1,6 +1,6 @@
 Topic "{topic}". A previous step produced a flat list of learning blocks that is TOO FINE-GRAINED — several blocks are **constituent sub-definitions / notation of ONE larger definition or model** and should become a single umbrella block. Find these groups. A good run finds several genuine umbrellas AND leaves most blocks standalone; judge each candidate on its merits.
 
-**Propose real umbrellas, but don't force them.** A downstream guard only rejects umbrellas that swallow a named theory-of-computation result (algorithm/problem/theorem/complexity class) — it does NOT catch a wrongly-swallowed engineering skill or procedure. So when a member could stand as its own lesson (test 3 below), keep it separate rather than merge on a hunch. But do NOT withhold a genuine merge merely because the members are lexically dissimilar (facets of one model routinely are) or because you are unsure of the parent's exact name.
+**Propose real umbrellas, judge each on its merits.** Merge when the members are constituent parts of one whole (test 3); keep a member separate when it stands as a full, usable unit on its own. Do NOT withhold a genuine merge merely because the members are lexically dissimilar (facets of one whole routinely are) or because you are unsure of the parent's exact name.
 
 CANDIDATES (your starting point):
 {candidates}
@@ -9,9 +9,9 @@ FULL BLOCK LIST (you may pull in ANY numbers below that are constituents of the
 {list}
 
 ## Merge test — propose an umbrella when ALL THREE hold
-1. **One parent.** The members are constituent parts/facets of ONE named parent model or definition — each member PRESUPPOSES that parent (you cannot introduce the member without first invoking the parent). TM-model parts (Konfiguration, Übergangsfunktion δ, Alphabet Σ, Akzeptierende Berechnung) presuppose „Turingmaschine"; KNF parts (Literale, Klauseln, Boolesche Variablen) presuppose „Konjunktive Normalform".
+1. **One parent.** The members are constituent parts/facets of ONE named parent (a model, system, setup, or definition) — each member PRESUPPOSES that parent: you cannot introduce it without first invoking the parent, and it has no purpose outside it.
 2. **Studied together.** A learner meets them together as one unit.
-3. **No standalone unit among them.** No member is a concept a learner would study and be tested on in its OWN right — one with its own exercises or procedure that you could practice without first teaching the parent. **Litmus:** could this member be its own lesson with its own tasks? If yes, it is a SIBLING, not a facet of the parent — keep it separate. This covers BOTH domains: in theory-of-computation a named **algorithm, problem, theorem, reduction/transformation, or complexity class** („List Scheduling", „3-SAT", „Cook/Levin", „3-SAT ≤ Clique", „NP", „NP-Vollständigkeit", „Polynomielle Transformation"); in engineering a **self-contained skill or procedure** („Plugin-Konfiguration / config.xml", „PHPUnit-Test-Setup") — each is its own learning object. By contrast, a facet like „Alphabet Σ" or „Übergangsfunktion δ" has NO exercises of its own without the parent model → it stays a member.
+3. **No standalone unit among them — autonomy test (decisive).** Remove the OTHER members, then ask of each: does it still stand as a COMPLETE, usable unit with its own goal? YES → autonomous → a SIBLING, keep separate (dropping the others took nothing from it). NO → alone it serves no goal and exists only to build the shared parent → a constituent PART, merge it. Structural containment („X is a file/step/field of Y") is NOT the test — autonomy is: own goal, complete without the siblings. This holds in every domain.
 
 *Note on test 1: „can this be defined at all?" is the WRONG question — Alphabet Σ and DTM CAN be stated in isolation, yet in THIS topic they are parts of the Turing-machine model and belong together. The question is whether the member PRESUPPOSES the shared parent, not whether a standalone sentence exists.*