Route pdf-summary discussions to Audits category

[Copilot]

Agent-generated report discussions were scattered across Audits (31), Announcements (29), and General (25) categories. When no category is configured, resolveCategoryId falls back to "Announcements" — so uncategorized workflows silently land there instead of "Audits".

Changes

• pdf-summary.md: Added category: "audits" to the create-discussion safe-outputs config — the only workflow with a create-discussion handler config missing an explicit category.
• pdf-summary.lock.yml: Recompiled to reflect the updated config.

# Beforesafe-outputs:
create-discussion:
expires: 1dmax: 1# Aftersafe-outputs:
create-discussion:
expires: 1dcategory: "audits"max: 1

All other audit/analysis workflows (including repository-quality, security-observability, geo-optimizer, terminal-stylist) already route to Audits via the shared/daily-audit-discussion.md import chain.

[github-actions]

Hey @Copilot 👋 — thanks for picking up the Audits category routing task from issue #44063! Standardizing create-discussion configs across the audit/analysis report workflows is exactly the right kind of corpus-hygiene fix.

This PR was just opened and currently has 0 changed files, so a few things to address once the implementation lands:

• Add a description — once the workflow config edits are in, update the PR body to list which workflows were changed and what create-discussion field was updated (e.g. category: Audits). Reviewers need to know which workflows were touched without diffing manually.
• Add tests or validation — if any of the affected workflows have test fixtures, snapshot files, or schema-validation steps, include coverage for the category field change. Even a note explaining why no tests apply would help reviewers.

If you'd like a hand finishing this up, you can assign this prompt to your coding agent:

Complete the implementation for PR #44092 in github/gh-aw.
Goal: standardize all agentic audit/analysis report workflows (e.g. repository-quality, security-observability, geo-optimizer, terminal-stylist) to post discussions into the "Audits" category by updating their `create-discussion` config field.
Steps:
1. Search for all workflow YAML files under .github/workflows/ that include a `create-discussion` step or config block.
2. For each file that is an audit/analysis report workflow but does NOT already set `category: Audits` (or equivalent), update it to do so.
3. Update the PR body with a summary of which files were changed and what field was updated.
4. If test fixtures or schema snapshots exist for these workflows, update them to reflect the new category value.

Generated by ✅ Contribution Check · 122 AIC · ⌖ 17.8 AIC · ⊞ 6.2K · ◷

[github-actions]

🤖 Triage Assessment

Field	Value
Category	chore
Risk	🟢 Low
Score	30/100 (Impact 10 + Urgency 8 + Quality 12)
Action	defer (draft)

Summary: Routes pdf-summary discussions to Audits category. Draft. Small config change (+7/−6, 2 files). No CI triggered.

Next: Convert to ready-for-review when tested.

Generated by 🔧 PR Triage Agent · 97.9 AIC · ⌖ 12.4 AIC · ⊞ 5.4K · ◷

[Copilot]

Pull request overview

This PR ensures the pdf-summary workflow’s create-discussion safe-output explicitly routes generated discussions to the Audits category, avoiding the current fallback behavior that places uncategorized discussions into Announcements.

Changes:

• Added category: "audits" to safe-outputs.create-discussion in pdf-summary.md.
• Recompiled pdf-summary.lock.yml so the generated safe-outputs handler config and tool descriptions include the Audits category routing.

Show a summary per file

File	Description
.github/workflows/pdf-summary.md	Sets create-discussion safe-output category to "audits" so discussions land in Audits rather than the fallback category.
.github/workflows/pdf-summary.lock.yml	Updates the generated workflow to reflect the new create_discussion.category setting and related generated metadata/config.

Review details

Tip

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

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Low

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.82.4