Merge remote-tracking branch 'upstream/main' into chore/merge-main-into-lv-2026-07-15

# Conflicts:
#	agent/src/pipeline.py
#	cdk/src/constructs/ecs-agent-cluster.ts
#	cdk/src/constructs/ecs-payload-bucket.ts
#	cdk/src/handlers/fanout-task-events.ts
#	cdk/src/handlers/shared/strategies/ecs-strategy.ts
#	cdk/src/handlers/shared/workflows.ts
#	cdk/src/stacks/agent.ts
#	cdk/test/constructs/ecs-agent-cluster.test.ts
#	cdk/test/handlers/shared/create-task-core.test.ts
#	cdk/test/handlers/shared/strategies/ecs-strategy.test.ts
#	cdk/test/handlers/shared/workflows.test.ts

Author: isadeks

agent/src/jira_reactions.py

@@ -25,7 +25,11 @@
     resolve_linear_api_token,
 )
 from context import assemble_prompt, fetch_github_issue
-from jira_reactions import comment_task_finished, comment_task_started
+from jira_reactions import (
+    comment_task_started,
+    transition_pr_opened,
+    transition_task_started,
+)
 from linear_reactions import react_task_finished, react_task_started
 from models import AgentResult, HydratedContext, RepoSetup, TaskConfig, TaskResult
 from observability import current_otel_trace_id, task_span
@@ -995,6 +999,17 @@ def _on_trace_truncated(max_bytes: int, first_dropped: int) -> None:
                 config.channel_metadata,
             )
 
+            # Move the Jira card To Do → In Progress so the board reflects that
+            # work has started (issue #572). No-op for non-Jira tasks.
+            # Best-effort; failures are logged and never block the pipeline.
+            # Part of the Early-ACK block (moved before setup_repo with the 👀
+            # and start comment) so board state updates immediately, not after
+            # the multi-minute baseline build.
+            transition_task_started(
+                config.channel_source,
+                config.channel_metadata,
+            )
+
             # Setup repo (deterministic pre-hooks). A failure/timeout/OOM in the
             # pre-agent baseline build raises here; it needs no local handler —
             # the outer ``except Exception`` at the bottom of this ``try`` writes
@@ -1327,6 +1342,14 @@ def _on_trace_truncated(max_bytes: int, first_dropped: int) -> None:
                     post_span.set_attribute("pr.url", pr_url or "")
             if pr_url:
                 progress.write_agent_milestone("pr_created", pr_url)
+                # Move the Jira card In Progress → In Review now that a PR is
+                # open (issue #572). Only fires when a PR was actually opened —
+                # failed / no-PR tasks leave the card where humans can see the
+                # failure comment. No-op for non-Jira tasks; best-effort.
+                transition_pr_opened(
+                    config.channel_source,
+                    config.channel_metadata,
+                )
 
             # Memory write — capture task episode and repo learnings
             memory_written = False
@@ -1388,14 +1411,14 @@ def _on_trace_truncated(max_bytes: int, first_dropped: int) -> None:
                 transition_state=linear_transition_state,
             )
 
-            # Terminal status comment on the Jira issue (REST shim, with the
-            # PR link when one was opened). No-op for non-Jira tasks.
-            comment_task_finished(
-                config.channel_source,
-                config.channel_metadata,
-                success=(overall_status == "success"),
-                pr_url=pr_url,
-            )
+            # NOTE: the terminal status comment on the Jira issue is NOT posted
+            # here. Since issue #573 the deterministic fan-out plane
+            # (``cdk/src/handlers/fanout-task-events.ts`` ``dispatchToJira``)
+            # owns the Jira final-status comment — it carries cost/turns/
+            # duration and, crucially, fires even if this agent crashes before
+            # reaching this point (max-turns, OOM). Posting here too would
+            # double-comment. The agent still posts the *start* comment
+            # (``comment_task_started`` above) for in-flight progress.
 
             # --trace trajectory S3 upload (design §10.1). Runs AFTER
             # post-hooks but BEFORE ``write_terminal`` so the resulting
@@ -1570,14 +1593,11 @@ def _on_trace_truncated(max_bytes: int, first_dropped: int) -> None:
                 success=False,
                 started_reaction_id=linear_eyes_reaction_id,
             )
-            # Best-effort failure comment on the Jira issue. No-op for
-            # non-Jira tasks; network failures are swallowed.
-            comment_task_finished(
-                config.channel_source,
-                config.channel_metadata,
-                success=False,
-                pr_url=None,
-            )
+            # NOTE: no Jira failure comment here — the fan-out plane's
+            # ``dispatchToJira`` (issue #573) owns the Jira terminal comment
+            # and fires on the platform side even when this crash path runs,
+            # so posting here would double-comment. (Contrast the Linear ❌
+            # reaction above, which the fan-out plane does not replicate.)
             raise