BugTraceAI CLI 4.0.20-beta

The installer now offers to open the real TUI when an interactive TUI/both
installation finishes. The launch uses the checkout path, so it works before
the installing terminal has the new btai command directory in PATH.

Global registration distinguishes a command ready now from registration for
new terminals. It provides a current-shell activation command and an immediate
launch path, and clarifies that Docker may still request sudo at startup.

Press Enter at the final prompt to open the workspace, or n to finish.
--launch no skips the prompt; --launch yes launches directly and requires
a terminal. API-only and noninteractive runs do not show the launch prompt.
Quitting the TUI returns cleanly; a launch failure preserves the completed
installation and saved profile. Opening the workspace does not start a scan.

Validation: 54 installer/profile/bootstrap tests, including real-PTY completion
tests and fresh-shell command lookup. The actual installed TUI opened through
the updated completion step with no user command directory in PATH, and
Ctrl+Q returned status 0. Existing Docker/Compose bootstrap fixes are retained.

For an existing installation, update the checkout and reuse its saved profile:

git pull --ff-only
./install.sh --reuse

If the earlier installer stopped before saving a profile, use ./install.sh
instead. An already registered command can be used in the current terminal:

export PATH="$HOME/.local/bin:$PATH"
btai