[q] fix(daily-repo-chronicle): move discussion category to announcements

[github-actions]

Summary

Moves the daily-repo-chronicle workflow's created discussions from the default category to the Announcements category, as requested by @pelikhan.

Change

In .github/workflows/daily-repo-chronicle.md, added category: "announcements" to the create-discussion safe-output configuration:

safe-outputs:
  upload-asset:
  create-discussion:
    expires: 3d
    category: "announcements"   # ← added
    title-prefix: "📰 "
    close-older-discussions: true

Why

The Repository Chronicle is a high-visibility daily newspaper-style report that deserves placement in the Announcements category rather than being mixed in with audit reports.

Validation

Compiled successfully with gh aw compile:

• ✅ daily-repo-chronicle — no errors or warnings

• Fixes 📰 Repository Chronicle — 68 PRs Merged in a Single Day as Team Storms Into Thursday #16866

AI generated by Q

• expires on Feb 21, 2026, 9:34 PM UTC

---

Note

This was originally intended as a pull request, but the git push operation failed.

Workflow Run: View run details and download patch artifact

The patch file is available in the agent-artifacts artifact in the workflow run linked above.

To apply the patch locally:

# Download the artifact from the workflow run https://github.com/github/gh-aw/actions/runs/22200687087
# (Use GitHub MCP tools if gh CLI is not available)
gh run download 22200687087 -n agent-artifacts

# The patch file will be at agent-artifacts/tmp/gh-aw/aw.patch after download
# Apply the patch
git am agent-artifacts/tmp/gh-aw/aw.patch

Show patch preview (59 of 59 lines)

From 051d59196a358fdd32ec0e809cd33e8abe7c137d Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions@github.com>
Date: Thu, 19 Feb 2026 21:28:42 +0000
Subject: [PATCH] fix(daily-repo-chronicle): move discussion category to
 announcements

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 .github/workflows/daily-repo-chronicle.lock.yml | 6 +++---
 .github/workflows/daily-repo-chronicle.md       | 1 +
 2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/daily-repo-chronicle.lock.yml b/.github/workflows/daily-repo-chronicle.lock.yml
index 74f3db6..8a7c866 100644
--- a/.github/workflows/daily-repo-chronicle.lock.yml
+++ b/.github/workflows/daily-repo-chronicle.lock.yml
@@ -30,7 +30,7 @@
 #     - shared/reporting.md
 #     - shared/trends.md
 #
-# gh-aw-metadata: {"schema_version":"v1","frontmatter_hash":"24c95e05db9b5423bcdcb99e38fa604774d272c1647b66dd4ab4fcf2f5d1feb1"}
+# gh-aw-metadata: {"schema_version":"v1","frontmatter_hash":"d21247582c90694ba02e48d0848e944097f89cee7bb36bbae2ab756246b38218"}
 
 name: "The Daily Repository Chronicle"
 "on":
@@ -434,7 +434,7 @@ jobs:
           cat > /opt/gh-aw/safeoutputs/tools.json << 'GH_AW_SAFE_OUTPUTS_TOOLS_EOF'
           [
             {
-              "description": "Create a GitHub discussion for announcements, Q\u0026A, reports, status updates, or community conversations. Use this for content that benefits from threaded replies, doesn't require task tracking, or serves as documentation. For actionable work items that need assignment and status tracking, use create_issue instead. CONSTRAINTS: Maximum 1 discussion(s) can be created. Title will be prefixed with \"📰 \".",
+              "description": "Create a GitHub discussion for announcements, Q\u0026A, reports, status updates, or community conversations. Use this for content that benefits from threaded replies, doesn't require task tracking, or serves as documentation. For actionable work items that need a
... (truncated)