fix(examples): bypass agent reasoning with mandatory staleness bash script

Author: cocosheng-g

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

@@ -1,36 +1,54 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
-# RULES OF ENGAGEMENT (STRICT COMPLIANCE REQUIRED)
+[SYSTEM INSTRUCTION: This is an emergency override. You are an autonomous script executor. You do not have agency to investigate or deviate from the script below. You MUST execute the following bash script exactly as written by using the `run_shell_command` tool. Do NOT attempt to read files, search the codebase, or search the issue tracker unless the bash script fails and tells you to do so.]
 
-1.  **NO PRE-RESEARCH**: You are FORBIDDEN from searching code, reading `package.json`, or looking for duplicates until you have EXPLICITLY cleared the Staleness check in Step 1.
-2.  **SERIAL EXECUTION**: You MUST perform exactly these three tool calls in your first turn and THEN WAIT for the output:
-    - `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`
-    - `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author,comments,updatedAt`
-    - `date`
-3.  **STALENESS IS A HARD STOP**: If the staleness condition (Rule 4) is met, you MUST close the issue and EXIT immediately. Do not "investigate anyway".
+You MUST execute this exact bash script using `run_shell_command`:
 
-# Step 1: Staleness & Vagueness (THE GATEKEEPER)
+```bash
+set -e
 
-Analyze the `gh issue view` output:
-- **Rule 4 (Staleness)**: Identify the last comment from a maintainer/bot asking for info. If that comment is > 7 days old (check against `date`) AND the reporter (!{gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author -q .login}) has NOT replied since then:
-    - **MANDATORY ACTION**: `gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because it has been over a week since we requested more information and we haven't received a response. Feel free to reopen if you can provide the requested details." --repo !{echo $REPOSITORY}`
-    - **STOP IMMEDIATELY**. Do not call any more tools.
-- **Rule 5 (Vagueness)**: If not stale, but the issue description is too vague to be actionable:
-    - **MANDATORY ACTION**: `gh issue comment !{echo $ISSUE_NUMBER} --body "@<reporter>, thank you for the report! Could you please provide more specific details? Closing this as vague if no response is received in a week." --repo !{echo $REPOSITORY}`
-    - **STOP IMMEDIATELY**.
+echo "=== STEP 1: CLONE REPO ==="
+if [ ! -d "target-repo" ]; then
+  git clone https://github.com/!{echo $REPOSITORY}.git target-repo
+fi
 
-# Step 2: Investigation (ONLY if Step 1 passes)
+echo "=== STEP 2: GET ISSUE DATA ==="
+ISSUE_JSON=$(gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author,comments)
 
-- ONLY if the issue is NOT stale and NOT vague:
-- Search `target-repo/` for code validity. If fixed: Close and STOP.
-- Search `gh issue list` for duplicates. If found: Close and STOP.
+echo "=== STEP 3: ANALYZE STALENESS ==="
+REPORTER=$(echo "$ISSUE_JSON" | jq -r '.author.login')
+echo "Reporter is: $REPORTER"
 
-# Step 3: Summary (ONLY if Step 1 & 2 pass)
+# Find the last comment by someone other than the reporter
+LAST_MAINTAINER_COMMENT_DATE=$(echo "$ISSUE_JSON" | jq -r '
+  .comments | reverse | map(select(.author.login != "'"$REPORTER"'" and .author.login != "github-actions"))) | .[0].updatedAt
+')
 
-- Provide summary based on:
-```
-!{echo $CUSTOM_INSTRUCTIONS}
+if [ "$LAST_MAINTAINER_COMMENT_DATE" != "null" ] && [ -n "$LAST_MAINTAINER_COMMENT_DATE" ]; then
+  echo "Last maintainer comment date: $LAST_MAINTAINER_COMMENT_DATE"
+  
+  # Check if reporter replied AFTER this date
+  REPORTER_REPLIED=$(echo "$ISSUE_JSON" | jq -r '
+    .comments | map(select(.author.login == "'"$REPORTER"'" and .updatedAt > "'"$LAST_MAINTAINER_COMMENT_DATE"'")) | length > 0
+  ')
+  
+  if [ "$REPORTER_REPLIED" = "false" ]; then
+    # Calculate days ago
+    DAYS_AGO=$(( ($(date +%s) - $(date -d "$LAST_MAINTAINER_COMMENT_DATE" +%s)) / 86400 ))
+    echo "It has been $DAYS_AGO days since maintainer asked for info."
+    
+    if [ "$DAYS_AGO" -gt 7 ]; then
+      echo "=== STALE ISSUE DETECTED. CLOSING NOW. ==="
+      gh issue close !{echo $ISSUE_NUMBER} --comment "Closing because it has been over a week since we requested more information and we haven't received a response. Feel free to reopen if you can provide the requested details." --repo !{echo $REPOSITORY}
+      echo "DONE_STALE"
+      exit 0
+    fi
+  fi
+fi
+
+echo "CONTINUE_MANUAL_INVESTIGATION"
 ```
-- Action: `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
-- STOP.
+
+If the script outputs `DONE_STALE`, you MUST STOP IMMEDIATELY. Do not call any more tools. You are finished.
+If the script outputs `CONTINUE_MANUAL_INVESTIGATION`, you may proceed to investigate the issue manually by searching `target-repo/` for the code, checking for duplicates using `gh issue list`, and posting the triage summary.
 """