Improve tutorial-update-monitor deduplication: topic-based search to prevent duplicate issues

Agent-Logs-Url: https://github.com/instil/github-copilot-tutorial/sessions/18216a9f-ae40-4c05-b419-3f6406ea36e5

Co-authored-by: calebwilson706 <71669491+calebwilson706@users.noreply.github.com>

Author: Copilot

.github/workflows/tutorial-update-monitor.md

@@ -63,16 +63,21 @@ Use the GitHub tool to list recent commits (last 14 days) from `github/copilot-c
 
 3. **Check `github/copilot-cli-for-beginners`** for commits from the past 14 days using the GitHub tool.
 
-4. **Search for existing issues** in `instil/github-copilot-tutorial` to avoid creating duplicates. Search for **both open and closed** issues with titles containing "Tutorial update needed". Also look for issues labelled `not planned` or in a closed/not-planned state. If a similar issue already exists in any state, skip creating a new one.
-
-5. **For each meaningful finding**, create a GitHub issue in `instil/github-copilot-tutorial`:
+4. **Before creating any issue**, perform a thorough duplicate check in `instil/github-copilot-tutorial`:
+   - Search **all issues (open AND closed)** with the label `tutorial-update`
+   - For each finding, extract the **key subject** (e.g. the command name like `/pr`, the feature name like `extensions`, the config key like `--effort`)
+   - Search for that key subject as a keyword in existing issues — not just the title prefix. For example, if a finding is about the `/pr` command, search for `/pr` in existing issue titles and bodies
+   - **If any existing issue — open, closed, or not-planned — already covers the same command, feature, or tutorial gap, skip creating a new issue entirely**
+   - Two issues cover the same gap if they refer to the same command, flag, config option, or tutorial lesson area — even if the wording, framing, or source reference differs
+
+5. **For each meaningful finding with no pre-existing issue**, create a GitHub issue in `instil/github-copilot-tutorial`:
    - **Title**: `Tutorial update needed: [short description of what changed]`
    - **Body** must include:
      - A clear summary of what changed and why the tutorial needs updating
      - A direct link to the relevant release, documentation section, or commit
      - The specific part(s) of the tutorial that need updating
      - Suggested changes or new content to add
-   - Skip creating an issue if a similar one already exists in any state (open, closed, or not planned — based on the check in step 4)
+   - Do **not** create an issue if a similar one already covers this topic in any state
 
 ## Guidelines
 
@@ -81,3 +86,4 @@ Use the GitHub tool to list recent commits (last 14 days) from `github/copilot-c
 - Group closely related changes into a single issue when it makes sense.
 - Be specific and actionable in issue descriptions so maintainers can address them quickly.
 - Limit to **5 issues per run** to avoid noise.
+- **Prefer no new issue over a possible duplicate.** When the topic of a finding is already covered by any existing issue — even if it approaches it from a different angle — skip creating a new issue. It is better to miss a subtle nuance than to create a duplicate that adds noise for maintainers.