fix: ensure proper delivery of stop signal in scheduler and improve readability of MemoryStore tests

Author: nassor

src/scheduler.rs

@@ -392,7 +392,8 @@ where
         // Send stop signal — use send().await to ensure delivery for critical control-plane command.
         // This is safe because stop signals are rare and waiting for queue space is acceptable.
         if let Some(tx) = self.command_tx.read().await.as_ref() {
-            tx.send(SchedulerCommand::Stop).await
+            tx.send(SchedulerCommand::Stop)
+                .await
                 .map_err(|e| CanoError::Workflow(format!("Failed to send stop: {}", e)))?;
         } else {
             return Err(CanoError::Workflow(

src/store/memory.rs

@@ -403,8 +403,13 @@ mod tests {
         assert!(result.is_err());
 
         // Verify the original value is still in the store (non-destructive error)
-        let retrieved: String = store.get(key).expect("Value should still exist after append error");
-        assert_eq!(retrieved, original_value, "Original value should be preserved after type mismatch");
+        let retrieved: String = store
+            .get(key)
+            .expect("Value should still exist after append error");
+        assert_eq!(
+            retrieved, original_value,
+            "Original value should be preserved after type mismatch"
+        );
     }
 
     #[test]