Does instances.start with a numeric instance ID prevent starting a same-name replacement VM?

I’m looking for an authoritative Compute Engine REST v1 contract for instances.start:

Consider this sequence:

  1. A caller is authorized to start an existing VM and records its server-assigned numeric instance ID.
  2. That VM is deleted, and another VM is created in the same project/zone with the same name but a different numeric ID.
  3. Equivalent instance-level IAM permissions are copied or reapplied to the replacement.
  4. A delayed instances.start request uses the original numeric ID in the instance path field.

Is numeric-ID addressing officially supported for this action? If so, is the request guaranteed to remain bound to the original VM incarnation and reject before any start side effect on the replacement, including a delete/recreate race during authorization or execution?

If that guarantee is unavailable, does the API offer a supported immutable-ID or fingerprint precondition that provides it?

A preceding GET, request deduplication through requestId, or checking the returned operation’s targetId afterward would not establish prevention by themselves. Please point to documentation specifying the target-resolution and side-effect ordering guarantee.