Remove idempotency verification and unused output_mode config

- Don't enforce idempotency, just document it as expected behavior
- Give lint formatters (black, ruff, prettier) as good examples
- Remove output_mode from config (not referenced elsewhere)
- Remove idempotency verification test scenarios

Author: claude

doc/policy_syntax.md

@@ -237,11 +237,7 @@ action:
 
 **Idempotency Requirement:**
 
-Commands MUST be idempotent. The system verifies this by:
-1. Running the command
-2. Checking for changes
-3. If changes occurred, running again
-4. If more changes occur, marking as failed
+Commands should be idempotent—running them multiple times produces the same result. Lint formatters like `black`, `ruff format`, and `prettier` are good examples: they produce consistent output regardless of how many times they run.
 
 ## Pattern Syntax
 

doc/policy_system_design.md

@@ -74,7 +74,7 @@ action:
   run_for: each_match
 ```
 
-Command actions execute idempotent commands. The system verifies idempotency by running the command twice and checking that no additional changes occur.
+Command actions should be idempotent—running them multiple times produces the same result. Lint formatters like `black`, `ruff format`, and `prettier` are good examples.
 
 ## Architecture
 
@@ -471,7 +471,6 @@ In `.deepwork/config.yml`:
 policy:
   enabled: true
   policies_dir: .deepwork/policies  # Can be customized
-  output_mode: batched  # batched or individual
 ```
 
 ## Performance Considerations

doc/test_scenarios.md

@@ -199,22 +199,14 @@ action:
 | CMD-5.2.1 | Multiple files | `["a.js", "b.js", "c.js"]` | `eslint --fix a.js b.js c.js` |
 | CMD-5.2.2 | Single file | `["a.js"]` | `eslint --fix a.js` |
 
-### 5.3 Idempotency Verification
-
-| ID | Scenario | First Run | Second Run | Expected Result |
-|----|----------|-----------|------------|-----------------|
-| CMD-5.3.1 | Truly idempotent | Changes files | No changes | Pass |
-| CMD-5.3.2 | Not idempotent | Changes files | Changes files | Fail |
-| CMD-5.3.3 | No changes needed | No changes | (not run) | Pass |
-
-### 5.4 Command Errors
+### 5.3 Command Errors
 
 | ID | Scenario | Command Result | Expected |
 |----|----------|----------------|----------|
-| CMD-5.4.1 | Exit code 0 | Success | Pass |
-| CMD-5.4.2 | Exit code 1 | Failure | Fail, show stderr |
-| CMD-5.4.3 | Timeout | Command hangs | Fail, timeout error |
-| CMD-5.4.4 | Command not found | Not executable | Fail, not found error |
+| CMD-5.3.1 | Exit code 0 | Success | Pass |
+| CMD-5.3.2 | Exit code 1 | Failure | Fail, show stderr |
+| CMD-5.3.3 | Timeout | Command hangs | Fail, timeout error |
+| CMD-5.3.4 | Command not found | Not executable | Fail, not found error |
 
 ## 6. Queue System