patch 16

COMMAND_REF.md

@@ -18,6 +18,7 @@ Diese Referenz ist gegen den realen Codebestand abgeglichen und ersetzt die vera
 | `mto:agent:system:rebuild` | System | Globaler Hard-Rebuild von Chunks, Vektorindex, Tags und optional Service-Reload |
 | `mto:agent:config:validate` | Config / Governance | Validiert die effektive RetrieX-Konfiguration |
 | `mto:agent:config:audit-source` | Config / Governance | Auditiert YAML-Mappings gegen PHP-Fallbacks und Defaults |
+| `mto:agent:config:audit-patterns` | Config / Governance | Auditiert fachliche Pattern-, Token- und Signalreste im PHP-Core |
 | `mto:agent:config:dump-effective` | Config / Governance | Gibt die effektive Konfigurationsinventur aus |
 | `mto:agent:regression:test` | Config / Governance | Fuehrt Offline-Regression-Guards fuer stabile Pfade aus |
 | `mto:agent:vector:rebuild` | Vector | Baut den Chunk-Vektorindex aus `index.ndjson` neu |
@@ -556,3 +557,29 @@ Der aktuelle Custom-CLI-Umfang des Systems besteht aus mindestens **18 projektsp
 - `mto:agent:vector:health`
 - `mto:agent:tags:rebuild`
 - `mto:agent:tag:health`
+
+### `mto:agent:config:audit-patterns`
+
+Audits remaining pattern-, token- and signal-sensitive calls in PHP core files for developer-policy review.
+
+**Signature**
+```bash
+bin/console mto:agent:config:audit-patterns [--details] [--json] [--all]
+```
+
+**Purpose**
+- finds configured calls such as `preg_match`, `str_contains`, `in_array` and related pattern/token helpers in configured source roots
+- raises WARN findings when configured domain marker terms are involved
+- keeps the command non-blocking and review-oriented; it does not change runtime behavior and does not activate strict validation
+
+**Options**
+- `--details` renders reviewable warning rows
+- `--json` renders machine-readable audit output
+- `--all` includes lower-priority REVIEW findings in addition to WARN findings
+
+**Expected use before merge**
+```bash
+bin/console mto:agent:config:audit-patterns --details
+```
+
+Review WARN findings and move new semantic terms, product names, intent words, commerce signals or retrieval/follow-up patterns to YAML-backed configuration when they are not purely technical.