Paste into Claude Code / CLAUDE.md task

# DevAgentRadar → Claude Code

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

## Context
Assistant: Kiro
Proposal: Kiro v2.19.1
Summary: 2.19.1 Aug 21, 2026 Spec Review Mouse Support and Automatic Stream Recovery This release brings mouse support to the spec review screen. · Under the hood, a stream idle watchdog, automatic retries with backoff, and a 60-minute streaming timeout mean a dropped connection or a thro
Primary source: https://kiro.dev/changelog/#v2-19-1

## Why it matters
Release: Kiro v2.19.1
Detail: 2.19.1 Aug 21, 2026 Spec Review Mouse Support and Automatic Stream Recovery This release brings mouse support to the spec review screen. · Under the hood, a stream idle watchdog, automatic retries with backoff, and a 60-minute streaming timeout mean a dropped connection or a throttled request no longer hangs or ends your turn. · Mouse support in spec review The spec review screen now supports the 
Themes: agent, security, ide, cli
Developer angle: Try in a throwaway repo before changing daily workflow.
Team angle: Pilot / sandbox / policy review before org rollout.
Source: https://kiro.dev/changelog/#v2-19-1

## Suggested actions
1. Read the release notes for Kiro v2.19.1 to understand the full scope of the update.


## Your job
1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.