fix: surface insight generation errors in the UI

[wesm]

Summary

• Send actual error details (e.g. "claude CLI not found", "gemini
  failed: exit status 1") to the client instead of the generic
  "X generation failed" message. Stderr dumps are stripped from the
  short message since they're already visible in the log stream.
• Show task error details and execution logs in the main content pane
  instead of cramming them into the narrow sidebar. On error, the
  failed task is auto-selected so the user immediately sees an error
  banner and full log output.
• Sidebar task items are now clickable to view their details in the
  main pane (both during generation and after errors).

Closes #175

Generated with Claude Code

[roborev-ci]

roborev: Combined Review (f0b0fad)

Verdict: One medium severity issue found regarding task cancellation logic; all other findings are low severity or safe.

Medium

• Location: frontend/src/lib/components/insights/InsightsPage.svelte:411

Problem: The header action for a selected task always calls dismissTask(task.clientId), even when the task is still generating. That removes the task from the UI but does not abort the underlying generation, unlike the sidebar action, so work continues in the background and can later update state for a task the
user thought they had canceled.

• Fix: Make the main-pane button follow the same branch as the sidebar button: call cancelTask() for active tasks and dismissTask() only for errored tasks, and update the button title/label to match.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (a39853b)

Summary Verdict: The changes implement task selection and error surfacing, but introduce a build-breaking syntax error and a keyboard event handling issue that require fixes.

High Severity

• Location: frontend/src/lib/components/insights/InsightsPage.svelte:397
• Problem: Svelte syntax error. The Svelte compiler strictly requires {@const without spaces. The space before @const in { @const task = insights.selectedTask} causes Svelte to parse the block as a JavaScript expression, which will throw a syntax error ("Unexpected token @") and break the frontend build.
• Fix: Remove the space after the brace: {@const task = insights.selectedTask}

Medium Severity

• Location: frontend/src /lib/components/insights/InsightsPage.svelte:286-293
• Problem: The new onkeydown handler on .task-item receives bubbled Enter/Space events from the nested dismiss/cancel <button>. Keyboard-activating that button now
  selects the task first, which is inconsistent with the mouse path. Furthermore, the Space key action does not call preventDefault(), causing the page to scroll when pressed.
• Fix: Guard the handler so it only runs when e.target === e.currentTarget, and call e.preventDefault() before handling
  Enter/Space; alternatively, move task selection onto a dedicated button element and keep the dismiss button separate.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (c35a2b1)

Summary Verdict: The PR successfully improves insight task UX and error handling, but contains a high-severity Svelte template compilation error that must be resolved.

High

• Location: frontend/src/lib/components/insights/InsightsPage.svelte, line 397
• Problem: Svelte tag syntax does not allow a space between the opening brace { and the tag name @const. { @const task ...} will cause a template compilation
  /parsing error.
• Fix: Remove the space: {@const task = insights.selectedTask}.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)

[roborev-ci]

roborev: Combined Review (9c72769)

Summary Verdict: All reviewers agree the code is clean and no issues were found.

---

Synthesized from 3 reviews (agents: codex, gemini | types: default, security)