added more information to the printout when asking to give me status of the atvm automation run

atvm/AGENTS.md

@@ -96,7 +96,7 @@ Use `atvm-automation-examples.md` as the common options/command reference.
 ### Status Request Format
 When the operator asks for run status, report in this order:
 1. Heading/title using the run `build_name`.
-2. Completed machines with pass/fail state for each machine.
+2. Completed machines with machine name first and status second for each machine.
 3. Skipped machines with reason.
 4. Remaining machines still to run.
 5. Summary counts for finished, passed, failed, and skipped machines.
@@ -112,6 +112,7 @@ When the operator asks for run status, report in this order:
 Status details:
 - Use the live run log on the automation VM when available.
 - Use the run `build_name` as the heading/title when available.
+- Format every machine entry as `machine-name - STATUS`.
 - Show blacklisted machines under skipped machines when they are part of the requested scope.
 - Show in-progress machines under remaining machines as `RUNNING`.
 - Show not-yet-started machines as `NOT STARTED`.
@@ -120,6 +121,7 @@ Status details:
 - Include start time in status output when it can be derived from the log.
 - Include end time and total runtime for completed runs, or elapsed runtime for active runs.
 - Include quickest completed test runtime, longest completed test runtime, and average completed test runtime under timing details when they can be derived from the log.
+- Make the estimated completion time refer to the entire remaining run, not only the current machine/spec.
 
 ### Automation Blacklist
 Always exclude these machines with `--exclude_partial_match` when building ATVM automation commands.