[nealrichardson]

Fixes #59. Fixes #61.

#61: installed with-connect prints a traceback

The installed command called main() directly, which skipped the code that turns errors into a short message. main() is now the only entry point: it runs the workflow (renamed to run()), prints RuntimeErrors as a one-line Error: ..., and exits with code 1. Both the console script (pyproject.toml) and python main.py call main().

#59: Docker errors print a traceback

These Docker failures are reported as one-line errors:

• Docker unreachable (for example, the daemon isn't running): Could not connect to Docker. Is it running? ...
• Container create fails, including client timeouts and 400 Bad Requests
• Container start fails (for example, the port is already allocated). The container is created and started in separate steps, so a container that fails to start is removed.
• --stop fails with a Docker error other than "not found"

If stopping the container fails during cleanup after a run, with-connect prints a warning and keeps the original error or the command's exit code.

Tests

Added unit tests for each failure path, plus a check that the console script points at main:main. They're also registered in the __main__ block so uv run test_main.py in CI runs them. I checked the installed command by hand against real Docker for --stop without a container ID, an unreachable DOCKER_HOST, and a port already in use, which left no container behind.

The branch is rebased onto main, including #69, #71, #74, and #75.

🤖 Generated with Claude Code

[nealrichardson]

I don't like how we have a function called main() (and see its docstring), but __main__ calls cli(). Sounds like we need some renaming at least, possibly refactoring.

[nealrichardson]

Renamed so main() is the entry point (console script, python main.py, and the error reporting), and the workflow it calls is run(). The console script is main:main again, the same as on main. (2f9b025)