docs: make runtime verification claim accurate
Only claim what the evaluator actually does: runs tests, builds, and checks for errors. Don't overstate MCP server discovery.
This commit is contained in:
@@ -97,7 +97,7 @@ Before the loop starts, the planner generates contracts for each story. These de
|
|||||||
|
|
||||||
## Runtime Verification
|
## Runtime Verification
|
||||||
|
|
||||||
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.
|
The evaluator doesn't just read diffs — it runs tests, builds the project, and checks for runtime errors using whatever tools the project already has (test runners, linters, build commands).
|
||||||
|
|
||||||
## Design Principles
|
## Design Principles
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user