5474312
diff --git a/‎.gitignore‎
Lines changed: 3 additions & 0 deletions b/‎.gitignore‎
Lines changed: 3 additions & 0 deletions
diff --git a/‎CHANGELOG.md‎
Lines changed: 20 additions & 0 deletions b/‎CHANGELOG.md‎
Lines changed: 20 additions & 0 deletions
diff --git a/‎Dockerfile‎
Lines changed: 9 additions & 3 deletions b/‎Dockerfile‎
Lines changed: 9 additions & 3 deletions
@@ -141,6 +141,9 @@ n8n-mcp-wrapper.sh
 # MCP configuration files (all variants: .mcp.json, .mcp.json.bk, .mcp.json.bak, etc.)
 .mcp.json*
 
+# Local Codex MCP configuration can contain credentials
+.codex/config.toml
+
 # UI Apps build output
 ui-apps/dist/
 ui-apps/node_modules/
 
@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.66.1] - 2026-07-26
+
+### Changed
+
+- **Updated n8n to 2.31.x.** Bumped `n8n-nodes-base` 2.30.3 → 2.31.3, `n8n-core` 2.30.2 → 2.31.3, `n8n-workflow` 2.30.1 → 2.31.3, and `@n8n/n8n-nodes-langchain` 2.30.3 → 2.31.3. Rebuilt the node database (828 core nodes: 699 from `n8n-nodes-base` + 129 from `@n8n/n8n-nodes-langchain`).
+- **Refreshed community nodes.** Registry sync added 107 community nodes (1,348 → 1,455 total; 1,295 verified + 160 unverified). README metadata and AI summaries now cover 1,444/1,455 community nodes; the remaining 11 packages have no retrievable npm README to summarize.
+- Updated README n8n version badge and node counts (2,283 total nodes: 828 core + 1,455 community).
+- **The Docker builder no longer installs a stale dependency set.** Its builder stage installs a hand-maintained list rather than the repo's own dependencies, and four of those pins had drifted from `package.json`. Two mattered: `n8n-workflow@^2.4.2` resolved through the package's `latest` dist-tag — which lags the release n8n ships (2.16.1 against the 2.31.3 in `package.json`) — so the image compiled `src/` against older type definitions and failed on `agentSelector`; and `zod@3.24.1` broke `npm install` outright, because `n8n-workflow@2.31.3` declares an exact `zod: 3.25.67` peer dependency. All four are realigned (`zod`, `@modelcontextprotocol/sdk`, `axios`, `uuid`), and `scripts/update-n8n-deps.js` now re-syncs every pin naming a direct dependency instead of leaving the list to drift until a build breaks.
+
+### Added
+
+- **`agentSelector` property type.** n8n 2.31 introduced it for the Message an n8n Agent node (typeVersion 2), where it replaces the resource locator that picks the target agent. n8n validates it through the same path as `resourceLocator`, so it is wired into the same three places: `ConfigValidator`, the structure check in `EnhancedConfigValidator`, and the `expectedFormat` hint `get_node` returns. Its declared shape is `mode` plus `value` — the `__rl: true` marker n8n's editor writes is not required, matching n8n's own `isINodeParameterResourceLocator` guard.
+
+### Fixed
+
+- **HTTP Request was not recognised as an AI tool, so `httpRequestTool` was missing entirely.** n8n's flag is typed `usableAsTool?: true | UsableAsToolDescription`, and HTTP Request uses the object form on every version from 3 onwards to carry its codex replacements. Detection compared against `true` by identity and therefore rejected it. `nodes-base.httpRequestTool` is the most used tool node in the template corpus — 139 of 2,352 templates, against 6 for `slackTool` — and it was absent from the database, so `search_nodes` and `get_node` could not find it and `get_node` reported `hasUsableAsToolProperty: false` for HTTP Request. Worse, because HTTP Request was not marked as having a tool variant, wiring the plain `nodes-base.httpRequest` node into an `ai_tool` connection produced a bare `INVALID_AI_TOOL_SOURCE` with no suggested fix, while every correctly detected node returned a `WRONG_NODE_TYPE_FOR_AI_TOOL` error carrying a `tool-variant-correction` autofix. Any value other than `false`/absent now counts, matching n8n.
+- **Tool capability is read from the node's current version, as n8n reads it.** Detection accepted the flag from any entry in `nodeVersions`, but n8n resolves `nodeVersions[currentVersion]` before consulting `usableAsTool`. No node in 2.31.3 diverges, so the database is unchanged by this, but the looser rule would have invented a tool variant for any node that dropped tool support while keeping an older version — the same class of defect as the name-based guess removed below.
+- **AI tool detection missed versioned nodes, so 26 tool variants were absent from the database.** `usableAsTool` is read from a node's description, but `VersionedNodeType` assigns its version map in the constructor — reading `nodeVersions` off the class finds nothing, and a node that declares `usableAsTool` per version rather than on its base description was therefore never recognised. Commonly used tool variants — `slackTool`, `postgresTool`, `googleSheetsTool`, `googleDriveTool`, `notionTool`, `microsoftTeamsTool`, `mySqlTool`, `awsS3Tool` and 18 more — could not be found via `search_nodes`/`get_node`, and `validate_workflow` rejected workflows that used them as unknown node types. Detection now instantiates the node to read its versions. The same gap would have dropped `messageAnAgentTool` and `microsoftSharePointTool` in this release, as both became versioned nodes in n8n 2.31.
+- **Node types that n8n does not have are no longer invented.** Tool-variant generation fell back to a name check — a node whose name contained `ai`, `openai`, `anthropic`, `cohere` or `huggingface` was treated as tool-capable regardless of `usableAsTool`. That produced 26 node types n8n rejects, including `nodes-base.waitTool` (from "w-ai-t"), `nodes-base.openAiTool`, `nodes-langchain.lmChatAnthropicTool` and `nodes-langchain.embeddingsOpenAiTool`. An agent could wire one into a workflow, have it validate cleanly, and only find out at deploy time. `usableAsTool` is now the sole signal, matching n8n's own `node-helpers`.
+
 ## [2.66.0] - 2026-07-25
 
 ### Fixed
 
