Pre-build SSH command for change detection and early abort

Summary Add the ability to run a server-side SSH command as the very first step in the deploy chain — before the build process runs — so that deployments can be aborted early based on the state of the remote server.

Background We use DeployHQ to manage deployments and keep environments in sync across all of our client projects. A recurring challenge is that clients sometimes make changes directly on their live sites (e.g. configuration tweaks, content updates, plugin/theme adjustments). When that happens, we need to pull those changes down before deploying, otherwise our deploy will overwrite the client's work.

The problem Today, the earliest hook we have for running a server command is the Pre-deployment command, which only fires after the build process has completed. This means:

• We can't check the state of the server before spending time and resources on a build.

• If we detect changes that need to be downloaded first, we've already wasted a full build cycle.

• Aborting at that point is later than ideal in the workflow.

Proposed solution Introduce a new step at the very beginning of the deploy chain — for example, a "Pre-build SSH command" — that runs against the target server before the build kicks off. This command could:

• Detect uncommitted or out-of-sync changes on the remote site.

• Exit with a non-zero status to abort the deploy cleanly and early, before any build runs.

• Optionally surface a clear message in the deploy log explaining why the deploy was halted.

Benefits

• Saves build minutes and compute on deployments that shouldn't proceed.

• Keeps the existing Pre-deployment command intact for steps that genuinely need to run after the build.