Greptile Summary

This PR adds a 30-second AbortSignal.timeout to the central fetchGraphJson() wrapper in the MS Teams extension, preventing indefinite hangs when the Microsoft Graph API is slow or unresponsive. The change is small, well-scoped, and correctly applies to all callers (listTeamsByName, listChannelsForTeam, etc.) through the single wrapper.

Key observations:

• The fetch call is now wrapped in a try/catch that re-throws with a consistent "Graph … request failed" message and preserves the original error via { cause: err } — a good pattern.
• The AbortSignal.timeout() static method is available in Node.js ≥ 17.3 / modern browsers; since TypeScript compilation reportedly succeeds, the project's runtime targets are assumed to support it.
• Minor inconsistency: the res.json() call on the happy path (line 58) sits outside the try/catch, so a body-parse failure will bubble up as a raw SyntaxError rather than the wrapped format used for network errors — worth aligning for consistency.

Confidence Score: 4/5

• This PR is safe to merge — it adds a defensive timeout with no functional regression risk.
• The change is minimal (one file, ~10 lines added) and solves a real problem (indefinite hang on slow Graph API calls). The only minor gap is that the res.json() body read on the success path is outside the new try/catch, leaving a slightly inconsistent error format for parse failures. This does not affect correctness or stability.
• No files require special attention beyond the minor res.json() error-wrapping inconsistency noted in extensions/msteams/src/graph.ts.

This is a comment left during a code review.
Path: extensions/msteams/src/graph.ts
Line: 58

Comment:
**`res.json()` not covered by try/catch**

The `res.json()` call on the success path sits outside the new try/catch block. If the response body is malformed or the stream is interrupted, the resulting `SyntaxError` (or other rejection) will bubble up un-wrapped, bypassing the consistent `"Graph … request failed"` error format that was just introduced for network-level failures.

Consider wrapping the body read as well for consistent error handling:

```suggestion
  return (await res.json().catch((err: unknown) => {
    throw new Error(
      `Graph ${params.path} response parse failed: ${err instanceof Error ? err.message : String(err)}`,
      { cause: err },
    );
  })) as T;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: 51409b8}