wback 7.3.1

[7.3.1] - 2026-08-25

Fixed

• app:validate no longer stops at the first check whose command will not start.
  A command that cannot be spawned at all — an unreadable working directory does
  this to every one of them — is now a failed check like any other, so the
  remaining binaries, and the paths, sites, remotes, logging and summary after
  them, are still reported. This happened on ap1: one run ended at mysqldump
  and looked at nothing else, which is the worst moment to stop talking for a
  command whose whole job is to say what is wrong.
• A check that cannot start now reports the cause rather than the first line of
  the exception. proc_open(): posix_spawn() failed: Permission denied (working directory: /root) says what to fix; The command "…" failed. repeats the
  check's own label. The whole message still goes to the log, with the check and
  the command as context.

Changed

• A file backup of an empty source directory now fails as an empty source
  directory, rather than as zip exit code 12 and "Nothing to do!". An
  unexpectedly empty docroot is worth failing over — it is what a half-finished
  migration looks like at 03:17 — but it should say so in the site's terms and
  name the site it belongs to. A site that deliberately has nothing to archive
  still opts out with files = ''.

Documentation

• The README now says that one site failing does not stop the others, which was
  the undocumented half — a failed stage not stopping the ones after it was
  already written down. A Skipping [cloud] line is only ever --no-cloud,
  never the consequence of an earlier failure, and that is now stated where
  someone reading a bad night's log will find it.
• The installation section no longer promises a SHA256SUMS on every release
  without one existing. 7.0.0, 7.1.0 and 7.2.0 have been given one after the
  fact — checked against the published assets rather than against a local build
  — so the documented check now works for every 7.x release, not just the newest.