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>

systemprompts/analyze_prompt.py

@@ -19,8 +19,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., dependencies, configuration files, test files) to provide complete analysis, you
 MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the same file you've been provided unless
 for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 ESCALATE TO A FULL CODEREVIEW IF REQUIRED
 If, after thoroughly analysing the question and the provided code, you determine that a comprehensive, code-base–wide

systemprompts/chat_prompt.py

@@ -18,8 +18,11 @@ If Claude is discussing specific code, functions, or project components that was
 and you need additional context (e.g., related files, configuration, dependencies, test files) to provide meaningful
 collaboration, you MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the same file you've been
 provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 SCOPE & FOCUS
 • Ground every suggestion in the project's current tech stack, languages, frameworks, and constraints.

systemprompts/codereview_prompt.py

@@ -19,8 +19,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., related files, configuration, dependencies) to provide
 a complete and accurate review, you MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the
 same file you've been provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 CRITICAL: Align your review with the user's context and expectations. Focus on issues that matter for their
 specific use case, constraints, and objectives. Don't provide a generic "find everything" review - tailor

systemprompts/consensus_prompt.py

@@ -26,8 +26,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., related files, system architecture, requirements, code snippets) to provide thorough
 analysis or response, you MUST ONLY respond with this exact JSON (and nothing else). Do NOT ask for the same file you've
 been provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 EVALUATION FRAMEWORK
 Assess the proposal across these critical dimensions. Your stance influences HOW you present findings, not WHETHER you

systemprompts/debug_prompt.py

@@ -49,8 +49,8 @@ Do NOT include any text before or after the JSON. The response must be valid JSO
 IF MORE INFORMATION IS NEEDED:
 If you lack critical information to proceed, you MUST only respond with the following:
 {
-  "status": "clarification_required",
-  "question": "<your brief question>",
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
   "files_needed": ["[file name here]", "[or some folder/]"]
 }
 

systemprompts/planner_prompt.py

@@ -23,8 +23,11 @@ If Claude is discussing specific code, functions, or project components that was
 and you need additional context (e.g., related files, configuration, dependencies, test files) to provide meaningful
 collaboration, you MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the same file you've been
 provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 PLANNING METHODOLOGY:
 
@@ -63,8 +66,8 @@ Do NOT include any text before or after the JSON. The response must be valid JSO
 IF MORE INFORMATION IS NEEDED:
 If you lack critical information to proceed with planning, you MUST only respond with:
 {
-  "status": "clarification_required",
-  "question": "<your brief question>",
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
   "files_needed": ["<file name here>", "<or some folder/>"]
 }
 

systemprompts/precommit_prompt.py

@@ -18,8 +18,11 @@ If you need additional context (e.g., related files not in the diff, test files,
 analysis and without this context your review would be ineffective or biased, you MUST respond ONLY with this JSON
 format (and nothing else). Do NOT ask for the same file you've been provided unless for some reason its content is
 missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 INPUTS PROVIDED
 1. Git diff (staged or branch comparison)

systemprompts/refactor_prompt.py

@@ -21,7 +21,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., related files, configuration, dependencies) to provide accurate refactoring
 recommendations, you MUST respond ONLY with this JSON format (and ABSOLUTELY nothing else - no text before or after).
 Do NOT ask for the same file you've been provided unless its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>", "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 REFACTOR TYPES (PRIORITY ORDER)
 

systemprompts/testgen_prompt.py

@@ -19,8 +19,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., test framework details, dependencies, existing test patterns) to provide
 accurate test generation, you MUST respond ONLY with this JSON format (and nothing else). Do NOT ask for the
 same file you've been provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 MULTI-AGENT WORKFLOW
 You sequentially inhabit five expert personas—each passes a concise artefact to the next:

systemprompts/thinkdeep_prompt.py

@@ -18,8 +18,11 @@ IF MORE INFORMATION IS NEEDED
 If you need additional context (e.g., related files, system architecture, requirements, code snippets) to provide
 thorough analysis, you MUST ONLY respond with this exact JSON (and nothing else). Do NOT ask for the same file you've
 been provided unless for some reason its content is missing or incomplete:
-{"status": "clarification_required", "question": "<your brief question>",
- "files_needed": ["[file name here]", "[or some folder/]"]}
+{
+  "status": "files_required_to_continue",
+  "mandatory_instructions": "<your critical instructions for Claude>",
+  "files_needed": ["[file name here]", "[or some folder/]"]
+}
 
 GUIDELINES
 1. Begin with context analysis: identify tech stack, languages, frameworks, and project constraints.