@yaklabs-ai/plugin-sdk 0.11.0 → 0.12.2

package/dist/kay-agent-testing.js

@@ -126,11 +126,22 @@ function unwired(name) {
     throw new Error(`${name} is not wired in this test double; pass your own handle to exercise it`);
   };
 }
+var NOT_WIRED = async () => ({ ok: false, reason: "unavailable", message: "not wired" });
+var UNWIRED_SURFACE = {
+  isAvailable: async () => false,
+  targets: NOT_WIRED,
+  observe: NOT_WIRED,
+  act: NOT_WIRED,
+  screenshot: NOT_WIRED,
+  open: NOT_WIRED
+};
 function fauxKayAgentCapabilities() {
   return {
     filesystem: {
       readText: unwired("filesystem.readText"),
       writeText: unwired("filesystem.writeText"),
+      readBytes: unwired("filesystem.readBytes"),
+      writeBytes: unwired("filesystem.writeBytes"),
       mkdir: unwired("filesystem.mkdir"),
       readDir: unwired("filesystem.readDir"),
       stat: unwired("filesystem.stat"),
@@ -161,6 +172,9 @@ function fauxKayAgentCapabilities() {
         remove: unwired("whiteboard.remove")
       })
     },
+    // Answers `unavailable` rather than rejecting: the real surfaces report an unavailable
+    // surface as `{ ok: false }`, never a throw. A test driving one overrides this handle.
+    interaction: { browserPane: UNWIRED_SURFACE, desktop: UNWIRED_SURFACE },
     interceptToolCall: () => void 0,
     // The one handle that does NOT refuse on use. `withJev`'s contract is that it always produces
     // the baseline, so a rejecting double would make a plugin's Jev path untestable and teach the