Audit the memory seam's FacadeRevealed bucket into the real upstream ask (#5560)

src/openhuman/agent/tools/remember_preference.rs

@@ -332,7 +332,10 @@ mod tests {
 
     // The read-back goes through the engine handle directly, so its entries
     // carry the engine's category type rather than the contract's.
-    use tinymemory_core::MemoryCategory as EngineMemoryCategory;
+    // The contract's type, not the engine's: `tinymemory-core` re-exports
+    // `tinymemory_api::traits::MemoryCategory` (#18 §A1). Named at its source
+    // so this test does not hold the engine crate in the build (#5560).
+    use tinymemory_api::types::MemoryCategory as EngineMemoryCategory;
 
     fn test_security() -> Arc<SecurityPolicy> {
         Arc::new(SecurityPolicy::default())

src/openhuman/memory/mod.rs

@@ -121,7 +121,13 @@ pub use tinymemory_core::ingestion::{
     IngestionState, IngestionStatusSnapshot, MemoryIngestionConfig, MemoryIngestionRequest,
     MemoryIngestionResult, DEFAULT_MEMORY_EXTRACTION_MODEL,
 };
-pub use tinymemory_core::rpc_models::*;
+// The host's own JSON-RPC request/response shapes. They lived in
+// `tinymemory_core::rpc_models` and were re-exported here by a glob; nothing
+// in `tinymemory` ever named one, so the engine crate was carrying this host's
+// RPC surface (#5560). Same glob, same paths, same wire bytes — the definitions
+// are simply ours now. See `rpc_models`'s module docs.
+pub mod rpc_models;
+pub use rpc_models::*;
 pub use tinymemory_core::traits::{
     Memory, MemoryCategory, MemoryEntry, MemoryTaint, NamespaceSummary, RecallOpts,
 };