ReDock 0.4.0

• Buttons say what they do. "Create WordPress", "Claim the name", "Delete
  images" — instead of a label that grew and shifted as you typed a name into
  the field above it.
• A live site's debug log can be switched on from ReDock and read in its Logs
  tab. ReDock edits the site's wp-config.php for you, keeps a copy of the
  original, and can put it back. The live site needs ReDock Connect 1.5.0 or
  newer — the one-click update on its Connection tab does that.
• The AI agent's screens are split the way you use them: an "AI permissions"
  tab for what the AI may do on a site, and the conversation on its own. Chat
  text can be selected and copied. The message box grows as you type, can be
  resized by hand, and remembers the size you gave it.
• The update banner is a popup now. "What's new" shows the notes for every
  update before you take it, and when you are already on the latest version it
  shows the notes for the version you have.
• Copying a live WordPress site is a different thing now. Instead of dragging
  it down file by file — thousands of separate requests, and a big video that
  died at 490 MB of 500 starting again from zero — the live site packs itself
  into one archive on its own disk, and ReDock brings that down in pieces that
  pick up at the exact byte if your connection drops. On the test site that is
  185 requests down to 52.
• Sites whose ReDock Connect plugin is older still copy exactly as before, and
  the wizard says so rather than leaving you guessing why it is slow. Updating
  the plugin on the live site is the one-click button already on its Connection
  tab.
• Backups are real backups. A backup is now a dated folder holding the site's
  files, its database, and a sheet of checksums that proves both — not just the
  database. ReDock keeps the last five per site and says so on screen before it
  removes the sixth.
• "Back up now" works on any WordPress site, whether or not it came from a live
  one, and a copy pulled from live keeps its archive as the first backup for
  free.
• If a site's media was left on the live site, its backup offers to go and get
  it — on by default, with the size shown before you commit. Turn it off and
  the backup says, in words, that the media is not in it.
• You can restore a backup over the site it came from — after ReDock takes a
  safety backup of what is there now — or turn it into a brand new site and
  leave the original untouched.
• Fixed: database backups could be taken and then refused to restore. That
  affected the old database snapshots too, and both are fixed.
• Refreshing a site from live asks what you want first. Incremental brings down
  only the files that changed — the quick one, and now the default — while Full
  downloads the whole site again for an exact copy. Each says what it costs you:
  Incremental cannot notice a file you deleted on the live site, so that file
  stays on this Mac.
• Fixed: a backup with nowhere to go now says so before it starts. ReDock
  checks there is room first and refuses in plain numbers — how much it needs,
  how much you have — instead of running for twenty minutes, filling the disk
  and leaving you with neither the backup nor the space to try again.
• Fixed: the new-site wizard could tell you to install PHP when PHP was already
  installed. It was showing that the moment it opened — before it had finished
  looking — and if the check failed it never looked again. It now says what it
  is doing, and offers to try again if it could not find out.
• Fixed: the web server no longer restarts itself over and over. ReDock decides
  whether it needs restarting by comparing the configuration it wants against
  the one the running server loaded — and that comparison was moving on its own
  whenever a public share link had come and gone, so the answer was always
  "restart it". In every log we have, the check had never once come back
  "already correct".
• Fixed: a site that is simply slow to answer after starting is no longer
  reported as a broken web server. WordPress can take a few seconds to serve
  its first page; ReDock now says that site had not answered yet, instead of
  telling you to restart a web server that was working the whole time.
• Fixed: ReDock's own health checks no longer fill the web server's log with
  errors. Each check used to hang up as soon as it had its answer, and the web
  server wrote that down as a failure every time. It reads to the end now.
• Fixed: two sites starting at the same moment could be handed the same port,
  and the second one would quietly fail to come up and fall back to serving its
  files instead of running. Ports are now claimed at the instant they are
  chosen.