Community nodes now checked for missing data lineage

When community node developers forget to include the pairedItem property on data returned from their execute() methods, downstream nodes lose the ability to trace where that data came from. Expressions like $('NodeName').item silently fail, and workflow authors are left debugging mysterious empty results with no clue why.

A new ESLint rule now catches this automatically during development. The rule scans .node.ts files for INodeType classes, flags any object literals with a json property but no pairedItem inside execute() methods, and points developers directly to the fix. It smartly skips cases where pairing is handled automatically via constructExecutionMetaData() or already present through spread elements.

The rule is enabled by default in the recommended community nodes ESLint configuration, eliminating a review bottleneck that appeared across most community node submissions. Developers get immediate, actionable feedback instead of waiting for manual review cycles.