Restrict repost detection to explicit source attributions

Remove proactive exact-phrase searches from issue spam triage. Run provenance checks only when submitted content includes an “Originally posted by” attribution, then follow its linked GitHub source using the appropriate read-only issue, comment, or discussion tool. Classify the submission as spam only when its substantive content is verified as a verbatim copy with no original context. Preserve attributed excerpts when the author adds an original problem statement or actionable request, and explicitly avoid searching for unattributed copies. Regenerate the compiled issue-triage workflow with gh-aw v0.87.5 so its source hash reflects the narrower attribution-driven behavior. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
sergiou87 · Sep 2, 2026 · Sep 2, 2026 · Sep 2, 2026 · Sep 2, 2026 · Sep 2, 2026
commit 66705146956887e358cf7a5e737ef50b47fe2c5c
@@ -185,14 +185,13 @@ as your conclusion unless the evidence supports it.
 
 Judge the issue against the spam criteria included at the top of this prompt.
 
-Check whether the issue's substantive title or body was copied verbatim from another
-`cli/cli` issue, discussion, or comment. Search issues and issue comments for a
-distinctive exact phrase from the content. Inspect a discussion only when the issue
-provides its direct URL through a source link or `Originally posted by` attribution;
-the available tools cannot search unlinked discussion content. Treat a verified verbatim
-repost with no original context as spam. Do not treat quoted excerpts as spam when the
-author adds their own problem statement or actionable request explaining why the
-quotation is relevant.
+If the issue contains an `Originally posted by` attribution, inspect its linked source
+with the available GitHub tools, whether it is an issue, comment, discussion, or another
+GitHub resource. Treat the issue as spam when its substantive content is copied verbatim
+from that source without original context. Do not perform proactive phrase searches when
+no attribution is present. Do not treat attributed excerpts as spam when the author adds
+their own problem statement or actionable request explaining why the quotation is
+relevant.
 
 If, and only if, the issue meets those criteria, call `apply_suspected_spam`. This
 directly applies the label instead of proposing it. Applying the label triggers the

@@ -65,13 +65,12 @@ document, or clarify GitHub CLI belong elsewhere and should be treated as spam.
   off-topic discussions).
 - Content that seems to be taken from, or quoting, another discussion or issue
   which does not establish a sensible context, problem statement, or feedback.
-- An issue whose substantive title or body is copied verbatim from another issue,
-  discussion, or comment and presented as a new issue without original context. Verify
-  issue and issue-comment matches with an exact phrase search. Verify discussion matches
-  only from a direct source link or `Originally posted by` attribution because unlinked
-  discussions cannot be searched with the available tools. Quoted excerpts are
-  legitimate when the author adds their own problem statement or actionable request
-  explaining why the quotation is relevant.
+- An issue containing an `Originally posted by` attribution whose substantive content
+  is copied verbatim from the linked issue, comment, discussion, or other GitHub source
+  and presented without original context. Inspect the linked source to verify the match;
+  do not proactively search for unattributed copies. Attributed excerpts are legitimate
+  when the author adds their own problem statement or actionable request explaining why
+  the quotation is relevant.
 
 ## Issue templates