magector 2.16.9 → 2.16.10

package/README.md

@@ -1029,9 +1029,15 @@ lib/internal
 The `magento_trace_config` tool can show actual database config values alongside code analysis. Export your `core_config_data` table as JSON and place files in `.magector/config-data/`:
 
 ```bash
-# Export from MySQL (one-time per environment)
+# MySQL 8.0+ with --json flag
 mysql -u user -p magento_db -e "SELECT scope, scope_id, path, value FROM core_config_data" --json > .magector/config-data/CZ-production.json
 
+# Older MySQL (no --json): pipe through python3
+mysql -u user -p magento_db -B -e "SELECT scope, scope_id, path, value FROM core_config_data" | \
+  python3 -c "import sys,json; lines=sys.stdin.read().strip().split('\n'); h=lines[0].split('\t'); \
+  rows=[dict(zip(h,l.split('\t'))) for l in lines[1:]]; [r.update({'scope_id':int(r['scope_id'])}) for r in rows]; \
+  json.dump(rows,sys.stdout,indent=2)" > .magector/config-data/CZ-production.json
+
 # Or from n8n/API/any tool that produces:
 # [{scope, scope_id, path, value}, ...]
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "magector",
-  "version": "2.16.9",
+  "version": "2.16.10",
   "description": "Semantic code search for Magento 2 — index, search, MCP server",
   "type": "module",
   "main": "src/mcp-server.js",
@@ -33,10 +33,10 @@
     "ruvector": "^0.1.96"
   },
   "optionalDependencies": {
-    "@magector/cli-darwin-arm64": "2.16.9",
-    "@magector/cli-linux-x64": "2.16.9",
-    "@magector/cli-linux-arm64": "2.16.9",
-    "@magector/cli-win32-x64": "2.16.9"
+    "@magector/cli-darwin-arm64": "2.16.10",
+    "@magector/cli-linux-x64": "2.16.10",
+    "@magector/cli-linux-arm64": "2.16.10",
+    "@magector/cli-win32-x64": "2.16.10"
   },
   "keywords": [
     "magento",

package/src/mcp-server.js

@@ -3945,9 +3945,11 @@ function formatTraceConfigResult(result) {
     let hasData = false;
     try { hasData = existsSync(dataDir) && readdirSync(dataDir).some(f => f.endsWith('.json')); } catch {}
     if (!hasData) {
-      text += '### Actual Values\nNo config-data exports found. Export `core_config_data` to `.magector/config-data/{env}.json` (format: `[{scope, scope_id, path, value}, ...]`).\n\n';
+      text += '### Actual Values\n**ACTION REQUIRED:** No config-data exports found. Ask the user to export `core_config_data` from their database and place the JSON file at `.magector/config-data/{country}-{environment}.json` (format: `[{scope, scope_id, path, value}, ...]`). Without this data, actual config values cannot be shown.\n\n';
     } else {
-      text += '### Actual Values\nNo matching values found in config-data exports.\n\n';
+      // Show which environments ARE available so agent knows what's missing
+      const availableEnvs = Object.keys(loadAllConfigData()).join(', ');
+      text += `### Actual Values\nNo matching values found in available exports (${availableEnvs}). If you need values from a different environment, ask the user to provide the export.\n\n`;
     }
   }
 
@@ -4789,7 +4791,7 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
     },
     {
       name: 'magento_trace_config',
-      description: 'Trace a Magento config path end-to-end: finds system.xml admin definition (label, type, source_model), PHP classes that read the value, and actual DB values from config-data exports. Use when investigating config-driven behavior ("why is this feature enabled/disabled?", "what controls marketplace payment methods?"). Accepts either an exact config path or a keyword to search for.',
+      description: 'Trace a Magento config path end-to-end: finds system.xml admin definition (label, type, source_model), PHP classes that read the value, and actual DB values from config-data exports. Use when investigating config-driven behavior ("why is this feature enabled/disabled?", "what controls marketplace payment methods?"). Accepts either an exact config path or a keyword to search for. IMPORTANT: If the output says no config-data exports are available, or if the analysis needs config values from a country/environment not yet exported, ask the user to provide the export. They can run a one-time MySQL query and place the JSON file in .magector/config-data/{country}-{environment}.json.',
       inputSchema: {
         type: 'object',
         properties: {