fix: QueryModeError.from() case-insensitive timeout detection

withTimeout throws "Timeout after Nms" (capital T) but from() checked
lowercase "timeout" — case-sensitive mismatch meant timeouts were
classified as QUERY_FAILED instead of QUERY_TIMEOUT/NETWORK_TIMEOUT.

Now uses toLowerCase() for timeout and R2/network keyword matching.
Added tests for both capital-T timeout and R2 network timeout paths.

Author: teamchong

src/convenience.test.ts

@@ -154,6 +154,17 @@ describe("error messages", () => {
     expect(err.message).toContain(".csv");
     expect(err.message).toContain(".json");
   });
+
+  it("QUERY_TIMEOUT from withTimeout-style capital-T message", () => {
+    const err = QueryModeError.from(new Error("Timeout after 10000ms"), { table: "events" });
+    expect(err.code).toBe("QUERY_TIMEOUT");
+    expect(err.message).toContain("events");
+  });
+
+  it("NETWORK_TIMEOUT when message mentions R2", () => {
+    const err = QueryModeError.from(new Error("R2 read timeout"), { table: "events" });
+    expect(err.code).toBe("NETWORK_TIMEOUT");
+  });
 });
 
 describe("DataFrame Pandas-like methods", () => {

src/errors.ts

@@ -70,9 +70,10 @@ export class QueryModeError extends Error {
       );
     }
 
-    // Timeouts
-    if (msg.includes("timeout") || msg.includes("timed out") || msg.includes("TIMEOUT")) {
-      const code = msg.includes("network") || msg.includes("R2") ? "NETWORK_TIMEOUT" : "QUERY_TIMEOUT";
+    // Timeouts — case-insensitive (withTimeout throws "Timeout after ...")
+    const msgLower = msg.toLowerCase();
+    if (msgLower.includes("timeout") || msgLower.includes("timed out")) {
+      const code = msgLower.includes("network") || msgLower.includes("r2") ? "NETWORK_TIMEOUT" : "QUERY_TIMEOUT";
       return new QueryModeError(
         code,
         `${code === "NETWORK_TIMEOUT" ? "Network" : "Query"} timeout${table ? ` on ${table}` : ""}: ${msg}`,