From 9fd428ac51809d1abef690553c990002bd9cb5cb Mon Sep 17 00:00:00 2001
From: Sheldon Finlay <sheldon@outerlimitsmedia.com>
Date: Sat, 28 Mar 2026 12:19:50 -0400
Subject: [PATCH] docs: replace specific MCP recommendations with general
 guidance
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Avoid maintaining specific install commands that will go stale.
The evaluator uses whatever tools are available — let users
configure their own testing environment.
---
 README.md | 22 ++--------------------
 1 file changed, 2 insertions(+), 20 deletions(-)

diff --git a/README.md b/README.md
index b391e00..3a212e5 100644
--- a/README.md
+++ b/README.md
@@ -95,27 +95,9 @@ Before the loop starts, the planner generates contracts for each story. These de
 | `config.json` | Harness configuration |
 | Git commits | Code changes with story-tagged messages |
 
-## Optional: Runtime Testing Tools
+## Runtime Verification
 
-The evaluator verifies code actually runs, not just that it looks correct. It uses whatever tools are available. For richer verification, install these optional MCP servers:
-
-**Web projects (Playwright):**
-```bash
-claude mcp add playwright npx @playwright/mcp@latest --headless --browser=chromium
-```
-
-**iOS/Xcode projects (XcodeBuildMCP):**
-```bash
-brew tap getsentry/xcodebuildmcp && brew install xcodebuildmcp
-claude mcp add xcodebuild -- xcodebuildmcp
-```
-
-**iOS Simulator interaction:**
-```bash
-claude mcp add ios-simulator -- npx -y ios-simulator-mcp
-```
-
-These are optional — the evaluator works without them but may miss runtime-only issues.
+The evaluator verifies code actually runs, not just that it looks correct. It uses whatever testing tools are available in your environment — test runners, linters, build tools, and any MCP servers you have installed (e.g., browser automation, simulator interaction). The more verification tools available, the more thorough the evaluator can be.
 
 ## Design Principles