linear-grab 0.20.0 → 0.20.2

package/dist/linear-grab.js

@@ -25754,7 +25754,7 @@ function pD(e) {
 	return i.length && t.push(i.join(" ")), t.join("\n\n");
 }
 var mD, hD, gD = t((() => {
-	mD = "You are an expert engineer drafting a Linear issue for a development team.\nYou are given a rough note from the reporter and, when available, the exact React source\nlocation of the UI element the issue is about (captured from a running dev build).\n\nWrite a crisp, actionable issue a coding agent can execute against with zero follow-up\nquestions. Be specific, never invent details you were not given, and keep the tone neutral\nand technical. If the note implies a bug, structure it as a bug; if it implies a change or\nfeature, keep reproSteps minimal and focus the description on the desired change.\n\nThe issue renders in this exact section order — fill each field for its section:\nSummary (description field) → Steps to Reproduce (reproSteps) → Expected Behavior\n(expected) → Actual Behavior (actual) → Impact (impact) → Analysis / Notes\n(analysisNotes, markdown bullets grounded in the provided source context) →\nSuggested Next Steps (suggestedNextSteps, markdown bullets with concrete fixes).\nThe Summary is a short plain-prose paragraph — no headings inside it, no repetition\nof the other sections.", hD = "- FIRST, self-orient in the repo checkout (skip any path that doesn't exist):\n  1. Read `CLAUDE.md` and `AGENTS.md` at the repo root — the master map of product rules, architecture, and memory/skill pointers.\n  2. Skim `.claude/memory/MEMORY.md` (the index) to learn what project memory exists; load the specific `.claude/memory/*.md` files the map names for the surface you're touching.\n  3. Load the matching `.claude/skills/<name>/SKILL.md` files before designing, building UI, or animating (if skills are symlinked, follow them into `.agents/skills/`).\n  Treat all of this as authoritative — it overrides your defaults.\n- Keep going until the code works and you're happy with the implementation.\n- MANDATORY COMPLETION GATE — the task is NOT complete (and you may not call it complete) until every step below is done, in order. Skipping any step silently is a FAILED task:\n  1. RUN the app and TEST your change hands-on (computer use / a real browser against the running app). Code reading alone does not count as verification.\n  2. RECORD a demo video or GIF showing the fix working (before → after where possible). If your environment genuinely cannot record media, capture before/after screenshots instead AND state explicitly in your closeout comment why video was not possible — never just omit the demo.\n  3. Open the PR, babysit it for the first set of review comments, and address them. If the repo has preview deployments (e.g. Vercel), wait for the preview to go green and include its URL — deep-linked to the changed page — in the PR body, the Linear closeout, and the announcement.\n  4. CLOSE OUT THE LINEAR ISSUE: post a completion comment (one-line fix summary + PR link), attach the demo media to the ISSUE itself (not only the PR), and move the issue to its review/done state.";
+	mD = "You are an expert engineer drafting a Linear issue for a development team.\nYou are given a rough note from the reporter and, when available, the exact React source\nlocation of the UI element the issue is about (captured from a running dev build).\n\nWrite a crisp, actionable issue a coding agent can execute against with zero follow-up\nquestions. Be specific, never invent details you were not given, and keep the tone neutral\nand technical. If the note implies a bug, structure it as a bug; if it implies a change or\nfeature, keep reproSteps minimal and focus the description on the desired change.\n\nThe issue renders in this exact section order — fill each field for its section:\nSummary (description field) → Steps to Reproduce (reproSteps) → Expected Behavior\n(expected) → Actual Behavior (actual) → Impact (impact) → Analysis / Notes\n(analysisNotes, markdown bullets grounded in the provided source context) →\nSuggested Next Steps (suggestedNextSteps, markdown bullets with concrete fixes).\nThe Summary is a short plain-prose paragraph — no headings inside it, no repetition\nof the other sections.", hD = "- FIRST, self-orient in the repo checkout (skip any path that doesn't exist):\n  1. Read `CLAUDE.md` and `AGENTS.md` at the repo root — the master map of product rules, architecture, and memory/skill pointers.\n  2. Skim `.claude/memory/MEMORY.md` (the index) to learn what project memory exists; load the specific `.claude/memory/*.md` files the map names for the surface you're touching.\n  3. Load the matching `.claude/skills/<name>/SKILL.md` files before designing, building UI, or animating (if skills are symlinked, follow them into `.agents/skills/`).\n  Treat all of this as authoritative — it overrides your defaults.\n- Live render telemetry (react-scan → linear-grab bridge): if `.lineargrab/scan.ndjson` exists in the repo, it holds the user's REAL interaction slowdowns — component render counts, self-times, change causes (`prop:x`/`state:i`/`context:y`), and interaction latencies, newest last. `curl -s http://127.0.0.1:4577/scan/report` returns an aggregated view. For any re-render/performance issue: read it BEFORE fixing (the evidence) and AFTER (the proof), and cite before→after numbers in your closeout.\n- Keep going until the code works and you're happy with the implementation.\n- MANDATORY COMPLETION GATE — the task is NOT complete (and you may not call it complete) until every step below is done, in order. Skipping any step silently is a FAILED task:\n  1. RUN the app and TEST your change hands-on (computer use / a real browser against the running app). Code reading alone does not count as verification.\n  2. RECORD a demo video or GIF showing the fix working (before → after where possible). If your environment genuinely cannot record media, capture before/after screenshots instead AND state explicitly in your closeout comment why video was not possible — never just omit the demo.\n  3. Open the PR, babysit it for the first set of review comments, and address them. If the repo has preview deployments (e.g. Vercel), wait for the preview to go green and include its URL — deep-linked to the changed page — in the PR body, the Linear closeout, and the announcement.\n  4. CLOSE OUT THE LINEAR ISSUE: post a completion comment (one-line fix summary + PR link), attach the demo media to the ISSUE itself (not only the PR), and move the issue to its review/done state.";
 })), _D = /* @__PURE__ */ r({
 	describeAiError: () => bD,
 	executeDraft: () => vD
@@ -41930,7 +41930,7 @@ function vQ() {
 		let e = HD().result;
 		if (!e) throw Error("No recording available.");
 		if (e.assetUrl) return e.assetUrl;
-		let t = await DO(e.blob, `recording-${Date.now()}.gif`);
+		let t = await Promise.race([DO(e.blob, `recording-${Date.now()}.gif`), new Promise((e, t) => setTimeout(() => t(/* @__PURE__ */ Error("upload timed out")), 6e4))]);
 		return rO(t), t;
 	}, k = async () => {
 		w(null), S("busy");
@@ -43132,20 +43132,27 @@ function i$(e, t = 6e3) {
 	return Promise.race([e, new Promise((e, n) => setTimeout(() => n(/* @__PURE__ */ Error("upload timeout")), t))]);
 }
 async function a$() {
-	let e = [];
-	for (let t of await Dr() ?? []) {
-		let n = t.source?.filePath ? ` — \`${t.source.filePath}${t.source.lineNumber == null ? "" : `:${t.source.lineNumber}`}\`` : "";
-		if (e.push(`- \`<${t.componentName ?? t.tagName ?? "element"}>\`${n}`), t.screenshotDataUrl) try {
-			let n = await i$(DO(ej(t.screenshotDataUrl), `capture-${t.grabbedAt}.png`));
-			e.push(`  ![capture](${n})`);
-		} catch {}
+	let e = [], t = [];
+	for (let n of await Dr() ?? []) {
+		let r = n.source?.filePath ? ` — \`${n.source.filePath}${n.source.lineNumber == null ? "" : `:${n.source.lineNumber}`}\`` : "";
+		if (e.push(`- \`<${n.componentName ?? n.tagName ?? "element"}>\`${r}`), n.screenshotDataUrl) try {
+			let t = await i$(DO(ej(n.screenshotDataUrl), `capture-${n.grabbedAt}.png`), 15e3);
+			e.push(`  ![capture](${t})`);
+		} catch {
+			t.push("element screenshot upload failed — the ref line still landed");
+		}
 	}
-	let t = HD();
-	if (t.result) try {
-		let n = t.result.assetUrl ?? await i$(DO(t.result.blob, `recording-${Date.now()}.gif`));
-		rO(n), e.push(`![recording](${n})`);
-	} catch {}
-	return e.length ? `Captured context:\n${e.join("\n")}` : null;
+	let n = HD();
+	if (n.result) try {
+		let t = n.result.assetUrl ?? await i$(DO(n.result.blob, `recording-${Date.now()}.gif`), 6e4);
+		rO(t), e.push(`![recording](${t})`);
+	} catch (e) {
+		t.push(`recording upload failed (${e instanceof Error ? e.message : "error"}) — Copy GIF from the Capture tab and paste it instead`);
+	}
+	return {
+		block: e.length ? `Captured context:\n${e.join("\n")}` : null,
+		failed: t
+	};
 }
 //#endregion
 //#region src/panel/components/markdown.ts
@@ -43573,8 +43580,8 @@ function p1(e) {
 	})), [C, w] = T(!1), E = async () => {
 		w(!0), y(null);
 		try {
-			let e = await a$();
-			e ? _((t) => `${t ? `${t}\n` : ""}${e}\n`) : y("Nothing captured yet — pick an element, capture a region, or record first.");
+			let { block: e, failed: t } = await a$();
+			e ? _((t) => `${t ? `${t}\n` : ""}${e}\n`) : t.length || y("Nothing captured yet — pick an element, capture a region, or record first."), t.length && y(t.join(" · "));
 		} catch (e) {
 			y(e instanceof Error ? e.message : "Attach failed.");
 		} finally {
@@ -44694,8 +44701,8 @@ function v0() {
 	let y = async () => {
 		m(!0);
 		try {
-			let e = await a$();
-			e && f((t) => `${t ? `${t}\n` : ""}${e}\n`);
+			let { block: e, failed: t } = await a$();
+			e && f((t) => `${t ? `${t}\n` : ""}${e}\n`), t.length && f((e) => `${e}\n<!-- upload issues: ${t.join(" · ")} -->\n`);
 		} finally {
 			m(!1);
 		}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "linear-grab",
-  "version": "0.20.0",
+  "version": "0.20.2",
   "type": "module",
   "description": "Point at any React element in your dev app, draft a Linear issue with AI, delegate it to the Cursor agent, and track it live — in any browser.",
   "exports": {