feat(examples): add 1-month age check for issue cleanup

Author: cocosheng-g

examples/workflows/issue-cleanup/README.md

@@ -7,7 +7,7 @@ This document describes a workflow to batch-process and clean up older open issu
 The Issue Cleanup workflow is designed to automate the triage of stale issues by using the Gemini CLI to:
 
 1. **Check for Staleness (Native)**: Identifies if an issue has been waiting for reporter feedback for over 7 days. If so, it closes the issue directly via a GitHub Action script to save AI resources.
-2. **Check for Vagueness (AI)**: If an issue is not stale but lacks sufficient information (e.g., reproduction steps), the agent asks the reporter for specific details and stops.
+2. **Check for Age and Vagueness (AI)**: If an issue is not stale but hasn't been updated in over a month, it asks the reporter to reproduce the issue with the latest build. If the issue lacks sufficient information (e.g., reproduction steps), it asks the reporter for specific details and stops.
 3. **Check Code Validity (AI)**: Determines if an issue is still relevant against the current codebase. The agent may attempt to write and execute a minimal reproduction script to verify if a bug has been resolved, or manually inspect the code. If verified as fixed, it will close the issue with an explanation.
 4. **Find Duplicates (AI)**: Checks if the issue has a more recent duplicate. If a duplicate exists, it closes the issue and links to the duplicate.
 5. **Summarize for Triage (AI)**: If an issue is still valid and unique, it provides a summary comment based on customizable instructions (e.g., categorizing it as `Maintainer-only` or `Help-wanted`). If no custom instructions are provided, it falls back to a standard triage summary.

examples/workflows/issue-cleanup/gemini-issue-cleanup.toml

@@ -8,13 +8,16 @@ You are an automated triage bot for the `!{echo $REPOSITORY}` repository. Your j
 
 ## Task Lifecycle
 
-### Step 1: Setup & Vagueness Check
+### Step 1: Setup, Age & Vagueness Check
 - Run `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`
-- Run `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,author,comments`
+- Run `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json title,body,author,comments,updatedAt`
+- **Age Check**: If the issue was last updated over 1 month ago (compare `updatedAt` to the current `date`):
+  - Ask the reporter: `gh issue comment !{echo $ISSUE_NUMBER} --body "@<reporter_username>, this issue hasn't been updated in over a month. Could you please try reproducing it with the latest build and let us know if it still occurs?" --repo !{echo $REPOSITORY}`
+  - **STOP EXECUTION IMMEDIATELY**.
 - **Vagueness Check**: If the issue description is fundamentally missing context (no logs, no repro steps, just "it's broken") AND no one has asked for more information yet:
   - Ask the reporter: `gh issue comment !{echo $ISSUE_NUMBER} --body "@<reporter_username>, thank you for the report! Could you please provide more specific details (e.g., reproduction steps, expected behavior, and environment)? Closing this as vague if no response is received in a week." --repo !{echo $REPOSITORY}`
   - **STOP EXECUTION IMMEDIATELY**.
-- If the issue is clear or the reporter has provided info, proceed to Step 2.
+- If the issue is clear, recent, or the reporter has provided info, proceed to Step 2.
 
 ### Step 2: Reproduction & Code Validity Check
 - If the issue describes a reproducible bug (e.g., a runtime error, unexpected output, or terminal behavior), you should write and execute a minimal test script using `node` to verify if the bug still occurs in the `target-repo/` codebase.