Extract shared smoke-test brevity prompt and import across 21 smoke workflows

.github/workflows/shared/smoke-test-brevity.md

@@ -0,0 +1,7 @@
+## Smoke Test Brevity
+
+**CRITICAL EFFICIENCY REQUIREMENTS:**
+- Keep ALL outputs extremely short and concise. Use single-line responses where possible.
+- NO verbose explanations or unnecessary context.
+- Minimize file reading - only read what is absolutely necessary for the task.
+- Use targeted, specific queries - avoid broad searches or large data retrievals.

.github/workflows/smoke-aider.md

@@ -24,6 +24,7 @@ engine:
 strict: true
 imports:
   - shared/aider.md
+  - shared/smoke-test-brevity.md
 network:
   allowed: []
 tools:
@@ -58,11 +59,6 @@ sandbox:
 
 # Smoke Test: Aider Engine Validation
 
-**CRITICAL EFFICIENCY REQUIREMENTS:**
-- Keep ALL outputs extremely short and concise. Use single-line responses.
-- NO verbose explanations or unnecessary context.
-- Minimize file reading - only read what is absolutely necessary for the task.
-
 Aider has no MCP client support, so this smoke test exercises only the CLI-native
 capabilities: prompt delivery, shell commands, and file editing. Safe outputs are
 emitted by appending JSONL entries to the file referenced by `$GH_AW_SAFE_OUTPUTS`.

.github/workflows/smoke-claude.md

@@ -36,6 +36,7 @@ imports:
   - shared/github-mcp-app.md
   - shared/otlp.md
   - shared/token-telemetry-check.md
+  - shared/smoke-test-brevity.md
 network:
   allowed:
     - defaults
@@ -142,8 +143,6 @@ features:
 
 # Smoke Test: Claude Engine Validation.
 
-**IMPORTANT: Keep all outputs extremely short and concise. Use single-line responses where possible. No verbose explanations.**
-
 ## Test Requirements
 
 For tests below, mark a test as passed only if the required tool call succeeds.

.github/workflows/smoke-codex.md

@@ -33,6 +33,7 @@ imports:
   - shared/trufflehog.md
   - shared/otlp.md
   - shared/token-telemetry-check.md
+  - shared/smoke-test-brevity.md
 network:
   allowed:
     - defaults
@@ -100,12 +101,6 @@ sandbox:
 
 # Smoke Test: Codex Engine Validation
 
-**CRITICAL EFFICIENCY REQUIREMENTS:**
-- Keep ALL outputs extremely short and concise. Use single-line responses.
-- NO verbose explanations or unnecessary context.
-- Minimize file reading - only read what is absolutely necessary for the task.
-- Use targeted, specific queries - avoid broad searches or large data retrievals.
-
 ## Test Requirements
 
 1. **GitHub MCP Testing**: Use GitHub MCP tools to fetch details of exactly 2 merged pull requests from ${{ github.repository }} (title and number only, no descriptions)