rush-ai 0.6.0 → 0.9.0

package/dist/skills/hand-off.md

@@ -0,0 +1,163 @@
+# Skill: Hand off the task to Rush
+
+Use this skill when the user is talking to you inside an IDE (Cursor, Claude Code, or similar) and the next step belongs on the Rush platform. You already have full context from the conversation — `rush-ai` exists so you can relay that context to Rush's cloud agents without making the user summarize it again.
+
+## When this skill applies
+
+Triggers (not exhaustive — use judgement):
+
+- "Build me a landing page / product site / marketing page."
+- "Turn this spec / sketch / Figma link into a site."
+- "Spin up a demo site for X."
+- Any time the conversation points at producing a running web artifact the user will want to **share a link** for.
+
+Do NOT use this skill for:
+
+- Small local edits the user wants you to apply directly in the current repo.
+- Questions about Rush itself ("what is rush-ai", "how do I log in") — answer those from docs instead of creating a task.
+
+## Decision: which agent?
+
+| Situation | Agent to pass to `-a` |
+|---|---|
+| Build a website, landing page, marketing page, or anything that should render as a live preview URL | `web-builder` |
+| General-purpose conversation / analysis / generation the user would have asked a chat agent for | `rush` (the platform default) |
+| User named a specific specialist agent (e.g. "use the HR analytics agent") | that agent name verbatim |
+
+If you are unsure, start with `npx rush-ai agent list --default` — that shows just the built-in defaults (`web-builder`, `rush`, `skill-publisher`, ...), which is usually all you need for a hand-off. Widen with `--search <keyword>` or `--all` only when the user clearly asked for a specialist. When in doubt between `rush` and `web-builder`, ask the user — but if the output is going to be a URL, default to `web-builder`.
+
+## Playbook
+
+### 1. Verify auth (once per session)
+
+```bash
+npx rush-ai auth status --json
+```
+
+The response includes a boolean `authenticated` (or equivalent) plus an auth method. **Read it before you do anything else.** There are only two cases — no third case, no "maybe":
+
+- **Authenticated** → proceed to step 2.
+- **Not authenticated** → STOP. Print this exact message to the user and wait:
+
+  > Rush 还没登录。请在终端里跑 `npx rush-ai auth login`（会打开浏览器完成 CAS 登录），登录成功后告诉我一声。
+
+  Do NOT run `auth login` yourself — it opens a browser and waits for human interaction.
+  Do NOT invent workarounds (don't try API keys, don't edit `~/.rush/auth.json`).
+  Do NOT fall through to `task create` anyway — it will return 401 and confuse the user.
+
+When the user returns, re-run `auth status --json` to confirm before continuing.
+
+### 2. Create the task, carrying the context you already have
+
+Write the prompt from the conversation. Do **not** ask the user to restate requirements you already know. Include any constraints they have already mentioned (brand, style, pages, copy).
+
+```bash
+npx rush-ai task create \
+  -a web-builder \
+  -p "<prompt synthesized from the conversation>" \
+  --json
+```
+
+The JSON response contains `id`. Keep it; you'll need it for every follow-up.
+
+### 3. Report the handoff to the user
+
+Tell the user, in one line:
+
+- the task id
+- that it's running on Rush
+- how they can watch (either "I'll poll for you" or "open the Rush web UI")
+
+Don't dump the full JSON unless they ask.
+
+### 4. Poll status until ready
+
+```bash
+npx rush-ai task status <id> --json | jq -r '.status'
+```
+
+Terminal states: `completed`, `failed`, `cancelled`. Poll every ~15–30s; don't hammer it.
+
+**Pipe directly** — don't round-trip the JSON through a shell variable:
+
+```bash
+# good — JSON stays as raw bytes, no shell re-interpretation
+npx rush-ai task status <id> --json | jq -r '.status'
+
+# bad — zsh's builtin `echo` re-interprets \n as a real newline;
+#       jq then rejects the result with "control characters must be escaped".
+#       (bash's echo usually doesn't, but behavior is shell-dependent.)
+STATUS=$(npx rush-ai task status <id> --json)
+echo "$STATUS" | jq .     # ← breaks in zsh once the JSON contains \n
+
+# acceptable alternatives when you really need the variable:
+printf '%s' "$STATUS" | jq .   # portable — printf never re-interprets escapes
+jq . <<< "$STATUS"             # here-string — does not re-interpret backslash escapes
+```
+
+When `status == completed`, the response contains (for `web-builder`):
+
+- `previewUrl` — shareable live preview (e.g. `https://<id>-preview.rush.zhenguanyu.com/`)
+- `gitRepoUrl` — cloneable repo (e.g. `https://gitlab-ee.zhenguanyu.com/rush/online/<id>`)
+
+Present both to the user. The preview URL is the primary artifact they care about.
+
+### 5. Iterate via `task send`, not by creating new tasks
+
+If the user says "change the button color" / "add a testimonials section" / "make the hero bigger", **do not create a new task** — send a follow-up to the existing one:
+
+```bash
+npx rush-ai task send <id> -p "<the change they asked for>" --json
+```
+
+The preview URL stays the same; it will refresh after the send completes. Poll `task status <id>` again.
+
+Only create a fresh task if the user explicitly starts a new, unrelated project.
+
+### 6. Failure handling
+
+If `status == failed`, the response has an `error` field. Surface it to the user verbatim and ask whether to:
+
+1. retry with a revised prompt via `task send`,
+2. cancel and start over, or
+3. dig in themselves (give them the task id so they can look it up).
+
+Do not silently retry.
+
+## Example end-to-end
+
+User (in Cursor): "帮我做个公司官网首页，风格大气专业。"
+
+Your actions:
+
+```bash
+# 1. check auth (assume ok)
+npx rush-ai auth status --json
+
+# 2. create (prompt synthesized from the prior conversation — brand, tone, pages)
+npx rush-ai task create -a web-builder \
+  -p "做一个公司官网首页，包含导航、Hero、核心特性、客户评价和底部联系信息，风格大气专业。" \
+  --json
+# → {"id": "lodig8oknq0r", "status": "pending", ...}
+
+# 3. tell the user
+# "已经派到 Rush 的 web-builder，任务 id lodig8oknq0r，我帮你盯着。"
+
+# 4. poll
+npx rush-ai task status lodig8oknq0r --json
+# ...wait...
+# → {"status": "completed", "previewUrl": "https://lodig8oknq0r-preview.rush.zhenguanyu.com/", "gitRepoUrl": "..."}
+
+# 5. present
+# "跑完了：
+#    预览: https://lodig8oknq0r-preview.rush.zhenguanyu.com/
+#    代码: https://gitlab-ee.zhenguanyu.com/rush/online/lodig8oknq0r
+#  要改哪儿继续说，我走 task send 不新起任务。"
+```
+
+## Anti-patterns
+
+- ❌ Asking the user to re-describe requirements they already told you in-thread.
+- ❌ Creating a new task for every tweak — use `task send`.
+- ❌ Hiding the task id from the user (they may want to reopen the Rush UI later).
+- ❌ Running `task watch` when all you need is final status — it streams verbosely, use `task status` for quick polls.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rush-ai",
-  "version": "0.6.0",
+  "version": "0.9.0",
   "description": "Rush CLI - Command-line interface for the Rush AI platform",
   "private": false,
   "type": "module",
