outpost cmompose -d (detached) flag keeps terminal attached instead of exiting

[degoke]

Summary

The outpost cmompose command hijacks the terminal and does not return control when run with the -d (detached) flag. It behaves as if it's running in the foreground and requires SIGINT (Ctrl+C) to end the session.

Steps to reproduce

1. Install outpost and ensure outpost cmompose is available in PATH.
2. From a terminal, run: outpost cmompose up -d (or the user's usual compose command via outpost that supports -d).
3. Observe that the terminal remains attached to the process and does not return to the shell prompt.

Expected behavior

• When run with -d the command should start the services in the background and return control to the terminal immediately, similar to how docker compose up -d behaves.

Actual behavior

• The terminal stays attached to the outpost compose session and requires the user to press Ctrl+C or otherwise send SIGINT to stop the session.

Environment (best-effort inference)

• Repository: degoke/outpost
• Command: outpost cmompose up -d (or outpost cmompose ... -d)
• Shell: unknown
• OS: unknown
• outpost version: unknown

Additional details / notes

• This appears to be a bug in how the cmompose command handles the -d / detached flag: it should detach and exit, rather than keep the terminal attached.
• If there are logs, debug output, or code paths that forward STDIN/TTY to child processes, those may be relevant to investigate.

Suggested information to collect (if needed by maintainers)

• The exact outpost version (output of outpost --version).
• The full command used including flags and the directory's compose files.
• Any logs printed by outpost cmompose when starting with -d vs without.

Workaround

• Manually press Ctrl+C to end the session (not ideal).