runtime-job-execution-reporting

To run long-running Hermes jobs in the background, you can convert blocking commands into background processes with robust polling. This prevents shell timeouts by orchestrating execution asynchronously and tracking progress until completion.

A receipt-based status report is a canonical final summary stored under state/receipts. It captures the final job status, stdout summaries, and exit codes to provide reliable progress tracking for Hermes runtime tasks.

You get a final status summary for Sapho-style workflows by polling the background job and inspecting the stamped receipt. The receipt provides the final report, including stdout and stderr summaries, once the Hermes task completes.

Yes, Hermes runtime job reporting distinguishes between fatal failures and non-fatal warnings. The receipt-driven reporting mechanism handles error and warning states differently while reporting final results to users.

The best way to poll for completion of Hermes tasks that stall interactions is to start them as background processes and poll their status. This approach provides reliable progress tracking and publishes a clear final report via a receipt.