Doku: Datenquellen Layout/Hardwareplanung, Konzept Layout+Hardware -> SCL

- Klassenhierarchie.md, Kapitel Daten: vollstaendige Rohangaben aus
  Anlagen-Hardware (CSV-Spalten, Merkmale je TeileArt) und Hardwareplanung
  (EA-Liste, TIA-Import, WSCAD, positionsdraw)
- Datenquellen_Layout_Hardwareplanung.md: was TROs/SCL aus Layout,
  Hardwareplanung und Defaults bekommen; 1Sep1Swi- und Vario-Aufruf
  zeilenweise mit Herkunft
- Konzept_Layout_Hardware_SCL.md: Zielablauf tro_flow -> hw_import ->
  hw_assign -> scl_skeleton, Rolle der bestehenden Skripte, Festlegungen
  zu TRO-IDs (stabil ueber Lage, --renumber) und Staubereichen
- CLAUDE.md: beide neuen Dokumente in der Leseliste

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

CLAUDE.md

@@ -138,6 +138,16 @@ this order for onboarding:
    its generated images come from `doc/TRO_Katalog/tro_graphs/gen_tro_graphs.py`
    (doc-tooling, not part of the generator — see `doc/Python_Scripts.md` §8) built from
    `doc/TRO_Katalog/connect.ini`.
+9. **`doc/Datenquellen_Layout_Hardwareplanung.md`** — which TRO/SCL data comes from the
+   mechanical layout (CSV), which from the hardware planning (EA list, TIA import,
+   WSCAD, `positionsdraw`) and which is a default; two reference call sites annotated
+   line by line. The full raw field lists of both sources are in
+   `doc/Klassenhierarchie.md`, chapter "Daten".
+10. **`doc/Konzept_Layout_Hardware_SCL.md`** — the target workflow (planned, not built):
+    layout → `<csv>_tro.json` (with slots, `jamAreas`), hardware planning →
+    `hw_import.py` → `<projekt>_hw.json`, `hw_assign.py` → `<csv>_anlage.json`,
+    then `scl_skeleton.py`; what happens to `e_planning.py` (split),
+    `tro_annotate.py` (viewer reading the JSON) and `tro_extract.py` (dropped).
 
 ### Used libraries (referenced but not vendored)