Show last execution status and time on the Scenarios page

Feature request

Problem / motivation

When a Huginn instance contains many scenarios, it can be difficult to quickly determine which scenarios are actively running, which ones have recently executed, and which ones may not have produced events for a long time.

The Scenarios page already provides an overview of configured scenarios, but users need to open individual scenarios or agents to investigate their recent activity.

For monitoring and maintenance, having basic execution information directly in the scenario list would make it much easier to identify inactive or potentially problematic workflows.

Proposed solution

Add optional execution information to each scenario in the Scenarios page, such as:

• Last execution time

• Last execution status, such as successful, failed, or currently running

• Optionally, the time since the last execution

The information should link to the relevant scenario or execution details where appropriate.

A simple implementation could initially display only the timestamp and status, without adding detailed execution history to the Scenarios page.

Benefits

This would make it easier to:

• Monitor multiple scenarios from a single page

• Quickly identify scenarios that have stopped executing

• Notice failed workflows without opening each scenario

• Troubleshoot automation workflows more efficiently

• Manage large Huginn installations with many scenarios

Alternatives considered

Currently, users can open individual scenarios or agents and inspect their activity. This works, but requires navigating through multiple pages when monitoring a larger installation.

Another option would be a dedicated monitoring dashboard, but adding basic execution information to the existing Scenarios page would provide useful visibility with less UI complexity.

Additional context

Huginn scenarios represent groups of agents connected through event flows, so surfacing their most recent execution state would provide a useful high-level monitoring view without changing the underlying event-processing model.