GeezerVison

Summary

• Table reads that hit the read statement timeout now return a 400 with code TABLE_QUERY_TIMEOUT and a readable message, instead of an opaque 500 "Failed to query rows". Sorting or range-filtering on a stored column reads every row's JSONB, so a large table can exceed the 15s guard on every attempt; the message points at the indexed createdAt/updatedAt sort, equality filters, or an Expiration column. Only the structured row query (the one that takes sort and filter) converts it; list, search, and write paths keep the raw error.
• POST /api/tools/custom answers a duplicate title (and a concurrent unique violation) with 409 instead of 500. The duplicate check now throws a typed CustomToolTitleConflictError.
• Instagram refresh code 190 (Graph API OAuthException: token logged out, revoked, or expired) is now recognized as a credential revocation, so the credential is flagged for reconnect and logged at WARN like other providers.
• Selector provider failures now log the endpoint (host + path, no query string), the reason, and the upstream status before being reduced to a 4xx/502. Previously nothing recorded why a selector returned 502.

Type of Change

• Bug fix

Testing

• New regression tests, each shown red with its guard reverted: duplicate-title 409 and the concurrent 23505 path (route.test.ts), statement-timeout mapping (rows.test.ts), Instagram 190 scoped to Instagram only (terminal-errors.test.ts)
• Ran route.test.ts, rows.test.ts, terminal-errors.test.ts, http.test.ts, use-cases.test.ts, credential-service.test.ts: 210 passed
• biome check on changed files; full type-check and audits left to CI

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)