chore: Update auto triage guidelines

.github/workflows/gemini-issue-automated-triage.yml

@@ -90,16 +90,18 @@ jobs:
             1. Run: `gh label list` to get all available labels.
             2. Review the issue title and body provided in the environment
                variables: "${ISSUE_TITLE}" and "${ISSUE_BODY}".
-            3. Classify issues by their kind (bug, enhancement, documentation,
+            3. Classify issues by their type (bug, enhancement, documentation,
                cleanup, etc) and their priority (p0, p1, p2, p3). Set the
-               labels accoridng to the format `kind/*` and `priority/*` patterns.
+               labels according to the format `type: *` and `priority: *` patterns.
+               If the priority is decided to be more urgent than p2 (e.g. p0 or p1), mark the issue
+               as p2 and add a comment in the issue with the reason. The comment should ping
+               @blakeli0, @lqiu96, and @zhumin8 to notify them.
             4. Apply the selected labels to this issue using:
                `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"`
-            5. If the "status/needs-triage" label is present, remove it using:
-               `gh issue edit "${ISSUE_NUMBER}" --remove-label "status/needs-triage"`
 
             ## Guidelines
 
+            - If there are already labels for `type: *` and `priority: *`, do not modify them
             - Only use labels that already exist in the repository
             - Do not add comments or modify the issue content
             - Triage only the current issue
@@ -118,4 +120,4 @@ jobs:
               repo: '${{ github.repository }}'.split('/')[1],
               issue_number: '${{ github.event.issue.number }}',
               body: 'There is a problem with the Gemini CLI issue triaging. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.'
-            })
+            })

.github/workflows/gemini-issue-scheduled-triage.yml

@@ -41,10 +41,6 @@ jobs:
           NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
             --search 'is:open is:issue no:label' --json number,title,body)"
 
-          echo '🏷️ Finding issues that need triage...'
-          NEED_TRIAGE_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
-            --search 'is:open is:issue label:"status/needs-triage"' --json number,title,body)"
-
           echo '🔄 Merging and deduplicating issues...'
           ISSUES="$(echo "${NO_LABEL_ISSUES}" "${NEED_TRIAGE_ISSUES}" | jq -c -s 'add | unique_by(.number)')"
 
@@ -98,17 +94,19 @@ jobs:
             1. Run: `gh label list`
             2. Check environment variable: "${ISSUES_TO_TRIAGE}" (JSON array
                of issues)
-            3. For each issue, apply labels:
-               `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"`.
-               If available, set labels that follow the `kind/*`, `area/*`,
-               and `priority/*` patterns.
-            4. For each issue, if the `status/needs-triage` label is present,
-               remove it using:
-               `gh issue edit "${ISSUE_NUMBER}" --remove-label "status/needs-triage"`
+            3. Classify each issue by their type (bug, enhancement, documentation,
+               cleanup, etc) and their priority (p0, p1, p2, p3). Set the
+               labels according to the format `type: *` and `priority: *` patterns.
+               If the priority is decided to be more urgent than p2 (e.g. p0 or p1), mark the issue
+               as p2 and add a comment in the issue with the reason. The comment should ping
+               @blakeli0, @lqiu96, and @zhumin8 to notify them.
+            4. Apply the selected labels to this issue using:
+               `gh issue edit "${ISSUE_NUMBER}" --add-label "label1,label2"`
 
             ## Guidelines
 
+            - If there are already labels for `type: *` and `priority: *`, do not modify them
             - Only use existing repository labels
-            - Do not add comments
+            - Do not add comments or modify the issue content
             - Triage each issue independently
             - Reference all shell variables as "${VAR}" (with quotes and braces)