# RetrieX Shop Query Context Cleanup Hotfix

Purpose:
- Keeps the existing language preservation and meta-query guard behavior.
- Fixes the follow-up case where a meta command such as "suche im shop" reused the full previous user question as the Shopware search query.
- The fallback now extracts a compact, generic shop query from recent context, e.g.:
  - "mit welchem testomat kann ich freies chlor messen" -> "testomat freies chlor"

Design constraints:
- No retrieval changes.
- No product-family-specific special cases.
- No Testomat 808 / Testomat 2000 / Tritromat hardcoding.
- Filtering terms are configurable in config/retriex/agent.yaml.
- PHP defaults remain as safety fallback.

Changed files:
- config/retriex/agent.yaml
- src/Agent/AgentRunner.php
- src/Config/AgentRunnerConfig.php
- src/Config/RetriexEffectiveConfigProvider.php

Recommended after applying:
- php bin/console cache:clear
- php bin/console mto:agent:config:validate
- php bin/console mto:agent:regression:test

Manual regression:
1. Ask: mit welchem testomat kann ich freies chlor messen
2. Then: suche im shop
3. Expected shop query should be a compact product/parameter query such as:
   testomat freies chlor
   It must not be the full previous prompt.