chore: update n8n to v1.116.2 (#348)

* docs: Update CLAUDE.md with development notes

* chore: update n8n to v1.116.2

- Updated n8n from 1.115.2 to 1.116.2
- Updated n8n-core from 1.114.0 to 1.115.1
- Updated n8n-workflow from 1.112.0 to 1.113.0
- Updated @n8n/n8n-nodes-langchain from 1.114.1 to 1.115.1
- Rebuilt node database with 542 nodes
- Updated version to 2.20.7
- Updated n8n version badge in README
- All changes will be validated in CI with full test suite

Conceived by Romuald Członkowski - www.aiadvisors.pl/en

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: regenerate package-lock.json to sync with updated dependencies

Fixes CI failure caused by package-lock.json being out of sync with
the updated n8n dependencies.

- Regenerated with npm install to ensure all dependency versions match
- Resolves "npm ci" sync errors in CI pipeline

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: align FTS5 tests with production boosting logic

Tests were failing because they used raw FTS5 ranking instead of the
exact-match boosting logic that production uses. Updated both test files
to replicate production search behavior from src/mcp/server.ts.

- Updated node-fts5-search.test.ts to use production boosting
- Updated database-population.test.ts to use production boosting
- Both tests now use JOIN + CASE statement for exact-match prioritization

This makes tests more accurate and less brittle to FTS5 ranking changes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: prioritize exact matches in FTS5 search with case-insensitive comparison

Root cause: SQL ORDER BY was sorting by FTS5 rank first, then CASE statement.
Since ranks are unique, the CASE boosting never applied. Additionally, the
CASE statement used case-sensitive comparison which failed to match nodes
like "Webhook" when searching for "webhook".

Changes:
- Changed ORDER BY from "rank, CASE" to "CASE, rank" in production code
- Added LOWER() for case-insensitive exact match detection
- Updated both test files to match the corrected SQL logic
- Exact matches now consistently rank first regardless of FTS5 score

Impact:
- Improves search quality by ensuring exact matches appear first
- More efficient SQL (less JavaScript sorting needed)
- Tests now accurately validate production search behavior
- Fixes 2/705 failing integration tests

Verified:
- Both tests pass locally after fix
- SQL query tested with SQLite CLI showing webhook ranks 1st

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: update CHANGELOG with FTS5 search fix details

Added comprehensive documentation for the FTS5 search ranking bug fix:
- Problem description with SQL examples showing wrong ORDER BY
- Root cause analysis explaining why CASE statement never applied
- Case-sensitivity issue details
- Complete fix description for production code and tests
- Impact section covering search quality, performance, and testing
- Verified search results showing exact matches ranking first

This documents the critical bug fix that ensures exact matches
appear first in search results (webhook, http, code, etc.) with
case-insensitive matching.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

CHANGELOG.md

@@ -7,6 +7,96 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.20.7] - 2025-10-22
+
+### 🔄 Dependencies
+
+**Updated n8n to v1.116.2**
+
+Updated all n8n dependencies to the latest compatible versions:
+- `n8n`: 1.115.2 → 1.116.2
+- `n8n-core`: 1.114.0 → 1.115.1
+- `n8n-workflow`: 1.112.0 → 1.113.0
+- `@n8n/n8n-nodes-langchain`: 1.114.1 → 1.115.1
+
+**Database Rebuild:**
+- Rebuilt node database with 542 nodes from updated n8n packages
+- All 542 nodes loaded successfully from both n8n-nodes-base (439 nodes) and @n8n/n8n-nodes-langchain (103 nodes)
+- Documentation mapping completed for all nodes
+
+**Testing:**
+- Changes validated in CI/CD pipeline with full test suite (705 tests)
+- Critical nodes validated: httpRequest, code, slack, agent
+
+### 🐛 Bug Fixes
+
+**FTS5 Search Ranking - Exact Match Prioritization**
+
+Fixed critical bug in production search where exact matches weren't appearing first in search results.
+
+#### Problem
+- SQL ORDER BY clause was `ORDER BY rank, CASE ... END` (wrong order)
+- FTS5 rank sorted first, CASE statement only acted as tiebreaker
+- Since FTS5 ranks are always unique, CASE boosting never applied
+- Additionally, CASE used case-sensitive comparison failing to match nodes like "Webhook" when searching "webhook"
+- Result: Searching "webhook" returned "Webflow Trigger" first, actual "Webhook" node ranked 4th
+
+#### Root Cause Analysis
+**SQL Ordering Issue:**
+```sql
+-- BEFORE (Broken):
+ORDER BY rank, CASE ... END  -- rank first, CASE never used
+-- Result: webhook ranks 4th (-9.64 rank)
+-- Top 3: webflowTrigger (-10.20), vonage (-10.09), renameKeys (-10.01)
+
+-- AFTER (Fixed):
+ORDER BY CASE ... END, rank  -- CASE first, exact matches prioritized
+-- Result: webhook ranks 1st (CASE priority 0)
+```
+
+**Case-Sensitivity Issue:**
+- Old: `WHEN n.display_name = ?` (case-sensitive, fails on "Webhook" vs "webhook")
+- New: `WHEN LOWER(n.display_name) = LOWER(?)` (case-insensitive, matches correctly)
+
+#### Fixed
+
+**1. Production Code** (`src/mcp/server.ts` lines 1278-1295)
+- Changed ORDER BY from: `rank, CASE ... END`
+- To: `CASE WHEN LOWER(n.display_name) = LOWER(?) ... END, rank`
+- Added case-insensitive comparison with LOWER() function
+- Exact matches now consistently appear first in search results
+
+**2. Test Files Updated**
+- `tests/integration/database/node-fts5-search.test.ts` (lines 137-160)
+- `tests/integration/ci/database-population.test.ts` (lines 206-234)
+- Both updated to match corrected SQL logic with case-insensitive comparison
+- Tests now accurately validate production search behavior
+
+#### Impact
+
+**Search Quality:**
+- ✅ Exact matches now always rank first (webhook, http, code, etc.)
+- ✅ Case-insensitive matching works correctly (Webhook = webhook = WEBHOOK)
+- ✅ Better user experience - predictable search results
+- ✅ SQL query more efficient (correct ordering at database level)
+
+**Performance:**
+- Same or better performance (less JavaScript sorting needed)
+- Database does the heavy lifting with correct ORDER BY
+- JavaScript sorting still provides additional relevance refinement
+
+**Testing:**
+- All 705 tests passing (703 passed + 2 fixed)
+- Comprehensive testing by n8n-mcp-tester agent
+- Code review approved with minor optimization suggestions for future
+
+**Verified Search Results:**
+- "webhook" → nodes-base.webhook (1st)
+- "http" → nodes-base.httpRequest (1st)
+- "code" → nodes-base.code (1st)
+- "slack" → nodes-base.slack (1st)
+- All case variations work correctly (WEBHOOK, Webhook, webhook)
+
 ## [2.20.6] - 2025-10-21
 
 ### 🐛 Bug Fixes