fix(editor): Remove unused $style.insightsTab class binding

[cubic-dev-ai]

Summary

• Removed unused $style.insightsTab class binding from InsightsSummary.vue

The :class="$style.insightsTab" binding on the N8nTooltip component referenced a CSS class that was never defined in the component's module styles. This binding had no effect and has been removed.

Test plan

• Verify the Insights tab renders correctly without visual changes
• Confirm no console warnings about undefined CSS module classes

🤖 Generated with Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

cubic-dev-ai[bot] seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cubic-dev-ai]

No issues found across 1 file

[codecov]

Bundle Report

Changes will increase total bundle size by 135 bytes (0.0%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
editor-ui-esm	40.94MB	135 bytes (0.0%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: editor-ui-esm

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
assets/SettingsApiView-*.js	220 bytes	13.78kB	1.62%
assets/InsightsSummary-*.js	-85 bytes	8.37kB	-1.0%

Files in assets/InsightsSummary-*.js:

• ./src/features/execution/insights/components/InsightsSummary.vue → Total Size: 356 bytes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[n8n-assistant]

Hey @cubic-dev-ai[bot],

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email nodes@n8n.io and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-6566". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.