chore(Automation): Auto-close daily status reports

[rllyy97]

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

Our automated daily status report issues are flooding our open issue logs.
This will auto-close any that are over a day old since there will be a new one to take it's place.

Impact of Change

• Users: N/A
• Developers: Our open issues will not be flooded with daily status reports
• System:

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

** GH issue automation, testing not needed **

Contributors

@rllyy97

Screenshots/Videos

N/A

[Copilot]

Pull request overview

This PR adds GitHub Actions automation to close daily-status issues after they’ve been open for more than a day, reducing noise in the open-issues backlog.

Changes:

• Add an actions/stale@v4 step scoped to daily-status labeled issues
• Mark eligible daily-status issues stale immediately and close them after 1 day
• Limit the number of operations per run for this new step

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(Automation): Auto-close daily status reports
• Issue: None — the title is clear, concise, and follows conventional-commit style.
• Recommendation: (Optional) For strictly consistent formatting across the repo you may prefer a lowercase scope, e.g. chore(automation): auto-close daily status reports, but this is not required.

---

✅ Commit Type

• Properly selected (chore).
• Only one item is selected which is correct.

---

✅ Risk Level

• The PR body selects Low and the PR has the label risk:low applied. This matches the change in the diff (a small workflow addition) and is appropriate.

---

✅ What & Why

• Current: "Our automated daily status report issues are flooding our open issue logs. This will auto-close any that are over a day old since there will be a new one to take it's place."
• Issue: None — the explanation is brief and adequate for this change.
• Recommendation: (Optional) You could add one sentence clarifying who/what currently creates the daily-status label (bot/workflow) so reviewers know label assignment is automated.

---

⚠️ Impact of Change

• The Impact section is partially filled (Users and Developers are described; System is left blank).
• Recommendation: Add a one-line System entry to explicitly state there are no performance/architecture changes and to call out workflow runtime/permissions. Example suggestions to add:
  • Users: N/A — this only affects issue visibility for maintainers.
  • Developers: Reduces noise in the open issues list for maintainers and contributors.
  • System: No runtime performance or architecture changes. The workflow uses the repo's GITHUB_TOKEN and will run within the existing .github/workflows/ISSUE_MANAGEMENT.yml job; it performs up to 100 operations per run.

---

✅ Test Plan

• Assessment: The PR marks manual testing completed and includes a note: "GH issue automation, testing not needed." Given this change modifies GitHub Actions issue management and does not touch runtime application code, manual testing / verification of the workflow behavior is reasonable.
• Recommendation: If you ran the workflow manually (or in a dry-run staging repo) include a short note describing how you validated it (e.g. "Verified in test repo that issues labeled daily-status are closed after 1 day by the workflow"). This helps reviewers reproduce/confirm behavior quickly.

---

✅ Contributors

• Assessment: Contributors section includes @rllyy97. Good — credit provided.

---

✅ Screenshots/Videos

• Assessment: N/A — not applicable to a non-UI automation change.

---

Summary Table

Section	Status	Recommendation
Title	✅	(Optional) Consider lowercase scope for consistency
Commit Type	✅	None
Risk Level	✅	None
What & Why	✅	(Optional) note source of daily-status label
Impact of Change	⚠️	Add a short System line explaining no perf/arch impact and mention operations-per-run / permissions
Test Plan	✅	(Optional) add one-line validation steps if you executed the workflow in a test repo
Contributors	✅	None
Screenshots/Videos	✅	None

---

Additional notes

• The code diff adds an actions/stale@v4 step configured to only target issues labeled daily-status, marking them stale immediately and closing them after 1 day. This is a small, repository-maintenance workflow change and the advised risk level is Low — matching the PR label.
• I noticed the needs-pr-update label is still applied to this PR. If you consider the PR ready, please remove that label so maintainers know no further updates are expected.

Final: Please add the single-line System impact note suggested above and (optionally) a short note in Test Plan describing how you validated the workflow in a test run. Once updated, this PR is good to merge.

---

Please update the PR title/body if you want to incorporate the optional suggestions, then re-submit or remove the needs-pr-update label when ready. Thank you for helping keep the repository tidy!

---

Last updated: Thu, 19 Mar 2026 18:40:33 GMT

[github-actions]

📊 Coverage Check

No source files changed in this PR.