fix(self-host): report CLI status, and show brain-init progress

Two ways the installer left an operator in the dark.

1. Nothing in this repo installed, updated, or even mentioned the DeepSQL CLI, so
   a reader who followed the README end to end finished with a running stack and
   no `deepsql` command — and anyone who installed it once drifted silently (a
   machine here sat on 0.16.0 while npm was on 0.26.0). Since the CLI is an
   agent-facing surface, a stale one misreports which tools exist. install.sh now
   reports installed vs latest and prints the exact install/update command.

   It reports rather than installs: `npm i -g` is a global mutation that can need
   elevated permissions, so the decision stays with the operator and the check can
   never fail the install. When npm is unreachable it says so instead of claiming
   "up to date" — that false green is the same class of bug as the stale CLI.

2. smoke-test.sh polled brain init for up to DEEPSQL_SMOKE_INIT_TIMEOUT_SECONDS
   (default 1200) while printing nothing at all: every check before it prints only
   on failure. Indistinguishable from a hang, and duly killed at 10 minutes by
   someone watching it, well before it would have finished. It now announces the
   wait and prints stage/percent on change.

Author: geekypunk

scripts/self-host/install.sh

@@ -476,6 +476,49 @@ else
   echo
 fi
 
+# ── DeepSQL CLI (@deepsql/mcp) ───────────────────────────────────────────────
+# Nothing in this repo installed or updated the CLI, so a reader who followed the
+# README end to end finished with a running stack and no `deepsql` command at
+# all — and anyone who installed it once drifted silently (a machine here sat on
+# 0.16.0 while npm was on 0.26.0). The CLI is an agent-facing surface, so a stale
+# one misreports which tools and subcommands exist.
+#
+# Report rather than install: this is a global npm mutation, and `npm i -g` can
+# need elevated permissions depending on the Node install. Printing the exact
+# command keeps the decision with the operator and never fails the install.
+report_cli_status() {
+  if ! command -v npm >/dev/null 2>&1; then
+    echo "DeepSQL CLI: npm not found — skipping check."
+    echo "  The CLI is optional; install Node 20+ then: npm i -g @deepsql/mcp"
+    echo
+    return 0
+  fi
+  local installed latest
+  installed="$(deepsql --version 2>/dev/null | tr -d '[:space:]' || true)"
+  # `npm view` reaches the network; never let it stall or fail the install.
+  latest="$(npm view @deepsql/mcp version 2>/dev/null | tr -d '[:space:]' || true)"
+
+  if [[ -z "$installed" ]]; then
+    echo "DeepSQL CLI: not installed."
+    echo "  Install it with:  npm i -g @deepsql/mcp"
+  elif [[ -z "$latest" ]]; then
+    # Don't claim "up to date" on a check that never completed — that is the
+    # same false-green that let a stale CLI sit unnoticed in the first place.
+    echo "DeepSQL CLI: ${installed} installed (could not reach npm to check for updates)."
+  elif [[ "$installed" != "$latest" ]]; then
+    echo "DeepSQL CLI: ${installed} installed, ${latest} available."
+    echo "  Update with:  npm i -g @deepsql/mcp@latest"
+  else
+    echo "DeepSQL CLI: ${installed} (up to date)."
+  fi
+  if [[ -n "$installed" ]]; then
+    echo "  Point it at this stack:  deepsql login --url http://localhost:${DEEPSQL_BACKEND_PORT}"
+  fi
+  echo
+}
+
+report_cli_status
+
 echo "Useful commands:"
 echo "  ./scripts/self-host/status.sh"
 echo "  ./scripts/self-host/smoke-test.sh"

scripts/self-host/smoke-test.sh

@@ -140,11 +140,21 @@ if [[ "$schema_json" != *'"success":true'* ]]; then
 fi
 
 if [[ "$DEEPSQL_SMOKE_WAIT_FOR_INIT" == "true" ]]; then
+  # Brain init calls the LLM once per schema batch and routinely runs for many
+  # minutes. Every check up to this point prints only on failure, so without the
+  # progress lines below this script sat completely mute for up to
+  # DEEPSQL_SMOKE_INIT_TIMEOUT_SECONDS (default 1200) — indistinguishable from a
+  # hang, and duly killed by whoever was watching it, well before it would have
+  # finished.
+  echo "Waiting for brain init (up to ${DEEPSQL_SMOKE_INIT_TIMEOUT_SECONDS}s)."
+  echo "This calls the LLM once per schema batch, so several minutes is normal."
   deadline=$((SECONDS + DEEPSQL_SMOKE_INIT_TIMEOUT_SECONDS))
+  last_report=""
   while (( SECONDS < deadline )); do
     init_json="$(curl -fsS -b "$cookie_jar" "$base/connections/${connection_id}/init-status")"
     init_stage="$(printf '%s' "$init_json" | sed -n 's/.*"currentStage":"\([^"]*\)".*/\1/p')"
     init_progress="$(printf '%s' "$init_json" | sed -n 's/.*"progressPercent":\([0-9][0-9]*\).*/\1/p')"
+    init_message="$(printf '%s' "$init_json" | sed -n 's/.*"stageMessage":"\([^"]*\)".*/\1/p')"
 
     if [[ "$init_stage" == "COMPLETED" ]]; then
       echo "Brain init completed for smoke-test connection (${init_progress:-100}%)."
@@ -157,6 +167,14 @@ if [[ "$DEEPSQL_SMOKE_WAIT_FOR_INIT" == "true" ]]; then
       exit 1
     fi
 
+    # Print only on change: enough to prove the run is alive and advancing,
+    # without 240 identical lines scrolling the earlier output away.
+    report="${init_stage:-?} ${init_progress:-0}% ${init_message:-}"
+    if [[ "$report" != "$last_report" ]]; then
+      echo "  [${SECONDS}s] ${init_stage:-unknown} ${init_progress:-0}%${init_message:+ — $init_message}"
+      last_report="$report"
+    fi
+
     sleep 5
   done