[project-summary] Project Summary - 2026-09-25 #2177

Project Summary

Period: 2026-09-23 to 2026-09-25

Non-bot activity was very light during this window (0 non-bot commits, 0 non-bot new issues, 0 non-bot new PRs, 0 non-bot merged PRs), but there are long-stale human-authored items that still need triage.

🎯 Easy Pickings

• #2159 — timezone-aware --since filter fix in fetch-workflow-logs is open as a draft and appears narrowly scoped; promote to ready-for-review or close if superseded.
• #2164 — utility-script hardening (requests + structural PyYAML edits) is open as a draft and includes targeted tests; decide whether to review/merge or supersede.

🔄 Stale Items

• #811 — "CodeRabbit and GitHub actions both react to /ai command, causing duplicate work" (last updated 2026-03-26).
• #815 — "Automation runs on closed PRs" (last updated 2026-03-26).
• #816 — "[kibana-flaky-test-triage] On-demand workflow to triage failed-test issues by team" (last updated 2026-03-26).

Chronicle Next Steps

1. Triage stale human-authored issues CodeRabbit and GitHub actions both react to /ai command, causing duplicate work #811, Automation runs on closed PRs #815, and [kibana-flaky-test-triage] On-demand workflow to triage failed-test issues by team #816: confirm relevance, then close with rationale or re-scope with an owner.
2. Decide disposition for draft fixes Fix timezone-aware --since filtering in fetch-workflow-logs #2159 and Fix workflow utility scripts to use requests and structural PyYAML edits #2164 (promote for review vs. close/supersede) to avoid accumulating unattended draft PRs.

What is this? | From workflow: Trigger Project Summary

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

• expires on Oct 2, 2026, 9:14 AM UTC