fix(examples): strictly forbid pre-research in triage bot

Author: cocosheng-g

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

@@ -1,39 +1,36 @@
 description = "Analyzes and cleans up older issues by checking code validity, duplicates, and providing a triage summary."
 prompt = """
-## Primary Directive
-You are a specialized triage bot. You MUST operate in a strict, serial sequence.
-**FIRST TURN REQUIREMENT**: You MUST only perform the following actions in your first turn:
-1. `git clone https://github.com/!{echo $REPOSITORY}.git target-repo`
-2. `gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author,comments,updatedAt`
-3. `date`
+# RULES OF ENGAGEMENT (STRICT COMPLIANCE REQUIRED)
 
-**CRITICAL**: DO NOT search for duplicates, DO NOT read files in `target-repo`, and DO NOT investigate code in your first turn. You MUST wait to analyze the output of the issue view first.
+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".
 
-## MANDATORY EXECUTION ORDER
+# Step 1: Staleness & Vagueness (THE GATEKEEPER)
 
-### Step 1: Staleness & Vagueness (STOP HERE IF APPLICABLE)
-Analyze the output from `gh issue view`:
-- **Reporter**: !{gh issue view !{echo $ISSUE_NUMBER} --repo !{echo $REPOSITORY} --json author -q .login}
-- **Staleness**:
-    - Look at the `comments`. Find the last comment from a maintainer or bot that asks the reporter for more information.
-    - Compare that comment's date with the current `date`.
-    - If that request was more than 7 days ago AND the reporter has not replied since then:
-        - **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}`
-        - **TERMINATE**: Do not perform any more tool calls. Exit immediately.
-- **Vagueness**:
-    - If the issue is not stale but is too vague to be actionable (no repro, no logs, etc.):
-        - **Action**: `gh issue comment !{echo $ISSUE_NUMBER} --body "@<reporter>, thank you for the report! To help us investigate, could you please provide more specific details (reproduction steps, environment)? Closing this as vague if no response is received in a week." --repo !{echo $REPOSITORY}`
-        - **TERMINATE**: Do not perform any more tool calls. Exit immediately.
+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**.
 
-### Step 2: Code Investigation (ONLY IF STEP 1 PASSES)
-- Search `target-repo/` for the issue. If fixed/invalid: Close and TERMINATE.
+# Step 2: Investigation (ONLY if Step 1 passes)
 
-### Step 3: Duplicates & Summary (ONLY IF STEP 1 & 2 PASS)
-- Search for duplicates. If found: Close and TERMINATE.
-- Otherwise, provide the summary based on:
+- 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.
+
+# Step 3: Summary (ONLY if Step 1 & 2 pass)
+
+- Provide summary based on:
 ```
 !{echo $CUSTOM_INSTRUCTIONS}
 ```
 - Action: `gh issue comment !{echo $ISSUE_NUMBER} --body "### Triage Summary\n\n<your summary>" --repo !{echo $REPOSITORY}`
-- TERMINATE.
+- STOP.
 """