docs(plugin)!: update for probitas-client breaking changes

Response body accessors changed from methods to properties in
probitas-client PR #65. Updated all examples to use property syntax
(json, data, text, etc.) and recommend dot-notation for keyPath
over array syntax in common cases.

BREAKING CHANGE: Plugin version bumped to 0.2.0 to reflect
probitas-client API changes. Users must update response accessor
syntax from method calls to property access.

Author: lambdalisue

plugins/probitas/.claude-plugin/plugin.json

@@ -1,12 +1,17 @@
 {
   "name": "probitas",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Probitas scenario testing framework integration for Claude Code",
   "author": {
     "name": "jsr-probitas",
     "url": "https://github.com/jsr-probitas"
   },
   "repository": "https://github.com/jsr-probitas/claude-plugins",
-  "keywords": ["testing", "integration-testing", "scenario", "deno"],
+  "keywords": [
+    "testing",
+    "integration-testing",
+    "scenario",
+    "deno"
+  ],
   "license": "MIT"
 }

plugins/probitas/agents/scenario-writer.md

@@ -18,7 +18,7 @@ export default scenario("Test name", { tags: ["..."] })
   .step("Step name", async (ctx) => {
     const res = await ctx.resources.http.post("/endpoint", { body: {} });
     expect(res).toBeOk().toHaveStatus(200);
-    return res.json<{ id: number }>()!;
+    return res.json as { id: number } | null;
   })
   .build();
 ```
@@ -119,36 +119,41 @@ expect(res)
   .toHaveDataMatching({ statusCode: 0 })
   .toHaveDataProperty("metadata");
 
-return res.data<{ metadata?: Record<string, unknown> }>()!;
+return res.data as { metadata?: Record<string, unknown> } | null;
 ```
 
-**For nested property paths, use array syntax:**
+**For nested property paths, use dot-notation strings:**
 
 ```typescript
-// ✅ CORRECT - array syntax for nested paths
+// ✅ CORRECT - dot-notation for nested paths
 expect(res)
   .toBeOk()
   .toHaveDataProperty("Metadata")
-  .not.toHaveDataProperty(["Metadata", "x-internal-token"]);
+  .not.toHaveDataProperty("Metadata.x-internal-token");
 ```
 
+**Use array syntax only when property names contain dots:**
+
 ```typescript
-// ❌ WRONG - dot-notation for nested paths (NOT SUPPORTED)
-expect(res).not.toHaveDataProperty("Metadata.x-internal-token");
+// ✅ CORRECT - array syntax when property name contains "."
+expect(res)
+  .toBeOk()
+  .not.toHaveDataProperty(["api.internal", "token"]); // "api.internal" is the actual property name
+```
 
+```typescript
 // ❌ WRONG - split expect calls
 expect(res).toHaveDataMatching({ statusCode: 0 });
-const data = res.data<...>()!;  // Don't extract between expects!
+const data = res.data as ...;  // Don't extract between expects!
 expect(res).toHaveDataProperty("metadata");
 
 // ❌ WRONG - separate expect for .not
 expect(res).toHaveDataProperty("metadata");
-expect(res).not.toHaveDataProperty(["Metadata", "x-internal-token"]);  // Chain it!
+expect(res).not.toHaveDataProperty("Metadata.x-internal-token");  // Chain it!
 ```
 
 **DO NOT GUESS API PATTERNS:**
 
-- DO NOT infer dot-notation paths (e.g., `"metadata.field"`) unless documented
 - DO NOT assume array index syntax unless documented
 - DO NOT guess method signatures or options
 - If unsure, fetch the specific API docs from links below
@@ -180,10 +185,10 @@ client.http.createHttpClient({
   };
 })
 
-// ❌ Unnecessary type casting
-const data = res.json() as { id: number };
-// ✅ CORRECT
+// ❌ Old syntax (deprecated)
 const data = res.json<{ id: number }>()!;
+// ✅ CORRECT - json is now a property returning any
+const data = res.json as { id: number } | null;
 ```
 
 ### Best Practices