tro_annotate: selten gebrauchte Optionen entfernt

- --max-residual: feste Grenze DEFAULT_MAX_RESIDUAL (600 mm), Meldung
  verweist auf --offset
- --layer-prefix: Layer immer mit Praefix TRO_
- --use-overrides: cfg/tro_overrides.ini wird nie gelesen, Marker passen
  damit immer zum TRO-Fluss
- damit toter Code entfernt: draw_open_points, Layer TRO_OPENPOINT,
  Berichtszeilen Offene Punkte/Typkorrekturen (Daten kamen nur aus der INI)
- --emit-lisp bleibt (einziger Weg, tro_types.lsp fuer TRO_INSERT/TRO_EDIT
  nach einem neuen Katalogtyp neu zu schreiben)
- doc/Python_Scripts.md nachgezogen

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

doc/Python_Scripts.md

@@ -337,19 +337,21 @@ overridden.
 | `--legend` | — | off | Draw a legend of the color groups. |
 | `--marker-size` | `MM` (float) | `300.0` | Marker radius in mm. |
 | `--text-height` | `MM` (float) | `220.0` | Text height in mm. |
-| `--layer-prefix` | `P` | `TRO_` | Prefix for the layers this tool creates. |
-| `--offset` | `DX,DY` | — | Set the CSV↔DXF offset by hand instead of deriving/loading it. |
+| `--offset` | `DX,DY` | — | Set the CSV↔DXF offset by hand instead of deriving/loading it. For a drawing built with dxfmakros (CSV exported from the same drawing) this is `0,0`. |
 | `--re-register` | — | off | Re-derive the coordinate offset even if a verified one is already cached in `%SKEL_CFG%`. |
-| `--max-residual` | `MM` (float) | `600.0` | Largest residual error of the coordinate registration that is still accepted; above it the run fails (exit 4). |
 | `--check` | — | off | Dry run: only analyze and report, write no output file. |
 | `--emit-lisp` | — | off | Regenerate `cad/tro_types.lsp` (the type list for the `TRO_INSERT`/`TRO_EDIT` dialogs) from `tro_catalog.py` and exit — no `--dxf` needed. Written under `%DXFM_LISP%` if set (next to the `dxfmakros` SSG_LIB modules that provide the dialogs), otherwise under `<SPS_SKEL>/cad`. |
 
+Layers always carry the prefix `TRO_`. `cfg/tro_overrides.ini` is never read,
+so the markers always match `tro_flow.py` (which reads it only with
+`--use-overrides`).
+
 **Output** (in `%SKEL_RESULTS%`, unless `--check`): `<name>_annotated.dxf`,
 `<name>_registration.json` (the coordinate transform used, with its proof).
 
 **Exit codes:** `0` ok · `1` input/CLI error · `4` coordinate registration
-could not be proven (or exceeds `--max-residual`) — resolve with `--offset` or
-by raising `--max-residual`.
+could not be proven (or its residual error exceeds 600 mm) — resolve with
+`--offset`.
 
 ## 5a. `tro_extract.py` — read the TROs back out of the drawing into JSON
 
@@ -534,13 +536,12 @@ Three kinds of entry, deliberately different in weight:
   flow node is primary, the rest stay attached so the linking still sees both
   sides of a transition. Like splits, this renumbers.
 - **`openpoint`** — a spot reported in a review that is **not** turned into a
-  TRO. The structure stays untouched; the point is only marked, in the doc
-  (section 6) and in the annotated drawing on layer `TRO_OPENPOINT` as a red
-  crossed circle with plain-text label. This keeps "derived" and "asserted"
-  distinguishable until the spot has been checked in BricsCAD.
+  TRO. The structure stays untouched; the point is only marked in the doc
+  (section 6). This keeps "derived" and "asserted" distinguishable until the
+  spot has been checked in BricsCAD.
 
-Consumers: `tro_flow.py` (type corrections + doc section 6), `tro_annotate.py`
-(corrected marker types + open-point markers), `material_flow.py` (writes the
+Consumers: `tro_flow.py` (only with `--use-overrides`: type corrections + doc
+section 6), `material_flow.py` (writes the
 `[<plant>.manual]` section into `connect.ini`). Unknown TRO IDs and types are
 not applied silently — they are reported as warnings in the console output and
 in doc section 6.3, which catches the common trap: **TRO IDs are running