Stabile TRO-IDs: ID-Datei je Anlage, Wiederfinden ueber die Lage

- lib/tro_ids.py: cfg/<csv>_tro_ids.ini lesen/schreiben, TROs ueber die
  Lage ihrer Separatoren wiederfinden, neue IDs vergeben, Weggefallene melden
- tro_flow: Nummerierung entlang des Materialflusses, Schalter --ids,
  --renumber, --id-tolerance; Bericht der IDs
- tro_annotate: liest dieselbe ID-Datei (nur lesend)
- Tests tests/test_tro_ids.py, Doku Python_Scripts.md, Konzept (Stufe 1 erledigt)

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

CLAUDE.md

@@ -36,7 +36,9 @@ Template" below). What exists today is:
   `tro_annotate.py --emit-lisp`)
 - `cfg/dxf_registration.json` — persisted, verified CSV↔DXF coordinate transform;
   `cfg/tro_overrides.ini` — hand-maintained corrections to the derived TROs (see `tro_overrides.py`);
-  `cfg/e_planning.ini` — project-specific rules for assigning E-planning symbols to layout parts
+  `cfg/e_planning.ini` — project-specific rules for assigning E-planning symbols to layout parts;
+  `cfg/<csv>_tro_ids.ini` — per-plant TRO-ID file (versioned, IDs renamed by the SPS
+  programmers), created/extended by `tro_flow.py` via `lib/tro_ids.py`
 - `doc/*.md` — analysis documents that reverse-engineer the SCL patterns and propose the
   fuller JSON layout schema for the parts of the pipeline still to be built out
 
@@ -179,7 +181,10 @@ byte — rewrite them (`SKEL_UPDATE_GOLDEN=1`) only for a reviewed, intended cha
 
 1. **`lib/tro_flow.py --json`** (implemented) — writes `<csv>_tro.json` (schema
    `sps_skel-tro-v3`, `model.TroDocument`): TROs, system boundaries `SYSn`, connections with
-   their kind, findings. See `doc/Python_Scripts.md` §4.
+   their kind, findings. TRO-IDs come from `cfg/<csv>_tro_ids.ini` (`lib/tro_ids.py`): each
+   TRO is found again by the position of its separators, so IDs survive a new layout export
+   (TeileIds do not); `--renumber` renumbers along the material flow, `--ids` points another
+   export of the same plant at the same file. See `doc/Python_Scripts.md` §4.
 2. **`lib/scl_skeleton.py`** (implemented) — reads that TRO-JSON through `TroDocument` (a
    wrong/renamed key or `items` not matching the catalog stops the run) and emits an `FB_Main` SCL
    skeleton (`<source>_FB_Main.scl`): one `REGION` per TRO with the instance call and every