Add pr_docs_update workflow job for automated documentation sync from merged PRs

[Copilot]

Creates an example workflow job that analyzes recently merged PRs and updates AGENTS.md or copilot-specific instructions accordingly, with state tracking to prevent duplicate processing across runs.

Implementation

New standard job: pr_docs_update

• Three-step workflow: fetch → analyze → update
• State tracking via .deepwork/pr_docs_state.json to skip processed PRs
• Configurable PR count parameter for historical depth control
• Categorizes changes as general (AGENTS.md) or copilot-specific

Job structure:

steps:
  - fetch_prs: Retrieves merged PRs, filters against state file
  - analyze_prs: Identifies documentation-relevant changes
  - update_docs: Applies updates, maintains state file

Files added:

• src/deepwork/standard_jobs/pr_docs_update/ (source of truth)
• .deepwork/jobs/pr_docs_update/ (working copy)
• Includes job.yml, step instructions, AGENTS.md, USAGE.md

Usage pattern:

# Initial run
/pr_docs_update.fetch_prs pr_count=10
/pr_docs_update.analyze_prs
/pr_docs_update.update_docs

# Subsequent runs automatically skip processed PRs
/pr_docs_update.fetch_prs pr_count=20  # Go deeper into history

State file enables incremental processing - each run only processes new PRs, supports arbitrary lookback by adjusting pr_count.

Original prompt

Create an example workflow job that looks at recently merged PR's and attempts to update either AGENTS.md or copilot specific instructions (if it's only for copilot agent). Subsuqnet runs should skip PR's that have already been merged. We should do last x PR's and can be ran multiple times to go further back into the PR history.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the DCO.
✅ (nhorton)[https://github.com/nhorton]
❌ @Copilot
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the DCO Assistant Lite bot.}