fix: store every node of multi-node community packages (czlonkowski#967) (czlonkowski#969)

* fix: store every node of multi-node community packages (czlonkowski#967)

The npm sync kept one row per package - the first parseable n8n.nodes
manifest entry - so multi-node packages lost the rest (pdf-toolkit
declares 18 nodes, the DB held one). One row per manifest entry now,
sharing package-level README and AI summary; per-node trigger/webhook
detection from the node's own name; the stale-row self-heal becomes a
set-diff over unverified community rows only; save-prune-seed runs in
a transaction; an unreadable package.json skips the package untouched
instead of collapsing it to a single heuristic row; shared summaries
are prompted package-scoped; statistics separate packages from rows.

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

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

* chore: refresh bundled DB with multi-node package rows

npm run fetch:community on the new sync: 60 npm packages now yield 133
node rows (was one row each), 1,569 community nodes total. Recovered
siblings inherit the package README and AI summary; one stale row
removed (no longer declared by its package).

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

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

* fix: report a truthful count from deleteStaleCommunityNodes

The method returned result.changes, which the sql.js adapter hard-codes
to 1 regardless of rows deleted. One WHERE string now feeds both a
SELECT COUNT(*) and the DELETE so the reported count cannot drift from
what is removed, and nodesRemoved is re-coupled to that value instead
of the service-side snapshot.

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

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

---------

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

Author: czlonkowski

CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.67.2] - 2026-07-29
+
+### Fixed
+
+- **The community npm sync stores every node a package ships (#967).** The sync stored exactly one row per npm package — the first parseable `n8n.nodes` manifest entry — so multi-node packages lost the rest: `@custom-js/n8n-nodes-pdf-toolkit` declares 18 nodes and the database held one. The sync now stores one row per manifest entry, sharing the package's README and AI summary across siblings, with trigger/webhook detection reading each node's own name instead of the package name (the package's trigger node was previously invisible, and a `*-trigger` package name used to mark every sibling a trigger). The v2.66.3 stale-row self-heal becomes a set-diff that still touches only unverified community rows, the save-prune-seed sequence runs in one transaction, and a package whose package.json cannot be fetched is skipped untouched instead of collapsing to a single heuristic row — a transient registry failure previously became data loss. Shared AI summaries are prompted with the package's node list rather than one sibling's identity, fetch statistics report packages and node rows separately, and the bundled database is refreshed with the recovered sibling nodes.
+
 ## [2.67.1] - 2026-07-29
 
 ### Changed

data/nodes.db

@@ -1,6 +1,6 @@
 {
   "name": "n8n-mcp",
-  "version": "2.67.1",
+  "version": "2.67.2",
   "description": "Integration between n8n workflow automation and Model Context Protocol (MCP)",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",