Migration from Docker to Standalone Python Server (#73)

* Migration from docker to standalone server
Migration handling
Fixed tests
Use simpler in-memory storage
Support for concurrent logging to disk
Simplified direct connections to localhost

* Migration from docker / redis to standalone script
Updated tests
Updated run script
Fixed requirements
Use dotenv
Ask if user would like to install MCP in Claude Desktop once
Updated docs

* More cleanup and references to docker removed

* Cleanup

* Comments

* Fixed tests

* Fix GitHub Actions workflow for standalone Python architecture

- Install requirements-dev.txt for pytest and testing dependencies
- Remove Docker setup from simulation tests (now standalone)
- Simplify linting job to use requirements-dev.txt
- Update simulation tests to run directly without Docker

Fixes unit test failures in CI due to missing pytest dependency.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* Remove simulation tests from GitHub Actions

- Removed simulation-tests job that makes real API calls
- Keep only unit tests (mocked, no API costs) and linting
- Simulation tests should be run manually with real API keys
- Reduces CI costs and complexity

GitHub Actions now only runs:
- Unit tests (569 tests, all mocked)
- Code quality checks (ruff, black)

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

* Fixed tests

* Fixed tests

---------

Co-authored-by: Claude <noreply@anthropic.com>

tools/codereview.py

@@ -25,14 +25,16 @@ from .base import BaseTool, ToolRequest
 
 # Field descriptions to avoid duplication between Pydantic and JSON schema
 CODEREVIEW_FIELD_DESCRIPTIONS = {
-    "files": "Code files or directories to review (must be FULL absolute paths to real files / folders - DO NOT SHORTEN)",
+    "files": "Code files or directories to review that are relevant to the code that needs review or are closely "
+    "related to the code or component that needs to be reviewed (must be FULL absolute paths to real files / folders - DO NOT SHORTEN)."
+    "Validate that these files exist on disk before sharing and only share code that is relevant.",
     "prompt": (
         "User's summary of what the code does, expected behavior, constraints, and review objectives. "
-        "IMPORTANT: Before using this tool, Claude should first perform its own preliminary review - "
+        "IMPORTANT: Before using this tool, you should first perform its own preliminary review - "
         "examining the code structure, identifying potential issues, understanding the business logic, "
-        "and noting areas of concern. Include Claude's initial observations about code quality, potential "
+        "and noting areas of concern. Include your initial observations about code quality, potential "
         "bugs, architectural patterns, and specific areas that need deeper scrutiny. This dual-perspective "
-        "approach (Claude's analysis + external model's review) provides more comprehensive feedback and "
+        "approach (your analysis + external model's review) provides more comprehensive feedback and "
         "catches issues that either reviewer might miss alone."
     ),
     "images": (
@@ -299,7 +301,7 @@ Please provide a code review aligned with the user's context and expectations, f
 
 ---
 
-**Claude's Next Steps:**
+**Your Next Steps:**
 
 1. **Understand the Context**: First examine the specific functions, files, and code sections mentioned in """
         """the review to understand each issue thoroughly.