test(logseq-cli): match the doctor status table in the help check

`logseq-cli doctor` prints a per-check status table with no summary line; the OCaml CLI has no "Doctor: ok" string
(absent from cli/lib/doctor.ml and the rendered output). The help check grepped for that phantom substring, so it
failed even though doctor exited 0 with every check ok. The branch never built far enough to run this check before, so
the assertion was never validated.

Assert the stable db-worker-script check row instead, preserving the guard against a degenerate banner that exits 0
without rendering the real table.

Author: Bad3r

modules/_checks/cli-help.nix

@@ -36,8 +36,12 @@ pkgs.runCommand "logseq-cli-help-check" { } ''
     echo "$doctor_output" >&2
     exit 1
   fi
-  if ! echo "$doctor_output" | ${pkgs.gnugrep}/bin/grep -qF 'Doctor: ok'; then
-    echo "logseq-cli doctor output missing expected 'Doctor: ok' substring:" >&2
+  # doctor prints a status table (one row per check), not a summary line; on
+  # success every row is `ok` and the command exits 0 (gated above). Require the
+  # db-worker-script check row so a degenerate banner that exits 0 without
+  # running the real checks is not rubber-stamped.
+  if ! echo "$doctor_output" | ${pkgs.gnugrep}/bin/grep -qF 'db-worker-script'; then
+    echo "logseq-cli doctor output missing expected 'db-worker-script' check row:" >&2
     echo "$doctor_output" >&2
     exit 1
   fi