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

atvm/atvm-automation-guide.md

@@ -133,7 +133,7 @@ When asked for one VM or a VM set:
 ## Status Reporting Format
 When the operator asks for the status of an ATVM automation run, 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.
@@ -149,6 +149,7 @@ When the operator asks for the status of an ATVM automation run, report in this
 Status-report expectations:
 - Use the live automation VM state when available.
 - Derive the heading/title from the run `build_name` when available.
+- Format every machine entry as `machine-name - STATUS`.
 - Derive completed-machine status from completed spec results already written to the run log.
 - Include the run start time in every status response when it can be derived from the run log.
 - If the run is complete, include the end time and total run time.
@@ -163,4 +164,5 @@ Status-report expectations:
 - If a machine has not started yet, show it under remaining machines as `NOT STARTED`.
 - If no failures are present in completed spec results, report those completed machines as `PASS`.
 - If a completed spec result shows a failure, report that machine as `FAIL` and include the failure reason from the run log.
-- Base the completion estimate on the current remaining machine count and recent per-machine runtime visible in the run log.
+- Base the completion estimate on the full remaining machine count and recent per-machine runtime visible in the run log.
+- Make the estimate explicitly refer to completion of the entire remaining run, not only the current machine/spec.