Docs: reflect implemented DXF->JSON->SCL first version

lib/scl_skeleton.py and lib/tro_extract.py already run the pipeline
end-to-end (annotated DXF -> TRO-JSON -> FB_Main SCL skeleton), but
CLAUDE.md and README.md still described these as unwritten tools
(tro_export.py / scl_gen.py). Update the current-state docs:

- CLAUDE.md: project purpose, reading order, roadmap section, and
  standard-template notes now describe the built pipeline plus the
  parts still open (full layout JSON schema, other per-controller
  blocks, timing defaults, --skip-json).
- README.md: bin/ tree and usage examples for tro_extract/scl_skeleton.
- doc/Python_Scripts.md: intro counts (8 modules / 5 CLI tools),
  header date, pipeline diagram, and tro_overrides.py in the lib list.

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

doc/Python_Scripts.md

@@ -1,12 +1,13 @@
 # Python Scripts — CLI Tooling Overview
 
-**As of:** 2026-08-03
+**As of:** 2026-08-20
 
-`lib/` currently holds five Python modules (three of them runnable CLI tools,
-two supporting libraries), plus one documentation-generator script that lives
+`lib/` currently holds eight Python modules (five of them runnable CLI tools,
+three supporting libraries), plus one documentation-generator script that lives
 under `doc/TRO_Katalog/tro_graphs/`. Together the CLI tools turn a CSV export
 of the mechanical layout (ILS 2.0) into a material-flow graph, a derived TRO
-list/diagram, and an annotated copy of the BricsCAD drawing.
+list/diagram, an annotated copy of the BricsCAD drawing, a TRO-JSON read back
+out of that drawing, and an `FB_Main` SCL skeleton generated from that JSON.
 
 This document is the practical "what does each script do and which switches
 does it take" reference. For the underlying domain model (TRO types, JSON
@@ -27,8 +28,14 @@ tro_flow.py       ──►  <name>_tro_flow.dot / .svg, _tro_doc.md, _tro_error
    │   (derives TROs, using the type catalog in tro_catalog.py)
    ▼
 tro_annotate.py   ──►  <name>_annotated.dxf, <name>_registration.json
-   (also needs the BricsCAD DXF; uses dxf_registration.py for the CSV↔DXF
-    coordinate offset and tro_catalog.py for marker shape/color per TRO type)
+   │   (also needs the BricsCAD DXF; uses dxf_registration.py for the CSV↔DXF
+   │    coordinate offset and tro_catalog.py for marker shape/color per TRO type)
+   ▼   (drawing may be hand-edited in BricsCAD before the next step)
+tro_extract.py    ──►  <drawing>_tro.json
+   │   (reads only the drawing; resolves plant coords via the registration)
+   ▼
+scl_skeleton.py   ──►  <source>_FB_Main.scl
+   (one REGION per TRO; E-planning values left as TODO(E-Planung) gaps)
 ```
 
 - `material_flow.py` models the material flow of the **mechanical** objects only
@@ -47,6 +54,9 @@ Supporting libraries (no CLI of their own, imported by the tools above):
 - **`lib/dxf_registration.py`** — derives, verifies and persists the rigid
   (rotation + offset) transform between the CSV export's coordinate system and
   the DXF drawing's.
+- **`lib/tro_overrides.py`** — reads the hand-maintained
+  `%SKEL_CFG%\tro_overrides.ini` (type corrections, open points, TRO merges)
+  that survive re-runs of `tro_flow.py`. See §6a.
 
 Separate, documentation-only tool (not part of the generator pipeline):
 
@@ -74,7 +84,7 @@ bin\tro_annotate.bat --file mubea.csv --dxf 500573_60_1.dxf --flow --fb --legend
 (`--use-cords` lays both graphs out at the real plant coordinates; drop it for
 Graphviz's computed left-to-right arrangement.)
 
-Conventions shared by all three tools:
+Conventions shared by the CLI tools:
 
 - `--file` / `--dxf` accept either a bare filename — resolved against
   `%SKEL_DATA%` — or a full path.