Remove update-discussion (not supported) and compile workflows

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

workflows/daily-backlog-burner.md

@@ -60,7 +60,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    2c. Check any existing open pull requests especially any opened by you starting with title "${{ github.workflow }}".
 
-   2d. If you think the plan is inadequate, and needs a refresh, update the planning discussion by rewriting the actual body of the discussion, ensuring you take into account any comments from maintainers. Add one single comment to the discussion saying the plan has been updated with a one sentence explanation about why. Then continue to step 3e.
+   2d. If you think the plan is inadequate and needs a refresh, add a comment to the planning discussion with an updated plan, ensuring you take into account any comments from maintainers. Explain in the comment why the plan has been updated. Then continue to step 3e.
 
    2e. Select a goal to pursue from the plan. Ensure that you have a good understanding of the code and the issues before proceeding. Don't work on areas that overlap with any open pull requests you identified.
 

workflows/daily-perf-improver.md

@@ -112,7 +112,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    3c. Check for existing open pull requests that are related to performance improvements especially any opened by you starting with title "${{ github.workflow }}". Don't repeat work from any open pull requests.
 
-   3d. If you think the plan is inadequate, and needs a refresh, update the planning discussion by rewriting the actual body of the discussion, ensuring you take into account any comments from maintainers. Add one single comment to the discussion saying the plan has been updated with a one sentence explanation about why. Then continue to step 3e.
+   3d. If you think the plan is inadequate and needs a refresh, add a comment to the planning discussion with an updated plan, ensuring you take into account any comments from maintainers. Explain in the comment why the plan has been updated. Then continue to step 3e.
 
    3e. Select a performance improvement goal to pursue from the plan. Ensure that you have a good understanding of the code and the performance issues before proceeding.
 

workflows/daily-plan.md

@@ -16,9 +16,6 @@ safe-outputs:
   create-discussion: # needed to create the project plan discussion
     title-prefix: "${{ github.workflow }}"
     category: "announcements"
-  update-discussion: # needed to update the project plan discussion if it already exists
-    target: "*" # can update one single discussion
-    body: # can update the discussion body only
 
 tools:
   web-fetch:
@@ -47,9 +44,9 @@ Your job is to act as a planner for the GitHub repository ${{ github.repository
 
    2c. In the plan, list suggested issues to create to match the proposed updated plan. Don't create any issues, just list the suggestions. Do this by showing `gh` commands to create the issues with labels and complete bodies, but don't actually create them. Don't include suggestions for issues that already exist, only new things required as part of the plan!
 
-3. You will either create or update the planning discussion so it contains a project plan in its body. 
+3. Create a new planning discussion with the project plan in its body. 
 
-   3a. If in step (1a) you found a "project plan" discussion, update its body with the project plan. If in step (1a) you didn't find a "project plan" discussion, create one with an appropriate title starting with "${{ github.workflow }}", using the project plan as the body.
+   3a. Create a discussion with an appropriate title starting with "${{ github.workflow }}" and the current date (e.g., "Daily Plan - 2025-10-10"), using the project plan as the body.
 
 
 <!-- You can customize prompting and tools in .github/workflows/agentics/daily-plan.config -->

workflows/daily-progress.md

@@ -61,7 +61,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    2c. Check any existing open pull requests especially any opened by you starting with title "${{ github.workflow }}".
 
-   2d. If you think the plan is inadequate, and needs a refresh, update the planning discussion by rewriting the actual body of the discussion, ensuring you take into account any comments from maintainers. Add one single comment to the discussion saying the plan has been updated with a one sentence explanation about why. Then continue to step 3e.
+   2d. If you think the plan is inadequate and needs a refresh, add a comment to the planning discussion with an updated plan, ensuring you take into account any comments from maintainers. Explain in the comment why the plan has been updated. Then continue to step 3e.
 
    2e. Select a goal to pursue from the plan. Ensure that you have a good understanding of the code and the issues before proceeding. Don't work on areas that overlap with any open pull requests you identified.
 

workflows/daily-test-improver.md

@@ -16,10 +16,6 @@ safe-outputs:
   create-discussion: # needed to create planning discussion
     title-prefix: "${{ github.workflow }}"
     category: "ideas"
-  update-discussion: # can update the planning discussion if it already exists
-    target: "*" # one single discussion
-    body: # can update the discussion title/body only
-    title: # can update the discussion title/body only
   add-comment:
     target: "*" # can add a comment to any one single issue or pull request
   create-pull-request: # can create a pull request
@@ -102,7 +98,7 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
 
    3d. Check for existing open pull opened by you starting with title "${{ github.workflow }}". Don't repeat work from any open pull requests.
 
-   3e. If you think the plan is inadequate, and needs a refresh, update the planning discussion by rewriting the actual body of the discussion, ensuring you take into account any comments from maintainers. Add one single comment to the discussion saying the plan has been updated with a one sentence explanation about why. Then continue to step 3f.
+   3e. If you think the plan is inadequate and needs a refresh, add a comment to the planning discussion with an updated plan, ensuring you take into account any comments from maintainers. Explain in the comment why the plan has been updated. Then continue to step 3f.
 
    3f. Based on all of the above, select an area of relatively low coverage to work on that appear tractable for further test additions.