Add status to RetryTimeoutError

[DevonFulcher]

Why

When the Semantic Layer SDK times out polling for query results (RetryTimeoutError), the error currently only includes timeout_s — the last known query status is lost. For agent contexts (dbt-mcp, ACA), a timeout with status COMPILED means the query finished SQL compilation and is executing against the data platform, indicating the query is too complex for agent use. Surfacing the status enables downstream consumers to make this distinction.

What

• Added optional status: Optional[str] = None parameter to RetryTimeoutError.__init__
• Updated __str__ to include status when present
• Both sync and async polling clients now pass qr.status.value when raising RetryTimeoutError
• Bumped version from 0.13.1 to 0.13.2
• Added unit tests for the error class and polling timeout behavior

Notes

Fully backwards compatible — existing callers that don't pass status get None. Uses str (not QueryStatus enum) to avoid coupling the error module to query models.

Drafted by Claude Opus 4.6 under the direction of @DevonFulcher

---

Note

Low Risk
Small, backwards-compatible error-reporting change plus tests and a dev dependency pin; main risk is minor behavior change in exception formatting/attributes for callers that introspect errors.

Overview
RetryTimeoutError now accepts an optional status and includes it in its string representation, while remaining backwards compatible when omitted.

Both sync and async GraphQL polling clients now pass the last known qr.status.value when raising RetryTimeoutError, and new unit tests assert the status propagation and formatting. Also adds an unreleased changelog entry and pins ruff to >=0.15 in dev dependencies.

^{Written by Cursor Bugbot for commit 7a2785f. This will update automatically on new commits. Configure here.}