A reply posted while the agent already has a queued run in the same thread is
folded into that run on the server: the reply becomes the run's trigger and the
earlier comment joins its covered set. The run's status does not change, so no
task event fired and open issue pages kept the run under the earlier comment,
leaving the new reply with no visible queue row.
Publish task:coalesced after the merge (and after a delegated-failure merge).
Web and desktop already refresh the issue's runs on any task: event, which moves
the queued block under the newest comment it answers; mobile now listens for it
too.
Co-authored-by: Cursor <[email protected]>
Co-authored-by: multica-agent <[email protected]>
* feat(issues): show agent runs inline with comment replies
* fix(issues): unify run comment projection and preserve disclosure focus
* refactor(issues): replace nested run cards with inline status rows
* fix(issues): align thread roots with reply content
* style(issues): remove thread toggle background
* style(issues): group reaction picker with comment actions
* feat(issues): show readable issue references in run summaries
* style(issues): move completed run logs into comment headers
* style(issues): balance comment block vertical spacing
* style(issues): shimmer live agent progress text
* style(issues): unify comment action hover feedback
* style(issues): reveal comment actions on block hover
* fix(issues): move published reply activity into the header
* fix(issues): settle comment UI as soon as replies are published
* fix(issues): reveal comment log buttons on hover
* fix(issues): defer run placement until trigger comments arrive
* fix(issues): isolate agent comment queues by thread
* fix(issues): display pending runs in execution order
* fix(ci): align integration tests with thread-scoped queues
* fix(issues): fit run actions to narrow comment columns
