Session and prompt lost when stopping an action or hitting the stop button

Bug Report

Description

When a user stops an in-progress action (e.g., hits the stop button during agent execution), the entire session — including the original prompt and any edits made to it — is deleted. This has happened multiple times.

Steps to Reproduce

1. Create a new session with a detailed prompt
2. The agent begins executing
3. Hit the "stop" button to cancel the action
4. The session disappears entirely — prompt, conversation history, and session are gone

Expected Behavior

Stopping an action should halt execution but preserve the session, the original prompt, and any conversation history up to that point. The user should be able to resume or re-run from that state.

Actual Behavior

The entire session is deleted, including the user's original prompt and any iterative edits they made to it. There is no way to recover the work.

Impact

• Loss of detailed, carefully crafted prompts that took time to write and iterate on
• User has to recreate the prompt from memory, losing edits made in the previous session
• Erodes trust in the tool for complex, multi-turn prompt development

Additional Context

• Reported by a user in the github/lifecyclemarketing project
• Has occurred multiple times (not a one-off)
• The lost session involved a complex weekly digest workflow prompt that had been edited several times before the stop action was triggered

通过创建一个包含已编辑 prompt 的会话、启动一个操作并按下停止按钮来复现该问题。跟踪停止/取消路径，以确定会话在哪个位置被删除；当执行停止，同时 prompt、编辑内容、对话历史记录和会话仍可用于恢复或重新运行时，即表示完成。