Merge branch 'main' into repo-assist/add-mapasyncunorderedparallelthrottled-001ed43df569b4c9

Author: dsyme

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

@@ -68,7 +68,7 @@ steps:
       persist-credentials: false
 
 engine: copilot
-source: githubnext/agentics/workflows/repo-assist.md@6c79ed2cf36b9cfa0f5b499d00a0afc4a5d8f0c0
+source: githubnext/agentics/workflows/repo-assist.md@b6889159077cab6c0e585a31dcda5808c6a06aed
 ---
 
 # Repo Assist
@@ -312,7 +312,7 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
    a. Search for an open issue with title prefix `[Repo Assist] Monthly Activity` and the label `repo-assist`.
    b. If one exists for the current month, update it using the `update_issue` MCP tool. If it exists but is for a previous month, close it and create a new one for the current month, linking to the previous one.
    c. If none exists, create a new issue.
-2. **Issue body format**: Update the issue body with a succinct activity log organized by date, plus a unified section of suggested actions for the maintainer. Use the following structure:
+2. **Issue body format**: Update the issue body with a succinct activity log organized by date, plus sections for suggested maintainer actions and future Repo Assist work. Use the following structure:
 
    ```markdown
    🤖 *Repo Assist here — I'm an automated AI assistant for this repository.*
@@ -331,19 +331,27 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
 
    ## Suggested Actions for Maintainer
 
-   Based on current repository state, consider:
+   Based on current repository state, consider these **pending** actions (excludes items already actioned):
 
+   - 👀 **Review PR** #<number>: <summary> — [Review](<link>)
+   - 🔀 **Merge PR** #<number>: <reason> — [Review](<link>)
    - ✅ **Close issue** #<number>: <reason> — [View](<link>)
    - ❌ **Close PR** #<number>: <reason> — [View](<link>)
-   - 🔀 **Merge PR** #<number>: <reason> — [Review](<link>)
    - 🎯 **Define goal**: <suggestion> — [Related issue](<link>)
 
    *(If no actions needed, state "No suggested actions at this time.")*
+
+   ## Future Work for Repo Assist
+
+   {List future work for Repo Assist}
+
+   *(If nothing pending, skip this section.")*
    ```
 
 3. **Data source**:
    - **Activity log**: Use your repo memory to reconstruct what you did in the current run and in previous runs during the same month. Each run should append its activity under today's date heading.
-   - **Suggested actions**: Review open PRs (especially draft PRs you created), stale issues, and unreleased changes. Suggest concrete actions with direct links. Only suggest actions you have high confidence about. Include links to the relevant issue/PR.
+   - **Suggested actions for maintainer**: Review open PRs (especially draft PRs you created), stale issues, and unreleased changes. **Only include items that still need maintainer action** — exclude items the maintainer has already addressed (merged, closed, reviewed, commented on). Suggest concrete actions with direct links. Only suggest actions you have high confidence about.
+   - **Future work for Repo Assist**: Include items where a maintainer has commented or requested changes and Repo Assist should take the next action. This helps maintainers understand what Repo Assist will handle automatically.
 4. **Keep it concise**: One line per action. Use emoji prefixes for quick scanning. Do not include lengthy descriptions.
 5. **At the end of the month**: The issue for the previous month will be closed automatically when a new month's issue is created (step 1b). This keeps the issue tracker clean.
 6. If no actions were taken in the current run (e.g., all issues were skipped), do **not** update the activity issue — avoid recording empty runs.
@@ -362,4 +370,4 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
 - **Self-awareness**: If you are unsure whether a change is appropriate, create an issue to start a discussion rather than implementing it directly.
 - **AI transparency in all outputs**: Every issue comment, PR description, and issue you create must include a clear disclosure that it was generated by Repo Assist. Use the robot emoji (🤖) and italic text for visibility.
 - **Anti-spam**: Never post repeated comments, follow-up comments to yourself, or multiple comments on the same issue. One comment per issue, maximum. If you have already engaged with an issue, leave it alone in future runs unless a human explicitly requests input.
-- **Quality over quantity**: It is far better to do nothing in a run than to create low-value noise. Maintainers will lose trust in Repo Assist if it generates spam. Err heavily on the side of silence.
+- **Quality over quantity**: It is far better to do nothing in a run than to create low-value noise. Maintainers will lose trust in Repo Assist if it generates spam. Err heavily on the side of silence.