improve workflows

Author: dsyme

docs/ci-doctor.md

@@ -55,7 +55,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Monitor for recurring failure patterns and adjust workflows accordingly
 - Disable or uninstall the workflow if failure investigations are not providing value
 
-## Activity duration
-
-- By default this workflow will trigger for at most 30 days, after which it will stop triggering.
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.

docs/daily-accessibility-review.md

@@ -44,8 +44,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Test accessibility improvements before closing issues
 - Disable or uninstall the workflow if accessibility reports are not accurate or useful
 
-## Activity duration
-
-- By default this workflow will trigger for at most 48 hours, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.
-

docs/daily-dependency-updates.md

@@ -50,8 +50,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Monitor for any issues after dependency updates are deployed
 - Disable or uninstall the workflow if dependency updates cause more problems than benefits
 
-## Activity duration
-
-- By default this workflow will trigger for at most 48 hours, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.
-

docs/daily-perf-improver.md

@@ -65,8 +65,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Merge approved performance improvements after thorough testing
 - Disable or uninstall the workflow if performance optimizations are not effective or introduce bugs
 
-## Activity duration
-
-- By default this workflow will trigger for at most 48 hours, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.
-

docs/daily-plan.md

@@ -46,7 +46,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Use planning issues as input for team coordination and sprint planning
 - Disable or uninstall the workflow if planning automation is not helpful
 
-## Activity duration
-
-- By default this workflow will trigger for at most 30 days, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.

docs/daily-progress.md

@@ -118,7 +118,6 @@ The Daily Progress workflow follows a systematic 7-step process:
 - **Draft Pull Requests**: All feature changes are created as draft PRs for human review
 - **Roadmap Issues**: Central tracking of project goals and progress
 - **Scheduled Execution**: Runs only on weekdays to respect team schedules
-g- **Timeout Protection**: Limited to 30 minutes per run with 1-month stop-after
 - **Safe Outputs**: Controlled limits on issues and PRs created
 
 ## Human in the loop

docs/daily-qa.md

@@ -51,7 +51,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Close issues once problems have been addressed
 - Disable or uninstall the workflow if QA findings are not actionable or valuable
 
-## Activity duration
-
-- By default this workflow will trigger for at most 48 hours, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.

docs/daily-repo-status.md

@@ -48,8 +48,3 @@ This workflow requires no configuration and works out of the box. You can use ed
 - Comment on issues to provide additional context or corrections
 - Use status reports to inform team meetings and planning decisions
 - Disable or uninstall the workflow if status reports don't provide valuable insights
-
-## Activity duration
-
-- By default this workflow will trigger for at most 30 days, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.

docs/daily-test-improver.md

@@ -52,8 +52,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Ensure tests are meaningful and not just coverage-padding
 - Merge approved test improvements after verification
 - Disable or uninstall the workflow if test additions are not improving code quality
-
-## Activity duration
-
-- By default this workflow will trigger for at most 48 hours, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.

docs/issue-triage.md

@@ -53,7 +53,3 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - Monitor triaged issues to ensure proper follow-up and resolution
 - Disable or uninstall the workflow if triage automation is not accurate or helpful
 
-## Activity duration
-
-- By default this workflow will trigger for at most 30 days, after which it will stop triggering. 
-- This allows you to experiment with the workflow for a limited time before deciding whether to keep it active.