StackJack 0.1.0.6227+65355c2

This release fixes how automation runs are cut off when they reach their Max runtime. Long-running automations can now use the full runtime limit configured in the builder, and a run that hits that limit is correctly reported as timed out rather than interrupted.

Bug fixes

• Automations configured with a Max runtime above roughly 30 minutes were being stopped at around the 30-minute mark and reported as timed out, even though the builder allows values up to 3,600 seconds. The platform-wide run limit has been raised so that any Max runtime you configure (up to the 3,600-second maximum) is now honoured in full. Product documentation that referenced the old limit has been corrected.
• When a run reached its Max runtime while the agent was quiet (no output arriving at that moment), the run was recorded as "Interrupted" with a "Stream cancelled" error, the agent received no wrap-up prompt, and the summary could be cut off mid-sentence. In some cases the same situation was shown as a clean "Completed" run. Runs that hit their Max runtime are now consistently shown as "Timed out" with a "Max runtime exceeded" message, the agent is sent the wrap-up prompt to finish up, and the failure notification email correctly describes the run as timed out. "Interrupted" is once again reserved for runs stopped by a person.
• A run whose agent session had already finished just before the runtime limit was reached is now recorded with its real outcome (completed or failed) instead of being labelled as timed out.