Split protocol and leaf surfaces into crates

Move the protocol runtime into unshell-protocol and remote shell leaf code into unshell-leaves so endpoint and TUI roles can compile independently without circular dependencies.

examples/protocol/remote_shell_endpoint.rs

@@ -4,15 +4,13 @@
 //! example over TCP, feeds inbound frames into the `ProcedureRuntime`, and flushes any resulting
 //! protocol frames back to the controller.
 
-#[path = "../../src/leaf/remote_shell/mod.rs"]
-mod remote_shell;
-
 use std::error::Error;
 use std::net::TcpStream;
 use std::sync::mpsc::RecvTimeoutError;
 use std::time::Duration;
 
 use unshell::protocol::tree::Ingress;
+use unshell_leaves::remote_shell;
 
 fn main() -> Result<(), Box<dyn Error>> {
     let mut stream = TcpStream::connect(remote_shell::LISTEN_ADDR)?;

examples/protocol/remote_shell_receive.rs

@@ -3,13 +3,11 @@
 //! This binary listens for the endpoint example, opens one remote shell session, sends a few
 //! commands, and prints returned hook data until the shell closes.
 
-#[path = "../../src/leaf/remote_shell/mod.rs"]
-mod remote_shell;
-
 use std::error::Error;
 use std::net::TcpListener;
 
 use unshell::protocol::tree::{Endpoint, EndpointOutcome, Ingress, LocalEvent};
+use unshell_leaves::remote_shell;
 
 fn main() -> Result<(), Box<dyn Error>> {
     let listener = TcpListener::bind(remote_shell::LISTEN_ADDR)?;

examples/protocol/remote_shell_single_endpoint.rs

@@ -5,13 +5,11 @@
 //! a shell process, so it is the easiest place to see how the endpoint and leaf metadata fit
 //! together.
 
-#[path = "../../src/leaf/remote_shell/mod.rs"]
-mod remote_shell;
-
 use std::error::Error;
 
 use unshell::protocol::tree::{EndpointOutcome, LocalEvent, ProtocolEndpoint};
 use unshell::protocol::{INTROSPECTION_PROCEDURE_ID, LeafIntrospection};
+use unshell_leaves::remote_shell;
 
 fn main() -> Result<(), Box<dyn Error>> {
     let mut endpoint = ProtocolEndpoint::new(