Refactor socket orchestration to HTTP-first while keeping socket service

[senamakel]

Summary

• Remove app-level socket orchestration wiring by deleting SocketProvider and socket hooks.
• Keep socketService in place for optional reverse-proxy transport, but remove built-in MCP/tool orchestration event handlers.
• Disable socket-driven skills/integration sync (tool:sync, metadata sync emits) and chat:init socket emits.
• Update Intelligence connection handling to no longer depend on socket status.
• Update connection indicator fallback logic and docs in CLAUDE.md to reflect HTTP-first orchestration.

Problem

• The codebase still had backend-pushed socket orchestration paths active (mcp:listTools, mcp:toolCall, tool:sync, Intelligence socket hooks), which conflicts with the desired HTTP chat-only orchestration behavior.
• Socket transport still needs to remain available for reverse-proxy scenarios.

Solution

• Removed the reactive socket orchestration layer (provider + hooks + event emitters) from frontend runtime paths.
• Preserved src/services/socketService.ts as an optional transport service, but stripped orchestration-specific handlers.
• Replaced skills/integration socket sync calls with no-op shims to keep call sites stable without backend-pushed events.
• Simplified Intelligence provider/page connection status handling so the feature is not blocked by socket connectivity.

Testing

• yarn -s compile
• cargo check --manifest-path src-tauri/Cargo.toml
• Other checks run (list commands)
• yarn -s tsc --noEmit
• yarn -s eslint src/App.tsx src/services/socketService.ts src/lib/skills/sync.ts src/lib/intelligence/chatTools.ts src/providers/IntelligenceProvider.tsx src/pages/Intelligence.tsx src/components/ConnectionIndicator.tsx src/lib/gmail/services/metadataSync.ts src/lib/notion/services/metadataSync.ts
• pre-push hooks: prettier --check ., eslint . --ext .ts,.tsx, tsc --noEmit
• Manual validation completed (list scenarios)
• Confirmed no runtime references remain to deleted SocketProvider, useSocket, or useIntelligenceSocket.
• Confirmed frontend no longer contains mcp:listTools, mcp:toolCall, or tool:sync event wiring.

Impact

• Frontend chat/tool orchestration now follows HTTP-first behavior.
• Socket transport remains available in code for future reverse-proxy usage.
• Existing socket-driven integration metadata sync is currently disabled (intentional, temporary behavior).

Breaking Changes

• None
• Yes (describe clearly, including migration steps)

Related

• Issue(s): N/A
• Follow-up PR(s)/TODOs:
• If needed, remove stale Rust-side socket orchestration command surface in a dedicated cleanup PR.