#3069 extension push: version-drift check reports 'no previously published version found' when the registry call failed

Problem

In src/cli/commands/extension_push.ts the drift lookup (GET /extensions/{name}/latest) is wrapped in a try/catch that only logs at debug level. When the call fails for any reason (no network, server error, bad credentials), published stays undefined and checkVersionConsistency prints the first-publish message: unable to check for version drift, no previously published version found in the registry (this is expected on first publish). Observed on 2026-10-06 with swamp 20261006.100009.0 by running a dry run of @swamp/ssh (published 2026.09.28.1) inside a network-less namespace: the summary claimed no published version existed.

Expected

A failed lookup produces its own warning naming the failure (registry unreachable, HTTP status), distinct from the never-published case, so an author does not read a transient failure as a first publish.

Related

Found while triaging Lab #3016, which makes the dry-run summary list the registry call itself; the wording of this warning is separate.