ReDock 0.4.3

• If MySQL's main download site stops carrying the version ReDock uses, the
  install now fetches the identical file from MySQL's permanent archive by
  itself — same file, same integrity check, no dead end.
• A new WordPress site needs one thing: a name. The admin login is filled in for
  you (and the email follows the name as you type, until you change it), and
  anything this Mac is missing — PHP, the database — becomes a checked line that
  says "ReDock will set this up for you" and then does, with progress for each
  step. Nothing sends you off to another screen first any more.
• WordPress and ReDock's AI connection are on from the start. A fresh install is
  a working WordPress app rather than three switches you have to find. Both are
  still switches: Settings → Capabilities turns either back off.
• Once local HTTPS is set up on your Mac, ReDock's web server comes up with the
  app — and right after first-run setup, so the first site you open works
  without a restart. Nothing else starts with it: no sites, no PHP, no database.
• When the database won't start, ReDock now tells you what the DATABASE said,
  not just that it couldn't connect. It reads the engine's own log and shows its
  last lines — on the screen where it failed, in that site's log, and in the
  report you can send.
• ReDock sets up the database the first time it is used, and checks that it
  worked. An empty database folder used to fail silently thirty seconds later
  with "connection refused".
• "Check my setup" gained a Database section: which engine, its version, whether
  it is answering, where its files are, whether they have been set up, and — when
  something is wrong — what it said, with a Start button.
• Every "isn't running" message now carries its own fix and stops pointing at the
  wrong thing. Opening a site while the web server is down used to say local
  HTTPS networking was off, and offer a password that could not help; it now says
  the web server isn't running and starts it.
• Every kind of site installs what it needs while it is being created. PHP, Node,
  Python, n8n, Bun, Playwright, Firecrawl, the image server, Video studio and a
  video project all used to stop and send you to the Runtimes screen when the
  thing they run on wasn't installed; now each one names the version it will
  fetch, keeps Create pressable, and installs it as the first step you watch.
  Copying a live WordPress site does the same instead of refusing at the very
  end, and so does asking the AI agent to make you a site.
• ReDock has its own database now. On a Mac with nothing installed it downloads
  MySQL from its makers — once, about 167 MB, and it tells you the size before it
  starts — sets it up, and runs it for you. One database server for all your
  sites, on its own port, with its own files, started when your sites need it and
  stopped with them.
• If you already have a database, ReDock uses that one and says so. Nothing is
  installed, nothing is moved, and your existing sites carry on exactly where
  they are. If the one you have won't start, ReDock shows you what it said and
  offers one button to use its own instead — your database is left untouched.
• Any site can move its data between the two, from its own Database tab. ReDock
  backs the site up first, copies it across, points the site at the new one, and
  leaves the old copy exactly where it was.
• "Check my setup" now lists both, tells you which is which in plain words, and
  says which of your sites are on each.