Catch and classify errors from the Linear GraphQL API/SDK so an agent can distinguish invalid input from auth, rate-limit, or transient failures

Documented steps

1. Wrap SDK calls in try/catch — the @linear/sdk parses GraphQL error responses into typed error objects automatically.
2. Catch the base LinearError class to access request context (error.query, error.variables) and response context (error.status, error.data).
3. Catch InvalidInputLinearError specifically to handle mutations that failed due to bad user-supplied input, separate from other failure classes.
4. Inspect error.errors, the parsed GraphQL errors array, where each entry exposes an error message, a LinearErrorType classification, whether it's due to user input, and the GraphQL schema path.
5. Use error.raw when you need the untouched original error/response object for logging or debugging beyond what the typed wrapper exposes.
6. Use `instanceof` checks against the SDK's error classes to branch handling logic (e.g. retry on rate-limit-type errors, surface InvalidInputLinearError to the user, log unknown types).
7. Official docs: https://linear.app/developers/sdk-errors