Add user-visible LSP status indicators #3085

🎯 Feature Request

Add user-visible LSP status indicators to help users understand when Language Server Protocol servers are active, working, or encountering issues.

📋 Problem Description

Currently, opencode gives no indication when LSP servers are enabled, starting, or working. Users are "flying blind" - they don't know if:

• ruby-lsp actually started when opening a Ruby project
• Why diagnostics aren't appearing (server crash? missing binary?)
• If LSP is working but just finding no issues
• Which LSP servers are active for their current project

This makes debugging language support issues difficult and reduces confidence in the tool.

🚀 Proposed Solution

Phase 1: Minimal Status Indicators (High Impact, Low Risk)

1. Status bar LSP indicator in TUI:

   • LSP: ✓ when servers are healthy
   • LSP: ⚠ when there are issues
   • LSP: ✗ when disconnected
   • LSP: 3 showing diagnostic count

2. Server initialization feedback:

   • Show "Starting ruby-lsp..." during initialization
   • Display errors if servers fail to start

3. Enhanced debug command:

   opencode debug lsp-status

   • Show all active servers, versions, connections
   • Display diagnostic counts and performance metrics
   • Show workspace root detection results

Phase 2: Enhanced Integration

• Progress indicators for long server initialization
• Hover details on LSP status showing active servers
• Diagnostic count badges in status bar

Phase 3: Advanced Features

• LSP performance dashboard
• Server restart capabilities
• Configuration validation

🏗️ Technical Implementation Notes

The codebase is well-prepared for this feature:

• Existing status bar (status/status.go) can be extended with LSP information
• Event system (Bus.publish()) already handles LSP diagnostics
• Log levels (--log-level debug) can control verbosity
• Debug commands already exist (debug/lsp.ts)
• LSP client lifecycle already tracks server states

🎨 UI/UX Considerations

• Normal mode: Minimal status bar indicator
• Debug mode: Detailed server information
• Error states: Always visible (server failed to start, missing binary)
• Follow existing patterns in the TUI status bar
• Use color coding for quick status recognition

📊 Success Criteria

• Users can see at a glance if LSP is working
• Clear feedback when LSP servers fail to start
• Easy way to debug LSP configuration issues
• Professional experience comparable to other editors
• No performance impact on normal operations