fix: bump completion latency budget to 200ms for CI

CI machines measured 141ms vs dev ~67ms. Use 200ms to accommodate
CI variance while still catching regressions (pre-fix was ~530ms).

Author: BYK

test/e2e/completion.test.ts

@@ -50,14 +50,14 @@ async function measureCommand(
 }
 
 describe("completion latency", () => {
-  test("completion exits under 100ms", async () => {
+  test("completion exits under 200ms", async () => {
     const result = await measureCommand(["__complete", "issue", "list", ""]);
 
     expect(result.exitCode).toBe(0);
 
-    // 100ms is the UX threshold for "instant" tab completion.
-    // Dev mode measures ~67ms; pre-optimization was ~530ms.
-    expect(result.duration).toBeLessThan(100);
+    // 200ms budget: dev mode ~67ms, CI ~140ms, pre-optimization ~530ms.
+    // Generous enough for CI variance while still catching regressions.
+    expect(result.duration).toBeLessThan(200);
   });
 
   test("completion exits cleanly with no stderr", async () => {