@@ -10,12 +10,18 @@ COPY tsconfig*.json ./
 
 # Create minimal package.json and install ONLY build dependencies
 # Note: openai and zod are needed for TypeScript compilation of template metadata modules
+#
+# These versions must match package.json. scripts/update-n8n-deps.js re-syncs them
+# on every n8n update. Two ways this list bites when it drifts: a stale n8n-workflow
+# compiles src against older type definitions (a range would resolve through the
+# `latest` dist-tag, which lags the release n8n ships), and a stale zod fails
+# `npm install` outright, because n8n-workflow declares an exact zod peer dependency.
 RUN --mount=type=cache,target=/root/.npm \
     echo '{}' > package.json && \
     npm install --no-save typescript@^5.8.3 @types/node@^22.15.30 @types/express@^5.0.3 \
-        @modelcontextprotocol/sdk@1.20.1 dotenv@^16.5.0 express@^5.1.0 axios@^1.10.0 \
-        n8n-workflow@^2.4.2 uuid@^11.0.5 @types/uuid@^10.0.0 \
-        openai@^4.77.0 zod@3.24.1 lru-cache@^11.2.1 @supabase/supabase-js@^2.57.4
+        @modelcontextprotocol/sdk@1.28.0 dotenv@^16.5.0 express@^5.1.0 axios@^1.18.1 \
+        n8n-workflow@2.31.3 uuid@^11.1.1 @types/uuid@^10.0.0 \
+        openai@^4.77.0 zod@3.25.67 lru-cache@^11.2.1 @supabase/supabase-js@^2.57.4
 
 # Copy source and build
 COPY src ./src