Add one-time follow-up triage when author provides missing env info

Extends the issue auto-triage workflow so a second (and final) triage
summary is produced when:
  1. The first triage flagged missing environment fields, AND
  2. The original issue author responds with a follow-up comment.

No further triage runs after the second summary. Comments from other
users, bots, or on PRs do not trigger re-triage.

NOTE: Maintainers must run 'gh aw compile' to regenerate
.github/workflows/issue-triage.lock.yml from this .md source.

Author: priyankatiwari08

.github/workflows/issue-triage.md

@@ -2,8 +2,26 @@
 on:
   issues:
     types: [opened]
+  issue_comment:
+    types: [created]
   roles: all
 
+# Cheap gate before the agent boots:
+#   - issues.opened          -> always run (initial triage)
+#   - issue_comment.created  -> only when the commenter IS the issue author,
+#                               the comment is on an issue (not a PR), and
+#                               the author is not a bot. The deeper checks
+#                               ("prior triage flagged missing env" and
+#                               "no second triage already posted") are done
+#                               inside the prompt because they require
+#                               reading existing comments.
+if: |
+  github.event_name == 'issues' ||
+  (github.event_name == 'issue_comment'
+   && github.event.issue.pull_request == null
+   && github.event.comment.user.login == github.event.issue.user.login
+   && !endsWith(github.event.comment.user.login, '[bot]'))
+
 engine: copilot
 
 permissions:
@@ -16,27 +34,63 @@ tools:
     min-integrity: none
 
 safe-outputs:
+  # Allow up to 2 triage summaries per issue (initial + one follow-up).
+  # `hide-older-comments` collapses the previous summary so the latest one
+  # is the only visible "current state".
   add-comment:
-    max: 1
+    max: 2
     hide-older-comments: true
 ---
 
 # SqlClient Issue Auto-Triage
 
 You are a triage specialist for **Microsoft.Data.SqlClient**.
-A new issue has just been opened. Your job is to:
+Your job is to post **at most one** triage summary comment per workflow run
+using `add_comment`.
+
+This workflow runs in two situations:
 
-1. Read the issue silently using GitHub read tools
-2. Post **one** triage summary comment using `add_comment`
+1. **Initial triage** — a new issue was just opened (`event_name == "issues"`).
+2. **Follow-up triage** — the original issue author posted a comment
+   (`event_name == "issue_comment"`). In this case you must first decide
+   whether a follow-up triage is actually warranted (see "Follow-up gate"
+   below) and call `noop` if it is not.
 
-That is the entire workflow. Do NOT call `add_comment` more than once.
+Do NOT call `add_comment` more than once per run.
 Do NOT call `add_labels`. Do NOT apply any labels.
 Do NOT post intermediate findings. Do NOT post separate comments for
 area detection, duplicate checking, or environment validation.
 Everything goes into the single triage summary at the end.
 
 ---
 
+## Follow-up gate (only when `event_name == "issue_comment"`)
+
+Before doing any triage work on a comment event, list all existing comments
+on the issue using GitHub read tools and verify **all** of the following.
+If any check fails, call `noop` with a short reason and stop — do NOT post
+a comment.
+
+1. **Exactly one prior triage summary exists.** Count comments authored by
+   `github-actions[bot]` whose body contains the string `🔍 Triage Summary`.
+   - If the count is `0`, the initial triage hasn't happened yet — call `noop`.
+   - If the count is `≥ 2`, the follow-up has already been posted — call
+     `noop`. We never post a third summary.
+2. **The prior triage flagged missing environment fields.** The single
+   existing `🔍 Triage Summary` comment body must contain the string
+   `⚠️ Missing:`. If it does not, the first triage had complete info and
+   no follow-up is needed — call `noop`.
+3. **The triggering comment is from the issue's original author.** This is
+   already enforced by the workflow-level `if:`, but re-verify defensively:
+   `comment.user.login == issue.user.login`. If not, call `noop`.
+
+Only if all three checks pass, proceed to the triage instructions below
+and produce a fresh summary. Treat the prior summary as **invalidated** —
+the new one supersedes it (the older one will be collapsed automatically
+by `hide-older-comments`).
+
+---
+
 ## Required Context
 
 Before analyzing the issue, you MUST read all project knowledge base files
@@ -52,15 +106,18 @@ environment validation, and analysis. Do not skip this step.
 
 ## Instructions
 
-Read the issue body. Then do ALL of the following analysis silently
-(using read tools and search only — no comments, no outputs):
+Read the issue body **and, for follow-up runs, every subsequent comment**.
+Then do ALL of the following analysis silently (using read tools and search
+only — no comments, no outputs):
 
 **A. Classify issue type**: Bug (reports unexpected behavior, crash, regression, or incorrect results), Feature (has proposal), Question, or Task.
 
 **B. Validate environment** (bugs only): Check for these required fields:
 SqlClient version, .NET target framework, SQL Server version, OS,
 repro steps, expected vs actual behavior.
 If any are missing, list them explicitly in the triage summary (e.g. "Missing: SQL Server version, OS").
+For follow-up runs, treat information supplied in any later comment by the
+issue author as if it were part of the original issue body.
 Proceed with all remaining triage steps regardless of missing environment details.
 
 **C. Classify area**: Based on the issue content, pick the single best matching area label from this list:
@@ -90,7 +147,8 @@ Proceed with all remaining triage steps regardless of missing environment detail
 
 ## Actions
 
-Call `add_comment` exactly **once** with this markdown:
+Call `add_comment` exactly **once** with this markdown (for follow-up runs,
+add the parenthetical "(updated after author response)" to the heading):
 
 ```
 ## 🔍 Triage Summary