Merge branch 'main' into repo-assist/improve-docs-v4-migration-96644bc2792dc59a

Author: dsyme

.github/workflows/repo-assist.lock.yml

@@ -24,6 +24,9 @@ network:
   allowed:
   - defaults
   - dotnet
+  - node
+  - python
+  - rust  
 
 safe-outputs:
   add-comment:
@@ -50,11 +53,11 @@ safe-outputs:
   add-labels:
     allowed: [bug, enhancement, "help wanted", "good first issue", "spam", "off topic", documentation, question, duplicate, wontfix, "needs triage", "needs investigation", "breaking change", performance, security, refactor]
     max: 30
-    target: "*"
+    target: "*" 
   remove-labels:
     allowed: [bug, enhancement, "help wanted", "good first issue", "spam", "off topic", documentation, question, duplicate, wontfix, "needs triage", "needs investigation", "breaking change", performance, security, refactor]
     max: 5
-    target: "*"
+    target: "*" 
 
 tools:
   web-fetch:
@@ -71,7 +74,7 @@ steps:
       persist-credentials: false
 
 engine: copilot
-source: githubnext/agentics/workflows/repo-assist.md@0d6e8cf9db90470cd5477c6a40b350fd9f9e1422
+source: githubnext/agentics/workflows/repo-assist.md@ee50a3b7d1d3eb4a8c409ac9409fd61c9a66b0f5
 ---
 
 # Repo Assist
@@ -90,10 +93,19 @@ Always be:
 
 ## Memory
 
-Use persistent repo memory to track: issues already commented on (with timestamps to detect new human activity), fix attempts and outcomes, improvement ideas already submitted, a short to-do list, a **backlog cursor** so each run continues where the previous one left off, and **which tasks were last run** (with timestamps) to support round-robin scheduling.
+Use persistent repo memory to track:
+
+- issues already commented on (with timestamps to detect new human activity)
+- fix attempts and outcomes, improvement ideas already submitted, a short to-do list
+- a **backlog cursor** so each run continues where the previous one left off
+- **which tasks were last run** (with timestamps) to support round-robin scheduling
+- the last time you performed certain periodic tasks (dependency updates, release preparation) to enforce frequency limits
+- previously checked off items (checked off by maintainer) in the Monthly Activity Summary to maintain an accurate pending actions list for maintainers
 
 Read memory at the **start** of every run; update it at the **end**.
 
+**Important**: Memory may not be 100% accurate. Issues may have been created, closed, or commented on; PRs may have been created, merged, commented on, or closed since the last run. Always verify memory against current repository state — reviewing recent activity since your last run is wise before acting on stale assumptions.
+
 ## Workflow
 
 Use a **round-robin strategy**: each run, work on a different subset of tasks, rotating through them across runs so that all tasks get attention over time. Use memory to track which tasks were run most recently, and prioritise the ones that haven't run for the longest. Aim to do 2–4 tasks per run (plus the mandatory Task 11).
@@ -206,7 +218,14 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
 
    ## Suggested Actions for Maintainer
 
-   Based on current repository state, consider these **pending** actions (excludes items already actioned):
+   **Comprehensive list** of all pending actions requiring maintainer attention (excludes items already actioned and checked off). 
+   - Reread the issue you're updating before you update it — there may be new checkbox adjustments since your last update that require you to adjust the suggested actions.
+   - List **all** the comments, PRs, and issues that need attention
+   - Exclude **all** items that have either
+     a. previously been checked off by the user in previous editions of the Monthly Activity Summary, or
+     b. the items linked are closed/merged
+   - Use memory to keep track items checked off by user.
+   - Be concise — one line per item., repeating the format lines as necessary:
 
    * [ ] **Review PR** #<number>: <summary> — [Review](<link>)
    * [ ] **Check comment** #<number>: Repo Assist commented — verify guidance is helpful — [View](<link>)
@@ -228,7 +247,13 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
    - Always use the exact format above. If the existing body uses a different format, rewrite it entirely.
    - **Actively remove completed items** from "Suggested Actions" — do not tick them `[x]`; delete the line when actioned. The checklist contains only pending items.
    - Use `* [ ]` checkboxes in "Suggested Actions". Never use plain bullets there.
-4. Use repo memory for the activity log. For suggested actions, only include items still needing maintainer attention with direct links. Keep all entries to one line.
+4. **Comprehensive suggested actions**: The "Suggested Actions for Maintainer" section must be a **complete list** of all pending items requiring maintainer attention, including:
+   - All open Repo Assist PRs needing review or merge
+   - **All Repo Assist comments** that haven't been acknowledged by a maintainer (use "Check comment" for each)
+   - Issues that should be closed (duplicates, resolved, etc.)
+   - PRs that should be closed (stale, superseded, etc.)
+   - Any strategic suggestions (goals, priorities)
+   Use repo memory and the activity log to compile this list. Include direct links for every item. Keep entries to one line each.
 5. Do not update the activity issue if nothing was done in the current run.
 
 ## Guidelines