If your machine can't be linked to a cloud session, it now runs cloud-only instead of failing.
What's wrong with this entry?
If the cloud service refuses to link the session to your machine, the session is kept and runs in the cloud instead of being archived and reported as a failure.
- A warning notice explains the consequence: no commands, hooks or pulling files back will run on this machine, and that "device binding is likely switched off there".
- Other unbound reasons still fail as before; only an explicit create refusal takes this path.
device binding is likely switched off there
Strings lifted out of the shipped bundle, so the claim above can be checked against them.