v4.124.1

Deploy resolve understands deployment hosts

run402 deploy resolve <url> and r.project(id).apply.resolve(...) now report dpl-*.sites.run402.com deployment hosts instead of host_missing:

• deployment_status: live (the active release or a subdomain serves the deployment), retained (replaced; still serving until origin_available_until), or retired (no longer served).
• path_evaluated: true when the path was resolved against the deployment's release (its static manifest and site.public_paths), with the usual match and authorization fields. A retired host, or a deployment no release names, is reported per host (match: deployment_host / deployment_retired).
• routes_active: false once a deployment was replaced; a matched route then reports result 404.
• The summary says when a replaced deployment host stops serving, and suggests the project host (or a promote) for a retired one.

These follow platform changes that are already live: a replaced deployment host serves for one hour after supersession (the same lifetime the project's own host gives removed files) and then answers 404, and deployment hosts honor site.public_paths like every other host.