p85b

patch_history/RETRIEX_PATCH_85B_GENERIC_DEVICE_EXACT_PARAMETER_ANCHOR_README.md

@@ -0,0 +1,107 @@
+# RetrieX Patch p85b - Generic Device Exact Parameter Anchor
+
+## Goal
+
+Harden p85 for generic device shop queries where a requested measurement parameter points to a concrete device variant.
+
+Motivating flow:
+
+```text
+suche gerät kühlsysteme Silikatüberwachung
+```
+
+p85 correctly recognized a generic device query and added a family anchor, but the resulting query was still too broad:
+
+```text
+testomat kühlsysteme silikatüberwachung
+```
+
+That can surface unrelated Testomat devices which mention cooling towers or silicate deposits but do not explicitly represent SiO2/Silicate monitoring as the requested measurement parameter.
+
+## Problem
+
+`gerät` is only a weak product-role signal. For `Silikatüberwachung`, the RAG device overview contains a more specific model-style identity: `Testomat 808 SiO2`.
+
+A broad family query such as `testomat silikatüberwachung` can produce noisy live-shop hits, for example Testomat devices for hardness, chlorine or self-cleaning contexts. Those hits must not be presented as precise Silicate-monitoring devices unless the same shop product identity or record explicitly supports that parameter.
+
+## Solution
+
+p85b keeps the p85 concept but makes the Silicate/SiO2 branch exact:
+
+```yaml
+shop_query_runtime:
+  generic_device_anchor:
+    anchor_rules:
+      - anchor: testomat 808 sio2
+        template: '{anchor}'
+        match_terms:
+          - silikat
+          - silikatüberwachung
+          - sio2
+          - kieselsäure
+```
+
+The generic `testomat` rule no longer contains the Silicate/Cooling-system terms. This means:
+
+- `gerät + Silikat/SiO2` becomes the precise shop query `testomat 808 sio2`.
+- `gerät + kühlsysteme` alone no longer forces a Testomat anchor.
+- Other p85 mappings stay intact, e.g. `gerät redox` -> `pockettester redox`.
+
+p85b also allows optional per-rule templates for generic device anchors. The default remains `{anchor} {query}`, but a specific rule may choose `{anchor}` when preserving the original context would make the Shopware search less precise.
+
+Finally, the configured Testomat model-anchor regex now accepts alphanumeric suffixes that contain at least one letter, e.g. `Testomat 808 SiO2`, without treating pure year-like suffixes such as `2019` as model variants.
+
+## Expected examples
+
+```text
+suche gerät kühlsysteme Silikatüberwachung
+=> testomat 808 sio2
+```
+
+```text
+gerät kühlsysteme
+=> no Testomat family anchor is injected solely from the application word
+```
+
+```text
+gerät redox
+=> pockettester redox
+```
+
+```text
+testomat gerät freies chlor
+=> unchanged by generic-device anchoring because `testomat` is already present
+```
+
+```text
+Testomat 808 SiO2
+=> recognized as a concrete model anchor for result-identity filtering
+```
+
+## Files changed
+
+- `config/retriex/genre.yaml`
+- `config/retriex/agent.yaml`
+- `src/Agent/AgentRunner.php`
+- `src/Config/AgentRunnerConfig.php`
+- `src/Config/RetriexEffectiveConfigProvider.php`
+
+## Local checks
+
+```text
+php -l src/Agent/AgentRunner.php
+php -l src/Config/AgentRunnerConfig.php
+php -l src/Config/RetriexEffectiveConfigProvider.php
+python3 YAML parse for config/retriex/genre.yaml and config/retriex/agent.yaml
+standalone smoke simulation for generic-device exact-anchor behavior
+PHP regex smoke for Testomat 808 SiO2 / Testomat 808 2019 / Testomat 2000 THCL / Testomat LAB CL
+```
+
+Symfony console checks require the deployment environment with `vendor/`:
+
+```text
+bin/console mto:agent:config:validate
+bin/console mto:agent:regression:test
+bin/console mto:agent:config:audit-source --details
+bin/console mto:agent:config:audit-patterns --details
+```