ReDock 0.4.1

• ReDock now works on a Mac that already runs Local by Flywheel, Herd, Valet,
  MAMP or a Docker stack. It used to show everything green while nothing opened:
  the other app owned port 443, so browsers reached its server instead of yours,
  and every check ReDock made asked its own ports and got a happy answer.
• When another app is holding the port, ReDock says so on Home and in Settings —
  it names the app, says its own web server is fine behind it, and gives you the
  other app's own fix when it knows one.
• One button switches ReDock to its own ports, and your sites open again
  straight away. Their addresses gain the port; nothing about the sites, their
  files or their databases changes, and you can switch back whenever the other
  app is gone.
• ReDock can quit the other app for you when it recognises it, or stop an
  unrecognised program after showing you exactly which one — and when the
  program belongs to the system it says so instead of offering a button that
  would not work.
• There is a switch in Settings → Local HTTPS for people who already know they
  run another local-server app, so the notice never appears.
• If the ports ReDock itself uses are taken, it moves to the next free ones,
  remembers them, and says which ones it is on and who took the old ones.
  Everything follows on its own.
• New in Settings → Advanced: "Check my setup" looks at every door your sites
  depend on and tells you, per site, what a browser opening it would actually
  reach. You can copy the report or send it to ReDock in one press with a short
  reference to quote back.
• A site that another app is answering for says so, instead of "nothing answered
  on the address" — something did answer, it just was not ReDock.
• The AI agent no longer fails on sites when another app holds port 443 — it
  talks to your sites over a path that never leaves this Mac.
• Sites with the AI features switched off no longer report an error about it.
  Nothing was wrong; it was a switch that was off.