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/lib.rs

@@ -48,7 +48,7 @@ pub mod util;
 pub mod cli;
 
 // TUI for memory-search
-pub mod tui;
+// tui moved to src/user/tui/ (consciousness binary screens)
 
 // Thalamus — notification routing and idle management daemon
 pub mod thalamus;
@@ -61,6 +61,10 @@ pub mod memory_capnp {
     include!(concat!(env!("OUT_DIR"), "/schema/memory_capnp.rs"));
 }
 
+pub mod channel_capnp {
+    include!(concat!(env!("OUT_DIR"), "/schema/channel_capnp.rs"));
+}
+
 // Re-exports — all existing crate::X paths keep working
 pub use hippocampus::{
     store, graph, lookups, cursor, query,