The Rust application must treat a tmux socket and its attachment policy as separate authority. Kwt now puts ordinary managed workspaces on a named server, so a named socket no longer means that a workspace is protected.
Keep the exact mode and socket through inventory, selection, attachment, reconnect, kill, and removal. Open direct worktrees and directory workspaces through kwt. Keep protected endpoints fail-closed. This prevents same-named sessions on default, dedicated, and protected servers from aliasing each other.
Generated with OpenAI Codex
Co-authored-by: OpenAI Codex <noreply@openai.com>
The Rust application now follows KWT's explicit attachment mode and tmux socket instead of treating every named socket as a protected pull-request workspace. This keeps ordinary managed workspaces on KWT's dedicated server without weakening the separate protected-workspace boundary.
Useful manual QA is to open a normal KWT worktree, a registered directory workspace, and a protected pull-request import on one WSL host, then navigate away and reconnect to each presentation.