Guard Should Indicate Completion of a Run

When a Guard completes a run, there is currently no clear indication or signal that the run has finished. This can lead to confusion for the Guard itself, potentially causing it to initiate the same run again unintentionally.

Current Behavior:
Guard executes a run.

Upon completion, there is no final status update, notification, or marker to indicate that the process has concluded.

In the absence of this signal, Guard may assume the run hasn't been completed and may trigger the same execution again.

Proposed Solution:
Introduce a clear end-of-run indicator or state update that explicitly marks the run as completed. This could be in the form of:

A final status log or flag (e.g., run_status = "completed")

A UI message or notification

A lock or cooldown mechanism to prevent re-triggering within a short time frame