Offer to start Docker instead of stopping to ask someone to click an icon

Starting a daemon that is already installed changes nothing durable and needs
no root on macOS, and it is the commonest of the three Docker failures — the
check's own output says "installed, but the daemon is not up" more often than
it says anything else. Stopping the conversion there was friction with no
safety behind it, so `open -a Docker` (then waiting for it to answer) is now on
the list the assistant may run with approval, like the pip installs. Linux
needs sudo systemctl, so it stays on the other list.

The two that remain a stop now say WHY, because "it changes how the machine
works" is squeamishness and these are consequences:

- Docker Desktop carries commercial licensing terms — a paid subscription above
  a company-size and revenue threshold. Installing it on approval walks the
  owner into accepting a licence they never read. That is the same boundary as
  not filling in a submission form on someone's behalf.
- An in-place `brew upgrade node` can break every other Node project on the
  machine. Version managers exist because of exactly this. Offer the command
  and the warning together; let them take the risk knowingly.

The friction this answers is real but was never "it should just work" — stage
-3 exists so the stop happens in the first minute rather than at gate B after
two hours. What changed is that one of the three stops did not need to be one.

Fixed in R&D first and carried forward, per the runbook; the two copies were
identical and are again. Verified by stubbing `docker info` to fail: the
daemon-start line now appears under "these are user-local and need no root"
instead of under the list the user has to act on.

Author: BELNEM s.r.o

.claude-plugin/marketplace.json

@@ -14,7 +14,7 @@
       "source": "./",
       "displayName": "html2wp — HTML to WordPress",
       "description": "BETA. Convert a static HTML site into a standalone WordPress block theme, verified against the original at three viewport widths — and reviewed by you before handover. The conversion runs through a verified Astro 5 build, so the Astro project is a real output too — proven pixel-identical to the source before anything WordPress-shaped is generated.",
-      "version": "1.0.0-beta.24",
+      "version": "1.0.0-beta.25",
       "author": {
         "name": "BELNEM s.r.o.",
         "email": "hello@html2wp.dev",

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "html2wp",
   "description": "BETA. Convert a static HTML site — or anything that builds to one (Lovable, Bolt, v0, Next export) — into a standalone WordPress block theme: pixel-1:1, pages, blog, forms, menus, SEO and redirects, with no plugin required and verification gates at every stage. Every conversion ends in your own page-by-page review; the gates catch most fidelity drift, not all of it.",
-  "version": "1.0.0-beta.24",
+  "version": "1.0.0-beta.25",
   "author": {
     "name": "BELNEM s.r.o.",
     "email": "hello@html2wp.dev",

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "html2wp",
-  "version": "1.0.0-beta.24",
+  "version": "1.0.0-beta.25",
   "description": "Convert static HTML or buildable web projects into verified, editable WordPress block themes.",
   "author": {
     "name": "BELNEM s.r.o.",

VERSION

@@ -1 +1 @@
-1.0.0-beta.24
+1.0.0-beta.25

skills/html2wp/SKILL.md

@@ -285,11 +285,27 @@ on Debian and Homebrew Python), do not reach for `--break-system-packages`:
 make a virtualenv, tell the user where it is, and use its `python3` for the
 rest of the conversion.
 
-**The machine list — say what is needed and stop.** Docker Desktop, a Node
-upgrade, starting the Docker daemon. These change how the machine works and
-they are not yours to decide. Print them, wait, and re-run the check when the
-user says they are done. Installing Docker for someone who did not ask is not
-helpfulness.
+**Starting a Docker daemon that is already installed is on the first list**,
+on macOS, where it needs no root: `open -a Docker`, then wait for it to answer.
+It is the commonest of the three Docker failures and it changes nothing
+durable, so stopping the conversion to ask someone to click an icon was
+friction with no safety behind it. On Linux it needs `sudo systemctl`, so it
+stays below.
+
+**The machine list — say what is needed and stop.** Two things, and the reason
+matters more than the rule, because "it changes the machine" is squeamishness
+while these are consequences:
+
+- **Installing Docker Desktop.** It carries commercial licensing terms — a
+  paid subscription above a company-size and revenue threshold. Installing it
+  on approval walks the owner into accepting a licence they never read, which
+  is not yours to do on their behalf however cheerfully they said yes.
+- **Upgrading Node.** An in-place `brew upgrade node` can break every other
+  Node project on that machine; version managers exist because of exactly
+  this. Offer the command and the warning together, and let them run it
+  knowing what it risks.
+
+Print them, wait, and re-run the check when the user says they are done.
 
 Then re-run the script and require exit 0 before stage -2. A conversion that
 starts without these does not fail fast — it fails at stage 5 or 6, after the

skills/html2wp/VERSION

@@ -1 +1 @@
-1.0.0-beta.24
+1.0.0-beta.25

skills/html2wp/assets/scripts/check-prereqs.sh

@@ -123,7 +123,16 @@ if command -v docker >/dev/null 2>&1; then
     fi
   else
     row "Docker" "NOT RUNNING" "installed, but the daemon is not up"
-    MISSING_USER+=("Start Docker$( [ "$PLATFORM" = macos ] && echo ' Desktop' ) and wait for it to report running")
+    # Starting a daemon that is ALREADY INSTALLED changes nothing durable, needs
+    # no root on macOS, and is the commonest of the three Docker failures — so
+    # it is the assistant's to offer, like the pip installs. Installing Docker
+    # is a different question and stays below.
+    if [ "$PLATFORM" = macos ]; then
+      MISSING_AGENT+=("open -a Docker && printf 'waiting for the Docker daemon' && until docker info >/dev/null 2>&1; do printf .; sleep 2; done; echo ' up'")
+    else
+      # systemctl needs root, so this one is still the user's to run.
+      MISSING_USER+=("Start the Docker daemon: sudo systemctl start docker")
+    fi
   fi
 else
   row "Docker" "MISSING" "gates B and C run WordPress in a throwaway container"