getsentry/craft bootstrap deadlock: gcs target runs before docker in .craft.yml — gcs failure blocks Docker Hub update

Trap: craft's .craft.yml target order is npm → gcs → registry → docker → github → gh-pages. The publish loop is sequential + fail-fast. If gcs fails (e.g., due to Node regression), docker targets never run, so getsentry/craft:latest on Docker Hub never gets the fixed image. The fixed image IS built and pushed to ghcr.io/getsentry/craft:latest by the image workflow on master merge, but Docker Hub remains stale. Recovery: manually mirror ghcr.io/getsentry/craft:<sha> → Docker Hub, or retry publish after gcs is unblocked. Reordering .craft.yml to put docker before gcs would require two separate runs (npm already published on first run). Node 24.18.0 upgrade (PR #838) merged 2026-06-26; new release cut immediately after merge.