[product-manager-impersonator] Expose no-op workflow_call outputs for scheduled workflows #663

Feature Idea

Summary: Add noop_message as a top-level workflow_call output in gh-aw-scheduled-audit and gh-aw-scheduled-fix so callers can branch cleanly on intentional no-op outcomes.

Why a Customer Would Want This

Teams chaining detector/fixer workflows already branch on created_issue_number / created_pr_number, but they currently can’t distinguish “healthy no-op” from “nothing created yet” without digging into internals. Exposing no-op status as workflow outputs makes orchestration more reliable and reduces brittle custom logic in downstream repos.

Rough Implementation Sketch

• Add noop_message output to on.workflow_call.outputs in .github/workflows/gh-aw-scheduled-audit.md and .github/workflows/gh-aw-scheduled-fix.md.
• Wire those outputs from existing conclusion-job outputs (jobs.conclusion.outputs.noop_message).
• Recompile lock files so .lock.yml artifacts expose the new outputs.
• Update chaining docs/examples (upgrading/chaining docs) to show conditional branches based on noop_message.

Why It Won't Be That Hard

The no-op value is already produced internally by both workflows; this is mostly output plumbing plus docs. It follows the same pattern recently used for created issue/PR outputs, so implementation surface area is small.

Evidence

• .github/workflows/gh-aw-scheduled-audit.lock.yml:85-91 exposes only created_issue_* outputs today.
• .github/workflows/gh-aw-scheduled-audit.lock.yml:1311-1313 already has internal noop_message in jobs.conclusion.outputs.
• .github/workflows/gh-aw-scheduled-fix.lock.yml:84-90 exposes only created_pr_* outputs today.
• .github/workflows/gh-aw-scheduled-fix.lock.yml:1298-1301 already has internal noop_message in jobs.conclusion.outputs.
• docs/upgrading.md:11-13 and docs/upgrading.md:28-33 show current output-based chaining direction, making this a natural extension.

Non-duplicate Check

Compared against open PM-impersonator issues (#650, #619, #570, #562, #523, #577, #554, #449, #409, #403, #382) and related output/no-op issues (#476, #605, #448). None request exposing noop_message as workflow_call outputs for scheduled workflows.

What is this? | From workflow: Trigger Product Manager Impersonator

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.