memoryd: the Honcho workspaces it reads, with their clients and labels

Co-Authored-By: ornith-1.5-35b-a3b <agent@wntrmute.dev>

crates/memoryd/src/honcho/client.rs

@@ -19,8 +19,8 @@ use crate::honcho::naming::HonchoSession;
 /// How long a connection may take, and a read may go without a byte.
 pub const CONNECT: Duration = Duration::from_secs(5);
 pub const READ: Duration = Duration::from_secs(30);
-/// A chat's read: a non-streamed chat sends nothing until it is done (M5c-2's `ask_memory`).
-pub const CHAT_READ: Duration = Duration::from_secs(180);
+/// A chat's read: a non-streamed chat sends nothing until it is done (M5c spec, section 9).
+pub const CHAT_READ: Duration = Duration::from_secs(150);
 
 /// The timeouts a client is built with. Tests shorten them.
 #[derive(Debug, Clone, Copy, PartialEq, Eq)]
@@ -176,7 +176,7 @@ fn created<T>(result: Result<T, Error>) -> Result<(), HonchoError> {
 }
 
 /// One workspace's client: no `roncho.toml` read, the timeouts given, the key when there is one.
-fn client(
+pub(crate) fn client(
     url: &str,
     workspace: &str,
     key: Option<&secrets::Secret>,
@@ -197,7 +197,7 @@ fn client(
 }
 
 /// The key named `name` in `[secrets]`, if one is configured, read now.
-fn key(
+pub(crate) fn key(
     config: &HonchoConfig,
     name: &str,
     env: &dyn Fn(&str) -> Option<OsString>,