channel architecture: wire protocol, daemons, supervisor

Design and implement the channel system for external communications:

- schema/channel.capnp: wire protocol for channel daemons
  (recv with all_new/min_count, send, subscribe, list)
- channels/irc/: standalone IRC daemon crate (consciousness-channel-irc)
- channels/telegram/: standalone Telegram daemon crate
  (consciousness-channel-telegram)
- src/thalamus/channels.rs: client connecting to daemon sockets
- src/thalamus/supervisor.rs: daemon lifecycle with file locking
  for multi-instance safety

Channel daemons listen on ~/.consciousness/channels/*.sock,
configs in *.json5, supervisor discovers and starts them.
IRC/Telegram modules removed from thalamus core — they're
now independent daemons that survive consciousness restarts.

Also: delete standalone tui.rs (moved to consciousness F4/F5),
fix build warnings, add F5 thalamus screen with channel status.

Co-Developed-By: Kent Overstreet <kent.overstreet@linux.dev>

src/cli/misc.rs

@@ -144,14 +144,7 @@ pub fn cmd_search(terms: &[String], pipeline_args: &[String], expand: bool, full
 }
 
 pub fn cmd_status() -> Result<(), String> {
-    // If stdout is a tty and daemon is running, launch TUI
-    if std::io::IsTerminal::is_terminal(&std::io::stdout()) {
-        // Try TUI first — falls back if daemon not running
-        match crate::tui::run_tui() {
-            Ok(()) => return Ok(()),
-            Err(_) => {} // fall through to text output
-        }
-    }
+    // TUI moved to consciousness binary (F4 unconscious screen)
 
     let store = crate::store::Store::load()?;
     let g = store.build_graph();