@@ -15,7 +15,9 @@
   },
   "files": [
     "dist",
+    "skills",
     "README.md",
+    "AGENTS.md",
     "LICENSE"
   ],
   "publishConfig": {
@@ -35,6 +37,7 @@
     "mcp"
   ],
   "dependencies": {
+    "@iarna/toml": "^2.2.5",
     "@modelcontextprotocol/sdk": "^1.12.1",
     "chalk": "^5.4.1",
     "commander": "^13.1.0",

package/skills/README.md

@@ -0,0 +1,48 @@
+# Rush-ai skills for AI agents
+
+`rush-ai` is a CLI for the Rush platform. If you are an AI agent (Cursor, Claude Code, a local sub-agent) reading this, these guides tell you when and how to invoke `rush-ai` on behalf of the user.
+
+## When to use rush-ai
+
+Pick the guide that matches the situation:
+
+- **You are in the middle of a conversation with the user (inside an IDE) and part of the work belongs on Rush.**
+  → Read [`hand-off.md`](./hand-off.md). Typical trigger: "build me a landing page", "turn this sketch into a site", "generate the docs site".
+
+- **You are composing a workflow and need a specialist agent as one of the steps.**
+  → Read [`agent-shelf.md`](./agent-shelf.md). Typical trigger: a workflow node that needs domain expertise you don't have (HR analytics, observability Q&A, physics reasoning, etc).
+
+Still unsure? Run `npx rush-ai agent list` first — seeing the available agents usually makes the decision obvious.
+
+## Cheat sheet
+
+```bash
+# Discover
+npx rush-ai agent list --default               # just the built-in defaults (web-builder, rush, skill-publisher, ...)
+npx rush-ai agent list --search "人力"         # fuzzy-filter the full shelf
+npx rush-ai agent list --all                   # everything (can be long)
+npx rush-ai agent info <agent>                 # inspect one agent's skills / MCP servers
+
+# Hand off
+npx rush-ai task create -a <agent> -p "<prompt>"   # create a task
+npx rush-ai task status <task-id>                  # check status (includes preview / git URLs when ready)
+npx rush-ai task send <task-id> -p "<follow-up>"   # iterate on a running task
+npx rush-ai task watch <task-id>                   # stream execution (SSE)
+
+# Defaults
+-a rush           # general-purpose agent; this is the CLI default, so `-a` can be omitted when you want `rush`
+-a web-builder    # site/landing-page builder; returns previewUrl + gitRepoUrl
+-a <other>        # any other agent name from `agent list` — confirm it exists first
+```
+
+`--json` on any command gives machine-readable output; use it when you need to parse the result.
+
+## Prerequisites the agent should enforce
+
+Before creating a task, make sure the user is authenticated:
+
+```bash
+npx rush-ai auth status
+```
+
+If not authenticated, tell the user to run `npx rush-ai auth login` in their terminal (the command is interactive and requires a browser — you cannot complete it on their behalf).

package/skills/agent-shelf.md

@@ -0,0 +1,102 @@
+# Skill: Call a Rush agent as your sub-agent
+
+Use this skill when you are composing a workflow — your own, or one the user described — and a step calls for domain expertise you don't have. Rush hosts a shelf of specialist agents. You can invoke any of them with one `rush-ai task create` call and feed the result back into your workflow.
+
+## When this skill applies
+
+Triggers:
+
+- The user's instructions name a specialist by role ("use the HR analytics expert", "ask the physics reasoning agent", "let the observability agent check it").
+- You're drafting a multi-step plan and one node is outside your competence (e.g. "analyze RUM data", "write a physics problem set", "summarize an HR report").
+- The user asks "what can Rush do that I can't?" — that's a prompt to show the shelf.
+
+Do NOT use this skill when:
+
+- The task fits the default general-purpose agent (`rush`) — that's a hand-off, not a sub-agent call. See `hand-off.md`.
+- The task needs a live web artifact — use `web-builder` via `hand-off.md`.
+
+## Playbook
+
+### 1. Discover — don't guess
+
+Always start by listing the shelf, unless the user already named a specific agent. Use the right scope for the question at hand:
+
+```bash
+# Just the built-in defaults — useful when you're looking for the general fallback
+npx rush-ai agent list --default --json
+
+# Fuzzy-filter when the user hinted at a domain
+npx rush-ai agent list --search "人力" --json
+
+# Full catalog — use sparingly, can be hundreds of entries
+npx rush-ai agent list --all --json
+```
+
+Pick the best match by name + description. If multiple are plausible, inspect one:
+
+```bash
+npx rush-ai agent info <agent-name> --json
+```
+
+If nothing fits, tell the user what's available and ask how to proceed — don't force-fit a wrong agent.
+
+### 2. Call it as a node in your workflow
+
+Treat the agent call like a pure function: input prompt, output task result. Compose your own prompt with the context the agent needs (not the whole conversation — just the inputs for this step).
+
+```bash
+npx rush-ai task create -a <agent-name> \
+  -p "<focused prompt — inputs + expected output format>" \
+  --json
+```
+
+For a workflow node you need synchronously, poll:
+
+```bash
+npx rush-ai task status <id> --json
+```
+
+When `status == completed`, the response has the output. For agents that produce structured results, request `--json` and parse it.
+
+### 3. Feed the result back into your workflow
+
+The sub-agent's output is just another piece of context for the next step of your plan. Incorporate it into the next action the way you would any tool result.
+
+If the output is unsatisfactory, either:
+
+- refine via `task send <id> -p "<clarification>"` (same sub-agent, same context), or
+- fall back to your plan B (try a different agent, or escalate to the user).
+
+## Example
+
+User: "帮我分析一下 Q1 的部门人效，然后根据结论写一段给 CEO 的周会汇报。"
+
+Your plan:
+
+1. Call a data-analysis sub-agent on Rush to do the number-crunching.
+2. Use the analysis output to draft the exec-summary locally.
+
+```bash
+# Step 1 — find the HR analytics specialist (--json returns { agents, pagination })
+npx rush-ai agent list --search "人力" --json | jq '.agents[] | {name, description}'
+# → matches "人力资源分析专家"
+
+# Step 2 — call it as a sub-agent node
+npx rush-ai task create -a 人力资源分析专家 \
+  -p "分析 Q1 各部门人效趋势，输出 3 条关键结论。" \
+  --json
+# → {"id": "t_abc", "status": "pending"}
+
+# Step 3 — wait for the node to finish
+npx rush-ai task status t_abc --json
+# → {"status": "completed", "result": "..."}
+
+# Step 4 — you take the result and draft the exec summary locally.
+```
+
+## Anti-patterns
+
+- ❌ Inventing an agent name. If `agent list` doesn't show it, it doesn't exist — tell the user.
+- ❌ Passing the entire original conversation as the sub-agent's prompt. Give it only the inputs it needs.
+- ❌ Using `web-builder` for non-website work. It's specialized for producing deployable sites.
+- ❌ Abandoning the workflow if the sub-agent call fails. Surface the error, offer a fallback.

package/skills/hand-off.md

@@ -0,0 +1,163 @@
+# Skill: Hand off the task to Rush
+
+Use this skill when the user is talking to you inside an IDE (Cursor, Claude Code, or similar) and the next step belongs on the Rush platform. You already have full context from the conversation — `rush-ai` exists so you can relay that context to Rush's cloud agents without making the user summarize it again.
+
+## When this skill applies
+
+Triggers (not exhaustive — use judgement):
+
+- "Build me a landing page / product site / marketing page."
+- "Turn this spec / sketch / Figma link into a site."
+- "Spin up a demo site for X."
+- Any time the conversation points at producing a running web artifact the user will want to **share a link** for.
+
+Do NOT use this skill for:
+
+- Small local edits the user wants you to apply directly in the current repo.
+- Questions about Rush itself ("what is rush-ai", "how do I log in") — answer those from docs instead of creating a task.
+
+## Decision: which agent?
+
+| Situation | Agent to pass to `-a` |
+|---|---|
+| Build a website, landing page, marketing page, or anything that should render as a live preview URL | `web-builder` |
+| General-purpose conversation / analysis / generation the user would have asked a chat agent for | `rush` (the platform default) |
+| User named a specific specialist agent (e.g. "use the HR analytics agent") | that agent name verbatim |
+
+If you are unsure, start with `npx rush-ai agent list --default` — that shows just the built-in defaults (`web-builder`, `rush`, `skill-publisher`, ...), which is usually all you need for a hand-off. Widen with `--search <keyword>` or `--all` only when the user clearly asked for a specialist. When in doubt between `rush` and `web-builder`, ask the user — but if the output is going to be a URL, default to `web-builder`.
+
+## Playbook
+
+### 1. Verify auth (once per session)
+
+```bash
+npx rush-ai auth status --json
+```
+
+The response includes a boolean `authenticated` (or equivalent) plus an auth method. **Read it before you do anything else.** There are only two cases — no third case, no "maybe":
+
+- **Authenticated** → proceed to step 2.
+- **Not authenticated** → STOP. Print this exact message to the user and wait:
+
+  > Rush 还没登录。请在终端里跑 `npx rush-ai auth login`（会打开浏览器完成 CAS 登录），登录成功后告诉我一声。
+
+  Do NOT run `auth login` yourself — it opens a browser and waits for human interaction.
+  Do NOT invent workarounds (don't try API keys, don't edit `~/.rush/auth.json`).
+  Do NOT fall through to `task create` anyway — it will return 401 and confuse the user.
+
+When the user returns, re-run `auth status --json` to confirm before continuing.
+
+### 2. Create the task, carrying the context you already have
+
+Write the prompt from the conversation. Do **not** ask the user to restate requirements you already know. Include any constraints they have already mentioned (brand, style, pages, copy).
+
+```bash
+npx rush-ai task create \
+  -a web-builder \
+  -p "<prompt synthesized from the conversation>" \
+  --json
+```
+
+The JSON response contains `id`. Keep it; you'll need it for every follow-up.
+
+### 3. Report the handoff to the user
+
+Tell the user, in one line:
+
+- the task id
+- that it's running on Rush
+- how they can watch (either "I'll poll for you" or "open the Rush web UI")
+
+Don't dump the full JSON unless they ask.
+
+### 4. Poll status until ready
+
+```bash
+npx rush-ai task status <id> --json | jq -r '.status'
+```
+
+Terminal states: `completed`, `failed`, `cancelled`. Poll every ~15–30s; don't hammer it.
+
+**Pipe directly** — don't round-trip the JSON through a shell variable:
+
+```bash
+# good — JSON stays as raw bytes, no shell re-interpretation
+npx rush-ai task status <id> --json | jq -r '.status'
+
+# bad — zsh's builtin `echo` re-interprets \n as a real newline;
+#       jq then rejects the result with "control characters must be escaped".
+#       (bash's echo usually doesn't, but behavior is shell-dependent.)
+STATUS=$(npx rush-ai task status <id> --json)
+echo "$STATUS" | jq .     # ← breaks in zsh once the JSON contains \n
+
+# acceptable alternatives when you really need the variable:
+printf '%s' "$STATUS" | jq .   # portable — printf never re-interprets escapes
+jq . <<< "$STATUS"             # here-string — does not re-interpret backslash escapes
+```
+
+When `status == completed`, the response contains (for `web-builder`):
+
+- `previewUrl` — shareable live preview (e.g. `https://<id>-preview.rush.zhenguanyu.com/`)
+- `gitRepoUrl` — cloneable repo (e.g. `https://gitlab-ee.zhenguanyu.com/rush/online/<id>`)
+
+Present both to the user. The preview URL is the primary artifact they care about.
+
+### 5. Iterate via `task send`, not by creating new tasks
+
+If the user says "change the button color" / "add a testimonials section" / "make the hero bigger", **do not create a new task** — send a follow-up to the existing one:
+
+```bash
+npx rush-ai task send <id> -p "<the change they asked for>" --json
+```
+
+The preview URL stays the same; it will refresh after the send completes. Poll `task status <id>` again.
+
+Only create a fresh task if the user explicitly starts a new, unrelated project.
+
+### 6. Failure handling
+
+If `status == failed`, the response has an `error` field. Surface it to the user verbatim and ask whether to:
+
+1. retry with a revised prompt via `task send`,
+2. cancel and start over, or
+3. dig in themselves (give them the task id so they can look it up).
+
+Do not silently retry.
+
+## Example end-to-end
+
+User (in Cursor): "帮我做个公司官网首页，风格大气专业。"
+
+Your actions:
+
+```bash
+# 1. check auth (assume ok)
+npx rush-ai auth status --json
+
+# 2. create (prompt synthesized from the prior conversation — brand, tone, pages)
+npx rush-ai task create -a web-builder \
+  -p "做一个公司官网首页，包含导航、Hero、核心特性、客户评价和底部联系信息，风格大气专业。" \
+  --json
+# → {"id": "lodig8oknq0r", "status": "pending", ...}
+
+# 3. tell the user
+# "已经派到 Rush 的 web-builder，任务 id lodig8oknq0r，我帮你盯着。"
+
+# 4. poll
+npx rush-ai task status lodig8oknq0r --json
+# ...wait...
+# → {"status": "completed", "previewUrl": "https://lodig8oknq0r-preview.rush.zhenguanyu.com/", "gitRepoUrl": "..."}
+
+# 5. present
+# "跑完了：
+#    预览: https://lodig8oknq0r-preview.rush.zhenguanyu.com/
+#    代码: https://gitlab-ee.zhenguanyu.com/rush/online/lodig8oknq0r
+#  要改哪儿继续说，我走 task send 不新起任务。"
+```
+
+## Anti-patterns
+
+- ❌ Asking the user to re-describe requirements they already told you in-thread.
+- ❌ Creating a new task for every tweak — use `task send`.
+- ❌ Hiding the task id from the user (they may want to reopen the Rush UI later).
+- ❌ Running `task watch` when all you need is final status — it streams verbosely, use `task status` for quick polls.

package/dist/chunk-MG4HY2PD.js

@@ -1,136 +0,0 @@
-#!/usr/bin/env node
-
-// src/util/sse.ts
-function createSSEParser(onEvent, onDone) {
-  let buffer = "";
-  return {
-    feed(chunk) {
-      buffer += chunk;
-      const lines = buffer.split("\n");
-      buffer = lines.pop() ?? "";
-      for (const line of lines) {
-        if (line.startsWith("data: ")) {
-          const data = line.slice(6);
-          if (data === "[DONE]") {
-            onDone?.();
-            return;
-          }
-          try {
-            const parsed = JSON.parse(data);
-            onEvent({
-              type: parsed.type ?? "unknown",
-              data: typeof parsed.data === "string" ? parsed.data : JSON.stringify(parsed)
-            });
-          } catch {
-            onEvent({ type: "raw", data });
-          }
-        }
-      }
-    },
-    flush() {
-      if (buffer.startsWith("data: ")) {
-        const data = buffer.slice(6);
-        if (data !== "[DONE]") {
-          try {
-            const parsed = JSON.parse(data);
-            onEvent({
-              type: parsed.type ?? "unknown",
-              data: typeof parsed.data === "string" ? parsed.data : JSON.stringify(parsed)
-            });
-          } catch {
-            onEvent({ type: "raw", data });
-          }
-        }
-      }
-      buffer = "";
-    }
-  };
-}
-async function consumeSSEStreamWithReconnect(connectFn, onEvent, options = {}) {
-  const {
-    maxReconnects = 5,
-    reconnectDelay = 1e3,
-    signal,
-    onReconnect,
-    isTerminal
-  } = options;
-  let emittedEventCount = 0;
-  let reconnectAttempts = 0;
-  let terminalReached = false;
-  while (!terminalReached) {
-    if (signal?.aborted) return;
-    let receivedDone = false;
-    let currentEventIndex = 0;
-    try {
-      const stream = await connectFn();
-      const reader = stream.getReader();
-      const decoder = new TextDecoder();
-      const parser = createSSEParser(
-        (event) => {
-          currentEventIndex++;
-          if (currentEventIndex <= emittedEventCount) {
-            if (isTerminal?.(event)) {
-              terminalReached = true;
-            }
-            return;
-          }
-          emittedEventCount++;
-          onEvent(event);
-          if (isTerminal?.(event)) {
-            terminalReached = true;
-          }
-        },
-        () => {
-          receivedDone = true;
-        }
-      );
-      for (; ; ) {
-        if (signal?.aborted || terminalReached) {
-          reader.cancel().catch(() => {
-          });
-          return;
-        }
-        const { done, value } = await reader.read();
-        if (done) break;
-        parser.feed(decoder.decode(value, { stream: true }));
-        if (terminalReached) {
-          reader.cancel().catch(() => {
-          });
-          return;
-        }
-      }
-      parser.flush();
-    } catch {
-      if (signal?.aborted || terminalReached) return;
-    }
-    if (terminalReached) return;
-    if (receivedDone && terminalReached) return;
-    reconnectAttempts++;
-    if (reconnectAttempts > maxReconnects) {
-      throw new Error(
-        `SSE reconnection failed after ${maxReconnects} attempts`
-      );
-    }
-    if (signal?.aborted) return;
-    onReconnect?.(reconnectAttempts);
-    const delay = Math.min(
-      reconnectDelay * 2 ** (reconnectAttempts - 1),
-      3e4
-    );
-    await new Promise((resolve) => {
-      const timer = setTimeout(resolve, delay);
-      if (signal) {
-        const onAbort = () => {
-          clearTimeout(timer);
-          resolve();
-        };
-        signal.addEventListener("abort", onAbort, { once: true });
-      }
-    });
-  }
-}
-
-export {
-  consumeSSEStreamWithReconnect
-};
-//# sourceMappingURL=chunk-MG4HY2PD.js.map

package/dist/chunk-MG4HY2PD.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/util/sse.ts"],"sourcesContent":["/**\n * SSE (Server-Sent Events) line-buffered parser.\n * Handles events split across multiple chunks.\n */\nexport interface SSEEvent {\n  type: string;\n  data: string;\n}\n\nexport function createSSEParser(\n  onEvent: (event: SSEEvent) => void,\n  onDone?: () => void\n) {\n  let buffer = '';\n\n  return {\n    feed(chunk: string): void {\n      buffer += chunk;\n      const lines = buffer.split('\\n');\n      // Keep the last (possibly incomplete) line in the buffer\n      buffer = lines.pop() ?? '';\n\n      for (const line of lines) {\n        if (line.startsWith('data: ')) {\n          const data = line.slice(6);\n          if (data === '[DONE]') {\n            onDone?.();\n            return;\n          }\n          try {\n            const parsed = JSON.parse(data);\n            onEvent({\n              type: parsed.type ?? 'unknown',\n              data:\n                typeof parsed.data === 'string'\n                  ? parsed.data\n                  : JSON.stringify(parsed),\n            });\n          } catch {\n            // Non-JSON SSE data\n            onEvent({ type: 'raw', data });\n          }\n        }\n      }\n    },\n    flush(): void {\n      // Process any remaining buffered data\n      if (buffer.startsWith('data: ')) {\n        const data = buffer.slice(6);\n        if (data !== '[DONE]') {\n          try {\n            const parsed = JSON.parse(data);\n            onEvent({\n              type: parsed.type ?? 'unknown',\n              data:\n                typeof parsed.data === 'string'\n                  ? parsed.data\n                  : JSON.stringify(parsed),\n            });\n          } catch {\n            onEvent({ type: 'raw', data });\n          }\n        }\n      }\n      buffer = '';\n    },\n  };\n}\n\n/**\n * Consume an SSE ReadableStream with proper cross-chunk buffering.\n */\nexport async function consumeSSEStream(\n  body: ReadableStream<Uint8Array>,\n  onEvent: (event: SSEEvent) => void,\n  onDone?: () => void\n): Promise<void> {\n  const reader = body.getReader();\n  const decoder = new TextDecoder();\n  const parser = createSSEParser(onEvent, onDone);\n\n  for (;;) {\n    const { done, value } = await reader.read();\n    if (done) break;\n    parser.feed(decoder.decode(value, { stream: true }));\n  }\n  parser.flush();\n}\n\nexport interface SSEReconnectOptions {\n  /** Maximum number of reconnection attempts (default: 5) */\n  maxReconnects?: number;\n  /** Initial reconnection delay in ms (default: 1000) */\n  reconnectDelay?: number;\n  /** AbortSignal to cancel the stream and reconnections */\n  signal?: AbortSignal;\n  /** Called before each reconnection attempt */\n  onReconnect?: (attempt: number) => void;\n  /**\n   * Determines if an event represents a terminal state.\n   * When this returns true, the stream stops and no reconnection occurs.\n   */\n  isTerminal?: (event: SSEEvent) => boolean;\n}\n\n/**\n * Consume an SSE stream with automatic reconnection and event deduplication.\n *\n * Key behaviors:\n * - [DONE] does NOT automatically stop the stream. Only `isTerminal(event)` stops it.\n * - If [DONE] is received without a terminal event, reconnection is triggered\n *   (e.g., server 5-minute SSE connection lifetime timeout).\n * - On reconnection, the server replays all historical events from epoch.\n *   Client-side deduplication skips already-seen events using an event counter.\n *\n * @param connectFn - Factory that creates a new SSE stream (called on each reconnect)\n * @param onEvent - Event handler (only called for new, non-duplicate events)\n * @param options - Reconnection options\n */\nexport async function consumeSSEStreamWithReconnect(\n  connectFn: () => Promise<ReadableStream<Uint8Array>>,\n  onEvent: (event: SSEEvent) => void,\n  options: SSEReconnectOptions = {}\n): Promise<void> {\n  const {\n    maxReconnects = 5,\n    reconnectDelay = 1000,\n    signal,\n    onReconnect,\n    isTerminal,\n  } = options;\n\n  let emittedEventCount = 0;\n  let reconnectAttempts = 0;\n  let terminalReached = false;\n\n  while (!terminalReached) {\n    if (signal?.aborted) return;\n\n    let receivedDone = false;\n    let currentEventIndex = 0;\n\n    try {\n      const stream = await connectFn();\n      const reader = stream.getReader();\n      const decoder = new TextDecoder();\n\n      // Note: We do NOT reset reconnectAttempts here.\n      // For [DONE]+running scenarios (server 5-min timeout), each reconnect\n      // should count toward the limit. The counter only resets after the\n      // function is called fresh.\n\n      const parser = createSSEParser(\n        (event) => {\n          currentEventIndex++;\n\n          // Dedup: skip events we've already emitted in previous connections\n          if (currentEventIndex <= emittedEventCount) {\n            // Still check for terminal even on dedup'd events\n            if (isTerminal?.(event)) {\n              terminalReached = true;\n            }\n            return;\n          }\n\n          emittedEventCount++;\n          onEvent(event);\n\n          if (isTerminal?.(event)) {\n            terminalReached = true;\n          }\n        },\n        () => {\n          receivedDone = true;\n        }\n      );\n\n      for (;;) {\n        if (signal?.aborted || terminalReached) {\n          reader.cancel().catch(() => {});\n          return;\n        }\n\n        const { done, value } = await reader.read();\n        if (done) break;\n        parser.feed(decoder.decode(value, { stream: true }));\n\n        if (terminalReached) {\n          reader.cancel().catch(() => {});\n          return;\n        }\n      }\n      parser.flush();\n    } catch {\n      // Stream error — will attempt reconnect below\n      if (signal?.aborted || terminalReached) return;\n    }\n\n    // If terminal was reached, we're done\n    if (terminalReached) return;\n\n    // If [DONE] was received AND we already got a terminal event, stop\n    // (This shouldn't happen because terminalReached would be true, but safety check)\n    if (receivedDone && terminalReached) return;\n\n    // Otherwise, reconnect: [DONE] without terminal = server timeout, or stream error\n    reconnectAttempts++;\n    if (reconnectAttempts > maxReconnects) {\n      throw new Error(\n        `SSE reconnection failed after ${maxReconnects} attempts`\n      );\n    }\n\n    if (signal?.aborted) return;\n\n    onReconnect?.(reconnectAttempts);\n\n    // Exponential backoff for reconnection\n    const delay = Math.min(\n      reconnectDelay * 2 ** (reconnectAttempts - 1),\n      30_000\n    );\n\n    await new Promise<void>((resolve) => {\n      const timer = setTimeout(resolve, delay);\n      if (signal) {\n        const onAbort = () => {\n          clearTimeout(timer);\n          resolve();\n        };\n        signal.addEventListener('abort', onAbort, { once: true });\n      }\n    });\n  }\n}\n"],"mappings":";;;AASO,SAAS,gBACd,SACA,QACA;AACA,MAAI,SAAS;AAEb,SAAO;AAAA,IACL,KAAK,OAAqB;AACxB,gBAAU;AACV,YAAM,QAAQ,OAAO,MAAM,IAAI;AAE/B,eAAS,MAAM,IAAI,KAAK;AAExB,iBAAW,QAAQ,OAAO;AACxB,YAAI,KAAK,WAAW,QAAQ,GAAG;AAC7B,gBAAM,OAAO,KAAK,MAAM,CAAC;AACzB,cAAI,SAAS,UAAU;AACrB,qBAAS;AACT;AAAA,UACF;AACA,cAAI;AACF,kBAAM,SAAS,KAAK,MAAM,IAAI;AAC9B,oBAAQ;AAAA,cACN,MAAM,OAAO,QAAQ;AAAA,cACrB,MACE,OAAO,OAAO,SAAS,WACnB,OAAO,OACP,KAAK,UAAU,MAAM;AAAA,YAC7B,CAAC;AAAA,UACH,QAAQ;AAEN,oBAAQ,EAAE,MAAM,OAAO,KAAK,CAAC;AAAA,UAC/B;AAAA,QACF;AAAA,MACF;AAAA,IACF;AAAA,IACA,QAAc;AAEZ,UAAI,OAAO,WAAW,QAAQ,GAAG;AAC/B,cAAM,OAAO,OAAO,MAAM,CAAC;AAC3B,YAAI,SAAS,UAAU;AACrB,cAAI;AACF,kBAAM,SAAS,KAAK,MAAM,IAAI;AAC9B,oBAAQ;AAAA,cACN,MAAM,OAAO,QAAQ;AAAA,cACrB,MACE,OAAO,OAAO,SAAS,WACnB,OAAO,OACP,KAAK,UAAU,MAAM;AAAA,YAC7B,CAAC;AAAA,UACH,QAAQ;AACN,oBAAQ,EAAE,MAAM,OAAO,KAAK,CAAC;AAAA,UAC/B;AAAA,QACF;AAAA,MACF;AACA,eAAS;AAAA,IACX;AAAA,EACF;AACF;AAoDA,eAAsB,8BACpB,WACA,SACA,UAA+B,CAAC,GACjB;AACf,QAAM;AAAA,IACJ,gBAAgB;AAAA,IAChB,iBAAiB;AAAA,IACjB;AAAA,IACA;AAAA,IACA;AAAA,EACF,IAAI;AAEJ,MAAI,oBAAoB;AACxB,MAAI,oBAAoB;AACxB,MAAI,kBAAkB;AAEtB,SAAO,CAAC,iBAAiB;AACvB,QAAI,QAAQ,QAAS;AAErB,QAAI,eAAe;AACnB,QAAI,oBAAoB;AAExB,QAAI;AACF,YAAM,SAAS,MAAM,UAAU;AAC/B,YAAM,SAAS,OAAO,UAAU;AAChC,YAAM,UAAU,IAAI,YAAY;AAOhC,YAAM,SAAS;AAAA,QACb,CAAC,UAAU;AACT;AAGA,cAAI,qBAAqB,mBAAmB;AAE1C,gBAAI,aAAa,KAAK,GAAG;AACvB,gCAAkB;AAAA,YACpB;AACA;AAAA,UACF;AAEA;AACA,kBAAQ,KAAK;AAEb,cAAI,aAAa,KAAK,GAAG;AACvB,8BAAkB;AAAA,UACpB;AAAA,QACF;AAAA,QACA,MAAM;AACJ,yBAAe;AAAA,QACjB;AAAA,MACF;AAEA,iBAAS;AACP,YAAI,QAAQ,WAAW,iBAAiB;AACtC,iBAAO,OAAO,EAAE,MAAM,MAAM;AAAA,UAAC,CAAC;AAC9B;AAAA,QACF;AAEA,cAAM,EAAE,MAAM,MAAM,IAAI,MAAM,OAAO,KAAK;AAC1C,YAAI,KAAM;AACV,eAAO,KAAK,QAAQ,OAAO,OAAO,EAAE,QAAQ,KAAK,CAAC,CAAC;AAEnD,YAAI,iBAAiB;AACnB,iBAAO,OAAO,EAAE,MAAM,MAAM;AAAA,UAAC,CAAC;AAC9B;AAAA,QACF;AAAA,MACF;AACA,aAAO,MAAM;AAAA,IACf,QAAQ;AAEN,UAAI,QAAQ,WAAW,gBAAiB;AAAA,IAC1C;AAGA,QAAI,gBAAiB;AAIrB,QAAI,gBAAgB,gBAAiB;AAGrC;AACA,QAAI,oBAAoB,eAAe;AACrC,YAAM,IAAI;AAAA,QACR,iCAAiC,aAAa;AAAA,MAChD;AAAA,IACF;AAEA,QAAI,QAAQ,QAAS;AAErB,kBAAc,iBAAiB;AAG/B,UAAM,QAAQ,KAAK;AAAA,MACjB,iBAAiB,MAAM,oBAAoB;AAAA,MAC3C;AAAA,IACF;AAEA,UAAM,IAAI,QAAc,CAAC,YAAY;AACnC,YAAM,QAAQ,WAAW,SAAS,KAAK;AACvC,UAAI,QAAQ;AACV,cAAM,UAAU,MAAM;AACpB,uBAAa,KAAK;AAClB,kBAAQ;AAAA,QACV;AACA,eAAO,iBAAiB,SAAS,SAAS,EAAE,MAAM,KAAK,CAAC;AAAA,MAC1D;AAAA,IACF,CAAC;AAAA,EACH;AACF;","names":[]}