When running a LiquibaseCommand step with the status command, the verbose output (including how many changesets are pending against the target database) only appears in the step's console log. There's no way to capture that information as a pipeline output variable or a written file, so it can't be used in downstream steps for gating, notifications, or audit trails.

We'd like the LiquibaseCommand step to expose its output the same way the DB Schema Apply step already exposes applied changesets as an output variable. This would let teams programmatically check pending changes before proceeding, without having to parse raw console logs.