An instance lifecycle command changes a particular target in a particular project and zone. Read those identifiers before starting or stopping it.
The guest status is also only one part of an operations review: persistent disks, network resources and other dependencies can remain after compute stops.
These fictional rendering tasks save lifecycle and machine configuration. The browser doesn't boot an operating system or measure application health. A production operator still needs the actual guest status, supported command workflow and relevant workload checks. Keep those claims separate when reporting a local result. A saved running state isn't evidence that a real application accepted a request.
Target the intended instance and distinguish configuration from guest behavior.