fix: use async response status for network request list and detail views

[AlanJie]

Summary

• list_network_requests list and single-request detail views always showed [pending], even after the page finished loading
• Some requests (beacon/analytics) were incorrectly reported as [failed - net::ERR_ABORTED] when they actually returned HTTP 200

Root Cause

getShortDescriptionForRequest and getStatusFromRequest in networkFormatter.ts are synchronous, but Playwright's request.response() is async. The sync path can never obtain the real response status:

// Always returns [pending] — can't access response synchronously
export function getStatusFromRequest(request) {
    const failure = request.failure();
    if (failure) return `[failed - ${failure.errorText}]`;
    return '[pending]';
}

An async version getStatusFromRequestAsync already existed but was never called by the list or detail formatting code.

Fix

1. src/formatters/networkFormatter.ts — Added getShortDescriptionForRequestAsync, which calls the existing getStatusFromRequestAsync
2. src/McpResponse.ts — Updated 3 call sites to use the async versions:
   • Request list loop (in format())
   • Single-request detail status line (in #formatNetworkRequestData())
   • Redirect chain status (in #formatNetworkRequestData())
3. format() and #formatNetworkRequestData() method signatures changed to async

Before / After

Before	After
GET .../api/feed/topstory/recommend ... [pending]	GET .../api/feed/topstory/recommend ... [success - 200]
POST .../za/logs/batch [failed - ERR_ABORTED]	POST .../za/logs/batch [success - 200]
Status: [pending]	Status: [success - 200]

🤖 Generated with Claude Code