chore: placement menu leftpanel and ux create add projects

[urmauur]

Describe Your Changes

Improved project creation and navigation UX with enhanced visual consistency across the
application.

Key Changes:

• Auto-navigation after project creation: When creating a new project from either the left
  panel or project page, users are now automatically navigated to the newly created project
• Visual consistency improvements: Fixed styling inconsistencies for thread menu dots in
  project view to match the main view theme
• Enhanced left panel layout: Improved secondary menu positioning and spacing for better
  visual hierarchy

Technical Details

• Modified useThreadManagement.ts:37 to return the newly created folder object from
  addFolder()
• Updated project creation handlers in LeftPanel.tsx:219 and project/index.tsx:63 to
  navigate to new projects automatically
• Fixed thread list menu dot styling in ThreadList.tsx:188 to use appropriate colors in
  project context
• Reorganized left panel menu structure with proper secondary menu positioning

Test Plan

• Create a new project from the left panel and verify automatic navigation
• Create a new project from the project page and verify automatic navigation
• Verify thread menu dots display correctly in both main and project views
• Check left panel layout and menu positioning

This improves the user experience by eliminating the extra step of manually navigating to
newly created projects while maintaining visual consistency across different views.

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

Enhances project creation UX with auto-navigation to new projects and improved visual consistency in menus and thread styling.

• Behavior:
  • Auto-navigation to new projects after creation in LeftPanel.tsx:219 and project/index.tsx:63.
  • Thread menu dots styling updated in ThreadList.tsx:188 for project context.
• Functions:
  • addFolder() in useThreadManagement.ts now returns the new folder object.
• Layout:
  • Improved secondary menu positioning in LeftPanel.tsx for better visual hierarchy.

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

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to b4df56e in 1 minute and 32 seconds. Click for details.

• Reviewed 165 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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/ThreadList.tsx:328

• Draft comment:
  Avoid using the array index as the key for SortableItem; use thread.id instead to ensure stable identification during reordering.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

2. web-app/src/routes/project/index.tsx:63

• Draft comment:
  Use a route constant (e.g. route.project) instead of hardcoding the string '/project/$projectId' for navigation. This change promotes maintainability and consistency.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The comment appears to be correct in principle - using route constants is generally better than hardcoded strings. However, looking at the Route definition (L24), it's defined as '/project/' without the $projectId parameter. I'm not certain if Route.project would actually work as a direct replacement since the route definition doesn't match the usage pattern. Without seeing more of the routing setup, I can't be 100% sure this suggestion is correct. The route constant defined in the file doesn't include the $projectId parameter, so the suggested change might not work. We also don't know if there are other route constants defined elsewhere that would be more appropriate. While using route constants is a good practice, we need to be certain that the suggested constant actually matches the required route pattern with parameters. Given the uncertainty about the routing setup and the mismatch between the defined Route constant and the required route pattern, we should not keep this comment.

Workflow ID: wflow_by9DDQrVuthWBfTV

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

[louis-jan]

LGTM

[github-actions]

Barecheck - Code coverage report

Total: 29.68%

Your code coverage diff: 0.04% ▴

Uncovered files and lines

File	Lines
web-app/src/containers/LeftPanel.tsx	105-108, 120, 123-127, 130-141, 187-189, 203-205, 208-213, 216-219, 221-228, 233, 247-249, 251-259, 269, 272-273, 277, 296, 309-315, 317-318, 327-330, 332-348, 350-351, 353, 358-359, 363-367, 369, 371, 373, 381-382, 409-423, 425-431, 433-437, 439, 441-452, 454-470, 472-479, 481-488, 490, 492-495, 502-530, 532-547, 549-550, 554-566, 568-581, 585-595, 635, 658-663
web-app/src/containers/ThreadList.tsx	48-50, 53-61, 63-64, 66-80, 82-88, 90-96, 98-103, 105, 108-109, 111-118, 120-125, 127-129, 131-133, 135-140, 142-161, 163-167, 169-175, 177, 179-183, 185-204, 206-208, 210-214, 216-218, 220-225, 227-235, 237-238, 240-248, 250-255, 257-262, 264-274, 276-279, 281-293, 295, 308, 329
web-app/src/hooks/useThreadManagement.ts	28-29, 32-41, 44-51, 55-58, 60-67, 69-72, 75-76
web-app/src/routes/project/index.tsx	1-2, 4-6, 8-10, 18-20, 22, 24-26, 28-30, 32-44, 46-49, 51-57, 59-63, 65-72, 74-76, 79-85, 87-97, 99-110, 112-128, 130-136, 138-141, 143-155, 157-179, 181, 183-187, 189-192, 194, 196-202, 204-212, 214-220, 223-229, 231, 233-234, 236-251, 253