[BUG] Message Processing Order at Terminal Finished (or Interrupted) #937

Problem (one or two sentences)

After finish running terminal command, if there are queued messages, Zoo will read the terminal output -> generate output -> and might go to another round of terminal running, ignoring the user message queue.

Context (who is affected and when)

When debugging or running the scripts, the user might read the terminal output and witness some obvious error, and provide feedback regarding currently running program.
However, after the terminal finish, or killed by user interruption, Zoo will ignore the queued message (user debug feedback) and just read and think the terminal output, ignoring queued user message at the first conversation. Currently, if the program is killed by the user, Zoo will mostly think "The user interrupted the code running, I need to run it again", and might simply go to another run of code without any consideration of user feedback from last run.

Reproduction steps

1. ask Zoo to run a code
2. when running, ask Zoo to modify the code
3. after finish, witness Zoo's behavior of processing terminal output and queued messages

Expected result

Read queued message (user debug feedback or message) right after terminal ends. And react with both terminal output and user debug feedbacks

Actual result

Ignoring queued message at the first round of conversation, and might go into another run of code without that

Variations tried (optional)

No response

App Version

v3.70.0

API Provider (optional)

None

Model Used (optional)

No response

Zoo Code Task Links (optional)

No response

Relevant logs or errors (optional)