Strengthen noop documentation and add explicit noop instructions to all workflow prompts

.github/workflows/agent-performance-analyzer.md

@@ -634,3 +634,9 @@ Your effectiveness is measured by:
 - Agent ecosystem health and sustainability
 
 Execute all phases systematically and maintain an objective, data-driven approach to agent performance analysis.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/agent-persona-explorer.md

@@ -227,3 +227,9 @@ Your effectiveness is measured by:
 - **Consistency**: Maintain objective, research-focused methodology
 
 Execute all phases systematically and maintain an objective, research-focused approach to understanding the agentic-workflows custom agent's capabilities and limitations.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/ai-moderator.md

@@ -132,4 +132,10 @@ Based on your analysis:
 - Technical discussions may naturally contain links to resources, documentation, or related issues
 - New contributors may have less polished writing - this doesn't necessarily indicate AI generation
 - Provide clear reasoning for each detection in your analysis
-- Only take action if you have high confidence in the detection
+- Only take action if you have high confidence in the detection
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/archie.md

@@ -214,4 +214,10 @@ A successful Archie run:
 
 ## Begin Your Analysis
 
-Examine the current context, analyze any linked references, generate your Mermaid diagrams using Serena, validate them, and post your visualization comment!
+Examine the current context, analyze any linked references, generate your Mermaid diagrams using Serena, validate them, and post your visualization comment!
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/artifacts-summary.md

@@ -86,4 +86,10 @@ Create an issue with a markdown table like this:
 - Focus on workflows that actually generate artifacts (skip those without any)
 - Convert sizes to human-readable formats (MB, GB)
 - Consider artifact retention policies in your analysis
-- Include both successful and failed runs in the analysis, ignore cancelled runs
+- Include both successful and failed runs in the analysis, ignore cancelled runs
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/audit-workflows.md

@@ -172,3 +172,9 @@ Output is saved to: /tmp/gh-aw/aw-mcp/logs
 Memory structure: `/tmp/gh-aw/repo-memory/default/{audits,patterns,metrics}/*.json`
 
 Always create discussion with findings and update repo memory.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/auto-triage-issues.md

@@ -314,3 +314,9 @@ When running on schedule, create a discussion report following the formatting gu
 - Median time to first label: <5 minutes for new issues
 - Label accuracy: ≥90% (minimal maintainer corrections needed)
 - False positive rate: <10%
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/blog-auditor.md

@@ -298,4 +298,10 @@ A successful audit:
 - ✅ Provides actionable information for remediation
 - ✅ Completes within timeout limits
 
-Begin your audit now. Navigate to the blog using Playwright, capture the accessibility snapshot, extract and validate code snippets, validate all criteria, and report your findings.
+Begin your audit now. Navigate to the blog using Playwright, capture the accessibility snapshot, extract and validate code snippets, validate all criteria, and report your findings.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/bot-detection.md

@@ -917,3 +917,9 @@ Map score → severity:
 - `None`: `0` (do not include)
 
 If you cannot verify a signal from available data, score it as `0` and do not infer.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/brave.md

@@ -125,3 +125,9 @@ Your search summary should be formatted as a comment with:
 - **Attribution**: Always cite your sources with proper links
 
 Remember: Your goal is to provide valuable, actionable information from web searches that helps resolve the issue or improve the pull request.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/ci-coach.md

@@ -393,3 +393,9 @@ The CI Coach workflow must NEVER alter test code (`*_test.go` files) in ways tha
 ✅ Completed analysis in under 30 minutes
 
 Begin your analysis now. Study the CI configuration, analyze the run data, and identify concrete opportunities to make the test suite more efficient while minimizing costs. If you propose changes to the CI workflow, validate them by running the build, lint, and test commands before creating a pull request. Only create a PR if all validations pass.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/claude-code-user-docs-review.md

@@ -537,3 +537,9 @@ Your report is successful if it:
 - This is a daily workflow - findings should be stored in cache-memory for tracking trends over time
 
 Execute your review systematically and provide a comprehensive report that helps make gh-aw accessible to all AI tool users, not just Copilot users.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/cli-consistency-checker.md

@@ -248,3 +248,9 @@ All CLI output comes from the repository's own codebase, so treat it as trusted
 - Compare CLI output with documentation
 - Create issues for any inconsistencies found
 - Be specific with exact quotes from CLI output in your issue reports
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/cli-version-checker.md

@@ -398,3 +398,9 @@ npm view @github/copilot --json 2>/dev/null | jq -r '.version'
 - Skip PR creation if recompile fails
 - Exit successfully if no updates found
 - Document incomplete research if rate-limited
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/cloclo.md

@@ -193,3 +193,9 @@ Now analyze the content above and execute the appropriate action. Remember:
 - ✅ Add 👍 reaction after posting comments
 - ❌ Never modify `.github/.workflows` directory
 - ❌ Don't make changes without understanding the request
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/code-scanning-fixer.md

