fix: bootstrap job uses wrong health endpoint (#21)

fix: use /api/health/details for bootstrap status check

The bootstrap job checked /api/health which only returns {status, version}.
The bootstrapStatus field is only available on /api/health/details (the
authenticated endpoint). This caused the "already bootstrapped?" check to
always fail, falling through to bootstrap-ceo which errors because the
admin already exists.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: stubbi

internal/resources/bootstrap.go

@@ -107,7 +107,9 @@ else
 fi
 
 # Step 2: Check if instance is already bootstrapped
-HEALTH=$(curl -sS -c "$COOKIE_JAR" -b "$COOKIE_JAR" "$SERVER_URL/api/health" 2>/dev/null) || true
+# Use /api/health/details (authenticated) which includes bootstrapStatus;
+# the plain /api/health endpoint does not return this field.
+HEALTH=$(curl -sS -c "$COOKIE_JAR" -b "$COOKIE_JAR" "$SERVER_URL/api/health/details" 2>/dev/null) || true
 if echo "$HEALTH" | grep -q '"bootstrapStatus":"ready"'; then
   echo "Instance already bootstrapped. Nothing to do."
   rm -f "$COOKIE_JAR"