Kiro Crew 0.7.0 adds durable work queues and broader pull-request watches

Kiro Crew 0.7.0, dated September 24, 2026, makes most settings take effect after saving and delays updates until active work is idle. Accepted subagent work, Task Runner steps, and workflow calls enter a durable queue, which restores queued work after a Gateway restart. Pull-request watches now accept GitHub, GitLab, Bitbucket Cloud, and Azure DevOps Services URLs, while Azure DevOps Server and Bitbucket Data Center remain unsupported. Other changes include a turn minimap and model and reasoning controls in desktop chat, plus isolated pods on Windows. Preview users can also choose OpenCode and goose backends, use Jev to route individual turns, or run remote crews on AWS Fargate. An optional Crew log records an append-only session trail and durable ledger across context compaction, and requires a Gateway restart to enable.