Previously, the CI test only warned when templates were missing but
always passed. This allowed the templates database to be lost without
failing CI. Now the test will fail if templates are empty or below
the expected count of 2500.
Conceived by Romuald Członkowski - https://www.aiadvisors.pl/en🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* 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>
Fixes production search failures where 69% of user searches returned zero
results for critical nodes (webhook, merge, split batch) despite nodes
existing in database.
Root Cause:
- schema.sql missing nodes_fts FTS5 virtual table
- No validation to detect empty database or missing FTS5
- rebuild.ts used schema without search index
- Result: 9 of 13 searches failed in production
Changes:
1. Schema Updates (src/database/schema.sql):
- Added nodes_fts FTS5 virtual table with full-text indexing
- Added INSERT/UPDATE/DELETE triggers for auto-sync
- Indexes: node_type, display_name, description, documentation, operations
2. Database Validation (src/scripts/rebuild.ts):
- Added empty database detection (fails if zero nodes)
- Added FTS5 existence and synchronization validation
- Added searchability tests for critical nodes
- Added minimum node count check (500+)
3. Runtime Health Checks (src/mcp/server.ts):
- Database health validation on first access
- Detects empty database with clear error
- Detects missing FTS5 with actionable warning
4. Test Suite (53 new tests):
- tests/integration/database/node-fts5-search.test.ts (14 tests)
- tests/integration/database/empty-database.test.ts (14 tests)
- tests/integration/ci/database-population.test.ts (25 tests)
5. Database Rebuild:
- data/nodes.db rebuilt with FTS5 index
- 535 nodes fully synchronized with FTS5
Impact:
- ✅ All critical searches now work (webhook, merge, split, code, http)
- ✅ FTS5 provides fast ranked search (< 100ms)
- ✅ Clear error messages if database empty
- ✅ CI validates committed database integrity
- ✅ Runtime health checks detect issues immediately
Performance:
- FTS5 search: < 100ms for typical queries
- LIKE fallback: < 500ms (unchanged, still functional)
Testing: LIKE search investigation revealed it was perfectly functional,
only failed because database was empty. No changes needed.
Related: Issue #296 Part 2 (Part 1: v2.18.4 fixed adapter bypass)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
