Clarify direct safe-output usage in Daily Compiler Quality Check

[Copilot]

The Daily Compiler Quality Check could complete successfully without producing any recorded safe outputs. In the failing run, the agent invoked safeoutputs through bash, which bypassed the normal safe-output capture path and left the workflow with an empty result.

• Root cause

  • The workflow prompt allowed an ambiguous execution path: the agent could create the discussion via shell instead of calling the safe-output tool directly.
  • When discussion creation did not produce a recorded safe output, the prompt did not make the noop fallback explicit enough for this failure mode.

• Prompt contract changes

  • Require create_discussion and noop to be called directly as safe-output tools.
  • Explicitly forbid invoking safe outputs via bash, shell, or safeoutputs ... CLI commands.
  • Preserve the existing “single discussion” behavior when a valid report is available.
  • Add a required noop fallback when a valid discussion body cannot be produced.

• Documentation in the workflow

  • Added direct tool-call examples for both create_discussion and noop to make the expected invocation pattern unambiguous.

• Compiled workflow

  • Regenerated the lock file so the updated prompt contract is reflected in the executable workflow.

Example of the new expected pattern:

{"title":"Daily Compiler Code Quality Report - YYYY-MM-DD","category":"audits","body":"...full markdown report..."}

Fallback when no valid discussion should be created:

{"message":"No discussion created: [brief explanation]"}

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the daily compiler quality workflow instructions to require direct safe-output tool calls, and regenerates gh-aw lock metadata to reflect the updated prompt content.

Changes:

• Clarify the output contract to require direct create_discussion / noop tool calls (and forbid invoking safe outputs via shell/CLI).
• Add examples for direct tool calls in the daily compiler quality workflow markdown.
• Regenerate .lock.yml workflow lockfiles (updated body_hash metadata).

Show a summary per file

File	Description
.github/workflows/smoke-copilot.lock.yml	Regenerated gh-aw lock metadata (body_hash) after prompt/content changes.
.github/workflows/daily-compiler-quality.md	Tightens output contract to require direct tool calls and adds illustrative examples.
.github/workflows/daily-compiler-quality.lock.yml	Regenerated gh-aw lock metadata (body_hash) after prompt/content changes.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 3/3 changed files
• Comments generated: 1