Close console core implementation threads - mark interactive console, WebSocket, dev/game console streaming as complete

OPEN_THREADS.md

@@ -4,36 +4,40 @@ This document tracks **known open questions and deferred decisions**.
 
 ---
 
-## High Priority
+## Closed Threads
 
-### Console Development (Next Phase)
-
-#### Planned Order
-1. Read-only console output
-2. Interactive input (PTY / stdin)
-3. Permissions & safety controls
-
-#### Known Constraints
-- Console state is ephemeral
-- No persistence of logs
-- No agent push yet (polling only)
-
-#### Architecture Direction
-- Agent owns PTY
-- API brokers WebSocket sessions
-- Portal renders terminal (xterm.js)
-
-#### Explicitly Deferred
-- Proxmox-based live status polling
-- Agent push model
-- Multi-viewer consoles
+- ✅ Interactive console (PTY-backed, bidirectional)
+- ✅ WebSocket stability issues
+- ✅ Dev server CLI access
+- ✅ Game server console streaming
 
 ---
 
+## Still Open
+
+### Console UX Polish
+- Frontend presentation refinement
+- xterm.js-style terminal UI
+- Responsive layout optimization
+
+### Console Permissions & Security
+- RBAC for console access
+- Audit logging of console commands
+- Session timeout policies
+
+### Console Features (Optional)
+- PTY window size propagation (resize handling)
+- Command history
+- Multi-viewer support
+
+---
+
+## High Priority
+
 ### Server Detail / System View
 - Define System View layout
 - Decide runtime vs metadata sections
-- Determine console availability per server type (GAME vs DEV)
+- Integrate console as primary action
 
 ---