fix(perstack): handle stoppedByInteractiveTool in TUI execution loop

[FL4TLiN3]

Summary

• Add stoppedByInteractiveTool to the list of statuses that allow continuing the TUI loop
• Track when the next query should be treated as an interactive tool result
• Pass the user's input through parseInteractiveToolCallResult when continuing from an interactive tool stop

Problem

When an expert calls an interactive tool and the run stops with status stoppedByInteractiveTool:

1. The TUI execution loop would exit immediately instead of allowing the user to continue
2. Even if continued via CLI flags, the user's input was treated as a regular text query instead of an interactive tool result
3. This caused the TUI to hang or display incorrectly

Solution

1. Added stoppedByInteractiveTool to canContinue conditions
2. Added isNextQueryInteractiveToolResult flag that is set to true when the run stops for interactive tool
3. Use this flag to determine whether to parse the next query as an interactive tool result

Test plan

• Local build succeeds
• Test with an expert that uses interactive tools (e.g., buyer-category-agent)

🤖 Generated with Claude Code

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!