Clarify instruction wording for updating planning discussions

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 nothing but the plan has been updated with a one sentence explanation about why. Do not add multiple comments to the discussion, just update the body. Then continue to step 3e.
+   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.
 
    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 nothing but the plan has been updated with a one sentence explanation about why. Do not add multiple comments to the discussion, just update the body. Then continue to step 3e.
+   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.
 
    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-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 nothing but the plan has been updated with a one sentence explanation about why. Do not add multiple comments to the discussion, just update the body. Then continue to step 3e.
+   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.
 
    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

@@ -102,7 +102,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 nothing but the plan has been updated with a one sentence explanation about why. Do not add multiple comments to the discussion, just update the body. Then continue to step 3f.
+   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.
 
    3f. Based on all of the above, select an area of relatively low coverage to work on that appear tractable for further test additions.