You are helping me implement a feature in a TypeScript monorepo.

<...feature description...>

Use Context Master tools to propose a realistic implementation plan:
- Start with get-repository-overview to get an architectural overview of the codebase.
- Use get-symbol-context on symbols related to the feature to map blast radius and key call sites.
- Use read-file only if necessary. Use the `includeSource: true` flag when you want to read the source code of a symbol.

Help me understand a bug in our “Invite user” flow.

Question: When a user clicks “Invite” in `InviteMemberDialog`, how does the request propagate to the backend and where do we enforce role checks?

Use get-symbol-context to follow referenced-by edges for `inviteMember` and any auth/permission checks.

Output a concrete call chain (UI -> client -> server -> persistence) and where errors are generated.

I want to refactor `FooBar` to return a structured result instead of throwing:
<...refactor description...>

Use Context Master tools:
- get-repository-overview to gain a high-level understanding of the codebase and the most central symbols.
- get-symbol-context for `FooBar` and the top dependents (referenced-by).

I need tests for `computeRetryDelay` (used by our job queue).

Use get-symbol-context on `computeRetryDelay` and its referenced-by symbols (call-sites).

Then propose a test matrix that covers actual usage patterns and edge cases.

Draft internal docs for the `WebhookRouter` module.

Use Context Master tools:
- get-repository-overview to identify and understand the architecture of the codebase.
- get-symbol-context on the `WebhookRouter` symbol to list its dependents and dependencies.
- get-symbol-context on those symbols to gain a better understanding of the surroundings of `WebhookRouter`.

Write docs about:
- Entry points and how requests are routed
- How signatures are verified
- Where retries/idempotency are handled
- How to add a new webhook handler (step-by-step).