[ryanweiler92]

Description

Deleting a routine run now also deletes the chats that came from it. Before, the run left its history, but its chats stayed in the owner's Chats list.

The latest result's "Ask Assistant" chat now uses the run's own chat, the same one History's "Open chat" opens. That way every chat of a run can be found from the run when the run is deleted.

Changes Made

• WorkRoutineRoom.deleteRun deletes these chats before it deletes the run:
  • the rooms the run's agent worked in (every room id in the run's node outputs; each run gets new ones),
  • the chat opened from the run in History or the sidebar,
  • the latest result's chat, while this run is still the routine's latest.
• Each chat is removed the way RemoveUserRoom removes one: it is marked inactive for the owner, and its agent code context and Redis copy are cleared.
• If a chat can't be deleted, the call fails and the run stays, so deleting it again finishes the job.
• WorkDeleteRoutineRun now returns { deleted: true, roomIds: [...] }, the rooms it deleted, so the client can leave one that is open.
• WorkRoutineRoom.open for the latest result now opens the chat keyed by the run id, not by the routine row's start time. A latest-result chat that already exists keeps opening.
  • Why: the row's start time is when the run was claimed, not when it started, and the next run overwrites it. An older run's latest-result chat could never be found again.
• 4 new tests in WorkRoutineRoomUnitTests.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.