Jiang Bohan d175a9cbb2 fix(issues): retry button targets the row's agent, not the assignee (MUL-2457) ...

The execution log retry button used to re-fire the issue's current
assignee instead of the agent that actually ran the clicked row. After
a reassignment, or for squad workers / @-mention agents, the rerun
landed on the wrong agent.

POST /api/issues/{id}/rerun now accepts an optional task_id: when set,
the rerun targets that task's agent (and reuses its leader/worker
role). An empty body keeps the assignee-driven CLI/API contract.

The execution-log retry button passes task.id, so per-row retry always
fires the correct agent. enqueueMentionTask gained a forceFreshSession
parameter so the new mention-path rerun keeps the same fresh-session
contract as the assignee path.

Co-authored-by: multica-agent <github@multica.ai>

2026-05-20 15:15:08 +08:00

..

core

fix(issues): retry button targets the row's agent, not the assignee (MUL-2457)

2026-05-20 15:15:08 +08:00

eslint-config

…

tsconfig

…

ui

refactor(editor): unify attachment rendering into a single <Attachment> component (#2850)

2026-05-19 16:23:19 +08:00

views

fix(issues): retry button targets the row's agent, not the assignee (MUL-2457)

2026-05-20 15:15:08 +08:00