chore: switch course-updater to weekly on Monday and add duplicate PR prevention

[DanWahlin]

Changes

• Schedule: Changed from daily to weekly on monday (compiles to 38 11 * * 1 — 11:38 AM UTC / 4:38 AM PT)
• Duplicate prevention: Added Step 2 instructing the agent to read existing open bot PRs, identify which features they already cover, and exclude those from its work — preventing duplicate PRs for the same feature
• Renumbered steps 3–5 accordingly
• Recompiled lock file

[Copilot]

Pull request overview

Updates the Course Updater agentic workflow to run on a weekly cadence and adds explicit instructions to avoid generating duplicate automated PRs.

Changes:

• Switched the workflow schedule from daily to weekly on Monday.
• Added a new Step 2 to scan existing open bot PRs (by label) and exclude already-covered features from new updates.
• Recompiled the generated workflow lock file.

Show a summary per file

File	Description
.github/workflows/course-updater.md	Adjusts schedule and adds duplicate-PR avoidance instructions with renumbered steps.
.github/workflows/course-updater.lock.yml	Regenerates compiled workflow with updated cron and embedded prompt text.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 2

[Copilot]

Step 2 requires enumerating open PRs and reading their titles/descriptions. In the compiled workflow, the agent job’s GITHUB_TOKEN permissions are limited to contents: read, which can cause gh pr list/PR API calls to fail with “Resource not accessible by integration”. Consider either (a) granting pull-requests: read to the agent job token, or (b) explicitly instructing the agent to use the GitHub MCP github tool (which is already configured with GITHUB_MCP_SERVER_TOKEN) to list PRs instead of relying on gh auth.

Suggested change

Before doing any content comparison, list all open pull requests in this repo that have the `automated-update` or `copilot-cli-updates` labels. Read their titles and descriptions to understand which features or changes each PR already covers. Build a list of features that are **already addressed** by existing PRs — you must exclude those features from any updates you propose later. If every feature you found in Step 1 is already covered by an open PR, stop here and report that no new updates are needed.

Before doing any content comparison, use the `github` MCP tool (not `gh`) to list all open pull requests in this repo that have the `automated-update` or `copilot-cli-updates` labels. Read each matching PR's title and description to understand which features or changes it already covers. Build a list of features that are **already addressed** by existing PRs — you must exclude those features from any updates you propose later. If every feature you found in Step 1 is already covered by an open PR, stop here and report that no new updates are needed.

[Copilot]

The instruction “PRs that have the automated-update or copilot-cli-updates labels” is ambiguous for common tooling: gh pr list --label filters are conjunctive (AND), and GitHub search defaults to AND as well. To reliably avoid duplicates, clarify the intended query (either explicitly fetch both label sets and union them, or use an OR-capable search expression) so PRs with only one of the labels aren’t missed.

Suggested change

Before doing any content comparison, list all open pull requests in this repo that have the `automated-update` or `copilot-cli-updates` labels. Read their titles and descriptions to understand which features or changes each PR already covers. Build a list of features that are **already addressed** by existing PRs — you must exclude those features from any updates you propose later. If every feature you found in Step 1 is already covered by an open PR, stop here and report that no new updates are needed.

Before doing any content comparison, list all open pull requests in this repo that have **either** the `automated-update` label **or** the `copilot-cli-updates` label. Do this with an explicit OR-capable query, or by fetching PRs for each label separately and then unioning and deduplicating the results, so PRs that have only one of the labels are not missed. Read their titles and descriptions to understand which features or changes each PR already covers. Build a list of features that are **already addressed** by existing PRs — you must exclude those features from any updates you propose later. If every feature you found in Step 1 is already covered by an open PR, stop here and report that no new updates are needed.