docs(skill): complete API response refs + note network assertions cover made calls

- SKILL.md "Calling APIs directly" now shows the full reference set
  ({{name.status}}, {{name.response_body}}, {{name.response_body.<field>}}).
- Network assertions doc + cookbook §3.2 + kiro Network row now note that
  network assertions also cover API calls you make directly in an objective,
  not just the requests the page makes on its own.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: shravan-lambdatest

.agents/skills/kane-cli/SKILL.md

@@ -228,7 +228,7 @@ The agent can make API calls itself — not just observe the page's traffic. Phr
  assert {{login.status}} is 200"
 ```
 
-Reference the saved response as `{{login.status}}` and `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar (curl, chaining, direct-call vs DevTools/Network) is in `references/objectives-cookbook.md` §3.5.
+Reference the saved response as `{{login.status}}`, `{{login.response_body}}`, or `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar in `references/objectives-cookbook.md` §3.5.
 
 ### Chaining
 

.agents/skills/kane-cli/references/objectives-cookbook.md

@@ -81,6 +81,8 @@ Five subdomains. Each one is the right choice when the data you care about lives
 
 The agent captures every HTTP request/response per step. **Resets each step** — assert on traffic in the same step it happens (or extract and carry forward).
 
+These assertions also cover API calls **you** make directly in an objective (§3.5), not just the requests the page makes on its own — the agent records its own calls and you query them with the same fields below.
+
 Queryable fields: `method`, `url`, `domain`, `path`, `query_params`, `resource_type`, `request_headers`, `request_body`, `response_status`, `response_headers`, `response_body`, `timing.duration_ms`, `timing.ttfb_ms`, `failed`, `failure_reason`.
 
 ```text

.claude/skills/kane-cli/SKILL.md

@@ -228,7 +228,7 @@ The agent can make API calls itself — not just observe the page's traffic. Phr
  assert {{login.status}} is 200"
 ```
 
-Reference the saved response as `{{login.status}}` and `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar (curl, chaining, direct-call vs DevTools/Network) is in `references/objectives-cookbook.md` §3.5.
+Reference the saved response as `{{login.status}}`, `{{login.response_body}}`, or `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar in `references/objectives-cookbook.md` §3.5.
 
 ### Chaining
 

.claude/skills/kane-cli/references/objectives-cookbook.md

@@ -81,6 +81,8 @@ Five subdomains. Each one is the right choice when the data you care about lives
 
 The agent captures every HTTP request/response per step. **Resets each step** — assert on traffic in the same step it happens (or extract and carry forward).
 
+These assertions also cover API calls **you** make directly in an objective (§3.5), not just the requests the page makes on its own — the agent records its own calls and you query them with the same fields below.
+
 Queryable fields: `method`, `url`, `domain`, `path`, `query_params`, `resource_type`, `request_headers`, `request_body`, `response_status`, `response_headers`, `response_body`, `timing.duration_ms`, `timing.ttfb_ms`, `failed`, `failure_reason`.
 
 ```text

docs/user-guide/features/checkpoints/devtools/network.md

@@ -2,7 +2,7 @@
 
 Network assertions let you verify HTTP traffic — API responses, status codes, headers, response bodies, and request timing.
 
-> To **make** an API call yourself (seed data, hit a backend) rather than observe the page's traffic, see [API Calls](../../api-calls.md).
+> These network assertions also cover API calls **you** make directly in an objective — not just the requests the page makes on its own. The agent records its own calls and you query them with the same fields below. To *make* a call (seed data, hit a backend), see [API Calls](../../api-calls.md).
 
 ## How Capture Works
 

integrations/kiro-powers/steering/kane-cli-run.md

@@ -116,7 +116,7 @@ Five domains. Each captures data the user cannot see on screen. The agent picks
 
 | Subdomain | Captures | Scope | Common phrasing |
 |---|---|---|---|
-| **Network** | HTTP requests/responses — status codes, headers, response bodies, timing | Resets each step | "no API calls returned 5xx", "the POST /api/login returned 200", "all API responses completed under 2 seconds" |
+| **Network** | HTTP requests/responses, incl. API calls you make directly — status codes, headers, response bodies, timing | Resets each step | "no API calls returned 5xx", "the POST /api/login returned 200", "all API responses completed under 2 seconds" |
 | **Console** | `console.log/warn/error/info/debug` + uncaught JS exceptions | Resets each step. Top frame only | "no console errors", "no uncaught JS exceptions", "console contains '…'" |
 | **Performance** | Core Web Vitals — LCP, CLS, INP, FCP, TTFB | Per-navigation, point-in-time | "page LCP is under 2500ms", "CLS is below 0.1", "TTFB under 800ms" |
 | **Cookies** | All cookies including `httpOnly` — name, value, flags | Point-in-time, persists across steps | "a cookie named 'session_id' exists", "the session cookie is httpOnly", "no cookies without the Secure flag" |

skill-installer/skills/SKILL.md

@@ -228,7 +228,7 @@ The agent can make API calls itself — not just observe the page's traffic. Phr
  assert {{login.status}} is 200"
 ```
 
-Reference the saved response as `{{login.status}}` and `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar (curl, chaining, direct-call vs DevTools/Network) is in `references/objectives-cookbook.md` §3.5.
+Reference the saved response as `{{login.status}}`, `{{login.response_body}}`, or `{{login.response_body.<field>}}`; a pasted `curl` works too. Full grammar in `references/objectives-cookbook.md` §3.5.
 
 ### Chaining
 

skill-installer/skills/references/objectives-cookbook.md

@@ -81,6 +81,8 @@ Five subdomains. Each one is the right choice when the data you care about lives
 
 The agent captures every HTTP request/response per step. **Resets each step** — assert on traffic in the same step it happens (or extract and carry forward).
 
+These assertions also cover API calls **you** make directly in an objective (§3.5), not just the requests the page makes on its own — the agent records its own calls and you query them with the same fields below.
+
 Queryable fields: `method`, `url`, `domain`, `path`, `query_params`, `resource_type`, `request_headers`, `request_body`, `response_status`, `response_headers`, `response_body`, `timing.duration_ms`, `timing.ttfb_ms`, `failed`, `failure_reason`.
 
 ```text