fix(docs): correct stale source paths in code comments

Update two inline comments that referenced the old `adapters/remote` path to point to the current `crates/tinymemory-remote` location, ensuring the documentation accurately reflects the project's directory structure.

Auto-committed-on: dragonfly
Co-authored-by: Medulla <medulla@tinyhumans.ai>

Author: senamakel

crates/tinymemory-api/src/mandatory/mod.rs

@@ -78,7 +78,7 @@ pub const SCOPE_UNAPPLIED: &str =
 #[must_use]
 pub fn engine_error(error: anyhow::Error) -> MemoryError {
     // §A4: an adapter that already knows the failure's class attaches a typed
-    // MemoryError as the anyhow payload (adapters/remote/src/common.rs does
+    // MemoryError as the anyhow payload (crates/tinymemory-remote/src/common.rs does
     // for transport and HTTP-status failures). Recover it here instead of
     // flattening everything to Other — this one line is what makes
     // "unauthorized" distinguishable from "unreachable" across every

crates/tinymemory-core/src/store/factories.rs

@@ -359,7 +359,7 @@ pub fn create_memory(
 /// Issue #18 §A3/§A5. Until this existed, `tinymemory-core`'s
 /// [`UnifiedMemory`] was the one storage
 /// implementation in the workspace with no route through the contract: the
-/// TinyCortex adapter binds the bundled engine, `adapters/remote` binds the
+/// TinyCortex adapter binds the bundled engine, `tinymemory-remote` binds the
 /// three hosted services, and core's own SQLite store was reachable only by
 /// naming its concrete type. A host could therefore not treat "the store
 /// tinymemory ships with" as a driver, which is the whole premise of the