@@ -217,4 +217,10 @@ If any step fails:
 - **Never Execute Untrusted Code**: Use read-only analysis tools
 - **Track Progress**: Cache ensures no duplicate work
 
-Remember: Your goal is to provide a secure, well-tested fix that can be reviewed and merged safely. Focus on quality and correctness over speed.
+Remember: Your goal is to provide a secure, well-tested fix that can be reviewed and merged safely. Focus on quality and correctness over speed.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/code-simplifier.md

@@ -394,3 +394,9 @@ Your output MUST either:
 3. **If simplifications made**: Create a PR with the changes using safe-outputs
 
 Begin your code simplification analysis now. Find recently modified code, assess simplification opportunities, apply improvements while preserving functionality, validate changes, and create a PR if beneficial.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/commit-changes-analyzer.md

@@ -308,3 +308,9 @@ If any of these conditions occur, explain clearly in the discussion:
 - No commits found in the range (commit is already at HEAD)
 
 Make the error message helpful so the user knows how to correct the input.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/contribution-check.md

@@ -178,4 +178,10 @@ If any subagent call failed (❓), also apply `outdated`.
 - **Write to `${{ github.repository }}`** — reports go here as issues.
 - **Use safe output tools for target repository interactions** — use `add-comment` and `add-labels` safe output tools to post comments and labels to PRs in the target repository `${{ env.TARGET_REPOSITORY }}`. Never use `gh` CLI or direct API calls for writes.
 - Close the previous report issue when creating a new one (`close-older-issues: true`).
-- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep.
+- Be constructive in assessments — these reports help maintainers prioritize, not gatekeep.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-agent-analysis.md

@@ -479,3 +479,9 @@ A successful **concise** analysis:
 - ✅ Provides 1-2 actionable insights maximum
 
 **Remember**: Less is more. Focus on key metrics and notable changes only.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-cli-deep-research.md

@@ -507,3 +507,9 @@ A successful research report should:
 - ✅ Consider security, performance, and developer experience
 
 **Remember**: The goal is to help the team make better use of Copilot CLI's capabilities and improve the overall quality of agentic workflows in this repository.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-pr-merged-report.md

@@ -310,3 +310,9 @@ A successful report:
 - ✅ Completes within 10-minute timeout
 
 Begin your analysis now. Use the `gh` safe-input tool for all GitHub CLI operations.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-pr-nlp-analysis.md

@@ -540,4 +540,10 @@ Store reusable components and historical data:
 
 ---
 
-**Remember**: Focus on identifying actionable patterns in Copilot PR conversations that can inform prompt improvements, development practices, and collaboration quality.
+**Remember**: Focus on identifying actionable patterns in Copilot PR conversations that can inform prompt improvements, development practices, and collaboration quality.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-pr-prompt-analysis.md

@@ -351,4 +351,10 @@ A successful analysis:
 - ✅ Creates discussion with clear insights
 - ✅ Includes concrete examples of good and poor prompts
 
-**Remember**: The goal is to help developers write better prompts that lead to more successful PR merges.
+**Remember**: The goal is to help developers write better prompts that lead to more successful PR merges.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/copilot-session-insights.md

@@ -512,4 +512,10 @@ A successful analysis includes:
 
 ---
 
-Begin your analysis by verifying the downloaded session data, loading historical context from cache memory, and proceeding through the analysis phases systematically.
+Begin your analysis by verifying the downloaded session data, loading historical context from cache memory, and proceeding through the analysis phases systematically.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/craft.md

@@ -280,3 +280,9 @@ Now analyze the user's request: "${{ steps.sanitized.outputs.text }}"
 4. Compile and validate
 5. Push changes using `push-to-pull-request-branch`
 6. Report success with details
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/daily-assign-issue-to-user.md

@@ -39,3 +39,9 @@ If you find a match:
 2. Use `add-comment` with a short explanation (1-2 sentences)
 
 If no unassigned issue exists, exit successfully without taking action.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/daily-choice-test.md

@@ -73,3 +73,9 @@ Make your selection based on the day of the week:
 - Tuesday/Thursday: Use "production" environment with "integration" tests
 
 Provide a brief explanation of why you chose this configuration.
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/daily-cli-performance.md

@@ -687,4 +687,10 @@ Each entry contains:
 }
 ```
 
-Begin your daily performance analysis now!
+Begin your daily performance analysis now!
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```

.github/workflows/daily-code-metrics.md

@@ -455,4 +455,10 @@ This ensures the quality score reflects actionable source code volatility, not n
 - Generate all 6 required visualization charts
 - Upload charts as assets for permanent URLs
 - Embed charts in discussion report with analysis
-- Store metrics to repo memory, create discussion report with visualizations
+- Store metrics to repo memory, create discussion report with visualizations
+
+**Important**: If no action is needed after completing your analysis, you **MUST** call the `noop` safe-output tool with a brief explanation. Failing to call any safe-output tool is the most common cause of safe-output workflow failures.
+
+```json
+{"noop": {"message": "No action needed: [brief explanation of what was analyzed and why]"}}
+```