Very Poorly Planned UI Updates

What is going on with Comfyui? I'm about to give up on it. I spend 9/10th of my day fixing problems that result from "upgrades". My productivity has been severely hampered by the latest changes. The change-control process is out of control (and that's the sort of thing I do for a living, so take what I'm saying seriously).

1. Migration to new Comfyui-Manager.

- The entire bar with the new unrecognizable icon for the Manager, along with other tools like CPU, RAM, GPU stats, K-monitor and Run button now appears ON TOP OF MY WORKFLOW. This makes it even more difficult to see the workflow., This "toolbar" should exist above the canvas, not in it!
- I see no way to revert back to the old Manager because the portable version has no Server-Config tab to get to the settings that allow you to get back to the "sane" version of Manager. Right now, I can't do anything in Manager except look at extensions that are available. So, all of the other features of the Manager are completely gone. Do you realize the legacy Manager did way more than just "manage extensions".
- Installing extensions from Manager simply doesn't work. It just sits there with a spinning wheel. Its non-functional, yet released!

2. Nodes 2.0. Users need to be very weary of using it right now. It's beyond buggy and if you peek at it, you'll completely mess up your workflows when you come back to "sane" nodes, causing hours of additional work to get nodes positioned correctly.

Absolutely abhorrent change control processes here. Getting something to market as quickly as possible is important, but it needs to work and it needs to allow users to go back to the prior version. ALL OF THIS DEVELOPMENT HAS BEEN PREMATURELY RELEASED AND HAS CAUSED COUNTLESS HOURS OF UNPRODUCTIVE TIME TO THE USER COMMUNITY.

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-7772-Very-Poorly-Planned-UI-Updates-2d66d73d3650814d83e9eb4b51ecf530) by [Unito](https://www.unito.io)

No source file, test, or entry point is named. Start by reproducing the reported toolbar overlap, Manager installation spinner, portable-version settings limitation, and Nodes 2.0 workflow disruption, then separate them into focused reports with reproducible steps. Done would require agreed scope and verification for each specific failure.

Written by the indexing model from the issue text.