fix: truncate tool name

[urmauur]

Describe Your Changes

This pull request includes a minor change to the DropdownToolsAvailable component in DropdownToolsAvailable.tsx. The change updates the CSS class for the heading element to improve text clamping behavior.

• web-app/src/containers/DropdownToolsAvailable.tsx: Modified the h4 element's class from truncate to line-clamp-1 to enhance text clamping for better display of tool names.

Fixes Issues

• Closes #
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Update CSS class in DropdownToolsAvailable.tsx for better text clamping and remove unused class in hub.tsx.

• CSS Update:
  • In DropdownToolsAvailable.tsx, changed h4 class from truncate to line-clamp-1 for better text clamping of tool names.
• Misc:
  • Removed unused border-b border-main-view-fg/5 class in hub.tsx.

^{This description was created by for f316b74. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 92d8367 in 37 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/containers/DropdownToolsAvailable.tsx:123

• Draft comment:
  Replacing 'truncate' with 'line-clamp-1' improves one-line clamping, but ensure that Tailwind’s line clamp plugin is enabled in your configuration so that the utility works as expected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment suggests a specific code change and provides a reason for it, which is useful. However, it also includes a request to ensure that a configuration is set, which violates the rule against asking the PR author to ensure something is configured correctly. The first part of the comment is useful, but the second part is not allowed.

Workflow ID: wflow_60tAGwRJLNcMU0qN

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed f316b74 in 1 minute and 43 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/routes/hub.tsx:246

• Draft comment:
  The removal of the border classes (i.e. border-b border-main-view-fg/5) changes the visual separation of the header. Ensure this design change is intentional. Also, there’s an extra space between py-3 and h-10 that can be cleaned up.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The main part of the comment is about UI styling changes (border removal). Our rules explicitly state "Do NOT comment on any pure frontend UI or styling changes, only logic. Assume that if the author changed the UI, they did it correctly." The extra space observation is extremely minor and not worth a comment. The extra space in className could accumulate over time if left unchecked across the codebase. And removing visual separation could impact UX. While those concerns are valid, our rules are clear that we trust the author on UI changes. The extra space is too minor to warrant a comment. This comment should be removed as it primarily focuses on UI styling changes which we're told to ignore, and points out an insignificant formatting issue.

Workflow ID: wflow_eMMzHJ1cjqaciE8r

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}