Do we want the container monitor?

[ChrisJBurns]

When you run vt run ... it starts the container but also monitors it in the same shell, and to run vt list to see if the container is running, you have to open a new shell session. Is it worth making this flag driven? Or just removing it and just stopping the program once the container has been started successfully?

Example:

> ./vibetool run --transport sse --name postgres-mcp --port 5432 mcp/postgres:latest -- "postgresql://host.docker.internal:5432/mydb"
Creating container postgres-mcp from image mcp/postgres:latest...
Container created with ID: 2e2bc9029d5c5ae90ca8ed5090068a17a55059215cda0949847daa8aa8b6f1b2
Starting container postgres-mcp...
Setting up sse transport...
Starting sse transport...
MCP server postgres-mcp started successfully
> ./vibetool list
CONTAINER ID   NAME           IMAGE                 STATE     TRANSPORT   PORT
2e2bc9029d5c   postgres-mcp   mcp/postgres:latest   running   sse         5432

[JAORMX]

So, in the long run I want vt run to detach. It only doesn't detach now because I need to debug the protocol and proxy.