docs: clarify exporter maturity and lint fixtures

Author: DKFuH

README.md

@@ -111,6 +111,27 @@ Generated examples live under:
 
 - [docs/demos](./docs/demos)
 
+## Exporter Maturity
+
+To avoid false expectations, exporters are grouped by maturity level.
+
+Stable:
+
+- `json`
+- `context`
+- `markdown`
+- `html`
+- `graph`
+
+Experimental / scaffold:
+
+- `contract`
+- `bpmn`
+- `plantuml`
+- `littlehorse`
+
+Experimental exporters are intended as skeletons or integration scaffolds and may require manual review.
+
 ## Hero Demo: Craft Business Lead to Order
 
 The main showcase flow is:
@@ -238,6 +259,8 @@ npm run check:all
 npm run demo:generate
 ```
 
+Note: files under `tests/lint/` are intentionally invalid and are used to verify lint findings. Running `orgscript lint` on those fixtures is expected to fail.
+
 ## Ecosystem
 
 - VS Code extension: [editors/vscode](./editors/vscode)

docs/OrgScript-Handbuch-DE.md

@@ -178,6 +178,23 @@ Standardverhalten der Exporter:
 
 So bleibt Geschaeftslogik explizit und Kommentare werden keine versteckte zweite Sprache.
 
+## Exporter-Reifegrade
+
+Stabil:
+
+- `json`
+- `context`
+- `markdown`
+- `html`
+- `graph`
+
+Experimentell / Scaffold:
+
+- `contract`
+- `bpmn`
+- `plantuml`
+- `littlehorse`
+
 ## Schreibregeln
 
 - eine Anweisung pro Zeile

docs/OrgScript-Manual-EN.md

@@ -178,6 +178,23 @@ Default exporter policy:
 
 This keeps business meaning explicit and prevents comments from becoming a hidden second language.
 
+## Exporter maturity
+
+Stable:
+
+- `json`
+- `context`
+- `markdown`
+- `html`
+- `graph`
+
+Experimental / scaffold:
+
+- `contract`
+- `bpmn`
+- `plantuml`
+- `littlehorse`
+
 ## Writing guidelines
 
 - keep one statement per line