Fix memory resource limiter implementation using correct Wasmtime API

Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>

Author: Copilot

CHANGELOG.md

@@ -55,6 +55,9 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 - Spell check, link checker, and unused dependency checker to CI workflow ([#116](https://github.com/microsoft/wassette/pull/116))
 - Kubernetes-style resource limits in policy specification with `resources.limits` section supporting CPU ("500m", "1") and memory ("512Mi", "1Gi") formats ([#166](https://github.com/microsoft/wassette/pull/166))
 
+### Fixed
+- Memory resource limiter implementation by properly applying limits to Wasmtime store using the correct `limiter()` API ([#171](https://github.com/microsoft/wassette/pull/171))
+
 ### Changed
 - CLI now supports both server mode (`wassette serve`) and direct management mode for component operations
 - Component load/unload operations can now work independently without requiring a running MCP server

crates/wassette/src/lib.rs

@@ -485,9 +485,14 @@ impl LifecycleManager {
 
         let mut store = Store::new(self.engine.as_ref(), state);
 
-        // Apply memory limits if configured in the policy
-        if let Some(limiter) = resource_limiter {
-            store.set_limiter(limiter);
+        // Apply memory limits if configured in the policy by setting up a limiter closure
+        // that extracts the resource limiter from the WasiState
+        if resource_limiter.is_some() {
+            store.limiter(|state: &mut WassetteWasiState<WasiState>| {
+                // Extract the resource limiter from the inner state
+                // We know it exists because we checked above
+                state.inner.resource_limiter.as_mut().unwrap()
+            });
         }
 
         let instance = component