scl_templates: Aufruf-Template FB_ILS_MTRO_2Sep2Swi (ohne Referenz-Aufrufstelle)

Mubea wird damit vollstaendig aus Templates erzeugt. Der FB existiert noch
nicht in der ILSLib; die Schnittstelle ist aus 2Sep1Swi (Separatoren) und
1Sep2Swi (Weichen) angenommen und steht im Template-Kopf - mit den
SPS-Kollegen abzustimmen.

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

doc/Python_Scripts.md

@@ -626,8 +626,10 @@ with a real reference call site (`1Sep`, `1Sep1Swi`, `1Sep2Swi`, `1Sep_SSCC`,
 `Vario`, `Vario_workStation`, `PinStore_Auto`); each follows its call site in
 `doc/TRO_Katalog/scl_templates/` line for line, and every value that is still
 open carries `TODO(E-Planung)`. The line decisions are proposals to be confirmed
-by a PLC engineer (`doc/SCL_Templates.md` §6). `2Sep1Swi`, `EmptyCarrBuffer`,
-`LoadingBoom` and `2Sep2Swi` have no call site yet and stay generic. `--strict` stops (exit `1`, no SCL) if any FB type has no
+by a PLC engineer (`doc/SCL_Templates.md` §6). `2Sep1Swi`, `EmptyCarrBuffer` and
+`LoadingBoom` have no call site yet and stay generic. `2Sep2Swi` has a template without
+a call site (FB not yet in the ILSLib, interface assumed from `2Sep1Swi` + `1Sep2Swi`).
+`--strict` stops (exit `1`, no SCL) if any FB type has no
 template. Without `--templates` the output is unchanged.
 
 **Names from the plant JSON (stage 4, `--json <csv>_anlage.json`).** The
@@ -975,8 +977,11 @@ verified against `data/*.scl` where the source is vendored locally, and against
 > Kreisel2/Kreisel1 touch as a single control object with 2 separators,
 > 2 scanners and 2 switches. **`FB_ILS_MTRO_2Sep2Swi` does not exist** in this
 > repository or in `doc/TRO_Katalog/scl_templates/`, and has to be created in
-> the ILSLib — otherwise a future SCL generator will emit a call to a missing
-> block. The closest verified type is `2Sep1Swi` (2 separators, 2 scanners,
+> the ILSLib — otherwise the generated FB_Main calls a missing block. Since
+> 2026-10-28 there is a call-site template `lib/scl_templates/FB_ILS_MTRO_2Sep2Swi.scl.j2`
+> whose header lists the assumed interface (separators as in `2Sep1Swi`, switches
+> as in `1Sep2Swi`) - the FB has to be created to match it, or the template
+> adjusted. The closest verified type is `2Sep1Swi` (2 separators, 2 scanners,
 > **1** switch), which matches the hardware actually present in that export.
 > `3Sep2Swi` (3 separators, 3 scanners, 2 switches) was added on 2026-10-14
 > for the test plant `data/export.csv`, where one Kreisel pulley touches two