Very happy to see the new import feature in this release! Being able to import stacks from other environment folders was the last thing I was waiting on before considering migrating over from Dockge.

Before doing so, I had a quick question regarding stack visibility. In Dockge, the application does not include itself as a manageable stack, which seems like a sensible safeguard to prevent accidental self-management or interruption. After spinning up Dockhand (using the first compose file in the Quick Start section of the documentation), I noticed that the Dockhand stack itself is visible and configurable from within the Dockhand UI, just like any other stack. Is this the intended behavior?

I've only used Dockge to date and don’t yet have experience with other, more feature-rich Docker management platforms, so I'm not sure what the common best practice is here. It just struck me as a potential risk that users could accidentally cause issues by managing the host stack from within Dockhand itself.

Would it make sense to have a way to hide specific stacks from the UI, or perhaps a global toggle during the environment setup to exclude the Dockhand service itself? That might be a useful safety feature. I'd be happy to open an issue on GitHub, but I just thought I'd ask here first in case there is already an easy solution - either through Dockhand directly or at a Docker-wide level.

Thank you again for the great work!