Is your feature request related to a problem?

The deploy-deployer.yml reusable workflow currently has no declared outputs. All Deployer task output (info, warnings, errors) is only visible in CI logs. Calling workflows cannot pass deployment results to downstream jobs, which reduces log visibility.

Describe the desired solution

After the "Run Deployer" step, add a step that captures Deployer's stdout and parses out info and warning messages. Expose them as workflow_call outputs, so calling workflows can eventually use them in downstream jobs.

Describe the alternatives that you have considered

• Artifacts: Have Deployer write a notices file, upload it as an artifact, and download it in a follow-up job. This works but adds complexity (artifact upload/download steps) compared to simple workflow outputs.
• Deployer writes directly to $GITHUB_OUTPUT: The deploy task could write to the GitHub Actions output file from PHP. This is fragile, couples Deployer recipes to CI internals, and requires every project to implement it individually.

Additional context

Real-world example — recently, we executed a task that warns when a WP CLI command is not available. The deployment succeeds, but the warning is buried in logs. We'd like our calling workflow to pick it up and include it in a Slack notification sent by a separate job.

Code of Conduct

• I agree to follow this project's Code of Conduct