Merge branch 'main' into redesign_config

Author: Agent-Hellboy

.github/workflows/system-test.yml renamed to .github/workflows/e2e-test.yml

@@ -1,4 +1,4 @@
-name: System Test with Safety
+name: E2E Test with Safety
 
 on:
   push:
@@ -23,7 +23,7 @@ on:
         type: string
 
 jobs:
-  system-test:
+  e2e-test:
     runs-on: ubuntu-latest
     timeout-minutes: 15
 
@@ -80,18 +80,18 @@ jobs:
     - name: Run safety check
       run: |
         echo "🔒 Running pre-flight safety check..."
-        chmod +x tests/system/check_safety.sh
-        ./tests/system/check_safety.sh
+        chmod +x tests/e2e/check_safety.sh
+        ./tests/e2e/check_safety.sh
 
-    - name: Run system test with safety system
+    - name: Run e2e test with safety system
       env:
         TEST_MODE: ${{ github.event.inputs.test_mode || 'tools' }}
         RUNS_PER_TOOL: ${{ github.event.inputs.runs_per_tool || '3' }}
         MCP_FUZZER_TIMEOUT: '30'
         MCP_FUZZER_SAFETY_ENABLED: 'true'
         MCP_FUZZER_FS_ROOT: '/tmp/mcp_fuzzer_sandbox'
       run: |
-        echo "🧪 Running system test with safety system enabled"
+        echo "🧪 Running e2e test with safety system enabled"
         echo "Test Mode: $TEST_MODE"
         echo "Runs per tool: $RUNS_PER_TOOL"
         echo "Working Directory: $(pwd)"
@@ -104,15 +104,15 @@ jobs:
         python --version
         node --version
 
-        # Run the system test
-        chmod +x tests/system/test_desktop_commander_mcp.sh
-        ./tests/system/test_desktop_commander_mcp.sh
+        # Run the e2e test
+        chmod +x tests/e2e/test_desktop_commander_mcp.sh
+        ./tests/e2e/test_desktop_commander_mcp.sh
 
     - name: Upload test results
       if: always()
       uses: actions/upload-artifact@v4
       with:
-        name: system-test-results-${{ github.run_id }}
+        name: e2e-test-results-${{ github.run_id }}
         path: |
           reports/
           test-results/
@@ -121,7 +121,7 @@ jobs:
     - name: Generate test summary
       if: always()
       run: |
-        echo "## 🧪 System Test Results" >> $GITHUB_STEP_SUMMARY
+        echo "## 🧪 E2E Test Results" >> $GITHUB_STEP_SUMMARY
         echo "" >> $GITHUB_STEP_SUMMARY
 
         if [ -d "reports" ]; then

.gitignore

@@ -16,6 +16,8 @@ test.py
 sdks/
 doc_ref/
 # C extensions
+*REDESIGN*.md
+*FLOW.md
 *.so
 notes.md
 /reports/

README.md

@@ -218,6 +218,10 @@ The system is built with a modular architecture:
 - **Authentication**: Multiple auth provider support
 - **Reporting**: FuzzerReporter, Console/JSON/Text formatters, SafetyReporter
 
+### Runtime Watchdog Overview
+
+The watchdog supervises processes registered through `ProcessManager`, combining hang detection, signal dispatch, and registry-driven cleanup. For a deeper dive into lifecycle events, custom signal strategies, and registry wiring, see the [runtime management guide](docs/components/runtime-management.md).
+
 ### Understanding the Design Patterns
 
 For developers (beginners to intermediate) who want to understand the design patterns used throughout the codebase, please refer to our comprehensive [Design Pattern Review](docs/design-pattern-review.md). This document provides:

docs/SECURITY_CI.md

@@ -4,7 +4,7 @@
 
 ### ✅ SAFE FOR CI/CD EXECUTION
 
-The system test script can be safely run in GitHub Actions with the following security measures:
+The e2e test script can be safely run in GitHub Actions with the following security measures:
 
 ## 🔒 Security Safeguards
 
@@ -44,15 +44,15 @@ google-chrome, safari, edge, opera, brave
 ### Recommended GitHub Actions Workflow
 
 ```yaml
-name: System Test with Safety
+name: E2E Test with Safety
 on:
   push:
     branches: [ main, develop ]
   pull_request:
     branches: [ main ]
 
 jobs:
-  system-test:
+  e2e-test:
     runs-on: ubuntu-latest
     timeout-minutes: 15
 
@@ -70,13 +70,13 @@ jobs:
         cd testing-servers/DesktopCommanderMCP
         npm ci && npm run build
 
-    - name: Run system test
+    - name: Run e2e test
       env:
         MCP_FUZZER_SAFETY_ENABLED: 'true'
         MCP_FUZZER_TIMEOUT: '30'
       run: |
-        chmod +x tests/system/test_desktop_commander_mcp.sh
-        ./tests/system/test_desktop_commander_mcp.sh
+        chmod +x tests/e2e/test_desktop_commander_mcp.sh
+        ./tests/e2e/test_desktop_commander_mcp.sh
 
     - name: Upload results
       uses: actions/upload-artifact@v4
@@ -142,12 +142,12 @@ MCP_FUZZER_FS_ROOT=/tmp/mcp_fuzzer_sandbox
 
 ## 🎯 Conclusion
 
-**The system test script is SAFE for GitHub Actions execution** with:
+**The e2e test script is SAFE for GitHub Actions execution** with:
 
 - ✅ **Comprehensive safety system** preventing dangerous operations
 - ✅ **CI environment isolation** providing additional security layer
 - ✅ **Resource controls** preventing resource exhaustion
 - ✅ **Artifact isolation** controlling data exposure
 - ✅ **Automatic cleanup** preventing persistent state
 
-The combination of the MCP fuzzer's built-in safety system and GitHub Actions' security model provides multiple layers of protection, making this system test suitable for automated CI/CD pipelines.
+The combination of the MCP fuzzer's built-in safety system and GitHub Actions' security model provides multiple layers of protection, making this e2e test suitable for automated CI/CD pipelines.

docs/components/process-management-guide.md

@@ -7,6 +7,7 @@ This guide provides comprehensive information on managing processes, configuring
 ### Starting Processes
 
 When starting processes with the ProcessManager, follow these best practices:
+Use `ProcessManager.from_config(...)` for the default runtime wiring, or build your own dependencies and pass them to the `ProcessManager` constructor when you need custom registries, signal strategies, or watchdog settings.
 
 #### 1. Use Descriptive Names
 
@@ -105,7 +106,7 @@ async def periodic_activity_update(manager, pid, interval=5.0):
 
 ```python
 async def graceful_shutdown_example():
-    manager = ProcessManager()
+    manager = ProcessManager.from_config()
 
     # Start process
     config = ProcessConfig(command=["python", "server.py"], name="server")
@@ -135,7 +136,7 @@ if not success:
 ### Basic Configuration
 
 ```python
-from mcp_fuzzer.fuzz_engine.runtime.watchdog import WatchdogConfig
+from mcp_fuzzer.fuzz_engine.runtime import WatchdogConfig
 
 # Conservative settings for production
 production_config = WatchdogConfig(
@@ -201,7 +202,7 @@ prod_config = WatchdogConfig(
 ```python
 async def managed_process_example():
     watchdog_config = WatchdogConfig(auto_kill=True)
-    manager = ProcessManager(watchdog_config)
+    manager = ProcessManager.from_config(watchdog_config)
 
     # Processes are automatically registered with watchdog
     config = ProcessConfig(command=["python", "server.py"], name="server")
@@ -215,25 +216,36 @@ async def managed_process_example():
 
 #### Standalone Watchdog
 
+```python
+import asyncio
+import logging
+
+from mcp_fuzzer.fuzz_engine.runtime import (
+    ProcessConfig,
+    ProcessRegistry,
+    ProcessWatchdog,
+    SignalDispatcher,
+    WatchdogConfig,
+)
+
+logger = logging.getLogger(__name__)
+```
+
 ```python
 async def standalone_watchdog_example():
-    watchdog = ProcessWatchdog(WatchdogConfig())
+    registry = ProcessRegistry()
+    signals = SignalDispatcher(registry, logging.getLogger(__name__))
+    watchdog = ProcessWatchdog(registry, signals, WatchdogConfig())
 
-    # Start monitoring
     await watchdog.start()
-
-    # Register existing process
     process = await asyncio.create_subprocess_exec("python", "server.py")
-    await watchdog.register_process(
+    await registry.register(
         process.pid,
         process,
-        None,  # No activity callback
-        "server"
+        ProcessConfig(command=["python", "server.py"], name="server"),
     )
-
-    # Monitor for a while
+    await watchdog.update_activity(process.pid)
     await asyncio.sleep(30)
-
     await watchdog.stop()
 ```
 

docs/components/process-management.md

@@ -84,40 +84,47 @@ asyncio.run(main())
 
 ### ProcessWatchdog
 
-The core watchdog system that monitors processes for hanging behavior.
+The core watchdog system that monitors processes for hanging behavior. It reads
+from a shared `ProcessRegistry` instead of keeping its own process table.
 
 ```python
-from mcp_fuzzer.fuzz_engine.runtime import ProcessWatchdog, WatchdogConfig
 import asyncio
-import asyncio.subprocess as asp
+import logging
+from mcp_fuzzer.fuzz_engine.runtime import (
+    ProcessConfig,
+    ProcessRegistry,
+    ProcessWatchdog,
+    SignalDispatcher,
+    WatchdogConfig,
+)
+
 
 async def main():
-    # Custom configuration
-    config = WatchdogConfig(
-        check_interval=1.0,      # Check every second
-        process_timeout=30.0,    # Process timeout after 30 seconds
-        extra_buffer=5.0,        # Extra 5 seconds before killing
-        max_hang_time=60.0,      # Force kill after 60 seconds
-        auto_kill=True,          # Automatically kill hanging processes
+    registry = ProcessRegistry()
+    signals = SignalDispatcher(registry, logging.getLogger(__name__))
+    watchdog = ProcessWatchdog(
+        registry,
+        signals,
+        WatchdogConfig(check_interval=1.0, process_timeout=30.0, auto_kill=True),
     )
-
-    watchdog = ProcessWatchdog(config)
     await watchdog.start()
 
-    # Launch a subprocess to register
-    process = await asp.create_subprocess_exec("python", "-c", "import time; time.sleep(60)")
-
-    # Register a process for monitoring
-    await watchdog.register_process(
+    process = await asyncio.create_subprocess_exec(
+        "python", "-c", "import time; time.sleep(60)"
+    )
+    await registry.register(
         pid=process.pid,
         process=process,
-        activity_callback=None,
-        name="my_process",
+        config=ProcessConfig(
+            command=["python", "-c", "import time; time.sleep(60)"],
+            name="my_process",
+        ),
     )
-
-    # Some time later...
+    await watchdog.update_activity(process.pid)
+    await watchdog.scan_once(await registry.snapshot())
     await watchdog.stop()
 
+
 asyncio.run(main())
 ```
 
@@ -130,7 +137,8 @@ from mcp_fuzzer.fuzz_engine.runtime import ProcessManager, ProcessConfig
 import asyncio
 
 async def main():
-    manager = ProcessManager()
+    # Default wiring via factory (watchdog, registry, signals, lifecycle, monitor)
+    manager = ProcessManager.from_config()
 
     # Start a process
     config = ProcessConfig(
@@ -145,7 +153,7 @@ async def main():
     print(f"Process started with PID: {process.pid}")
 
     # Wait for completion
-    exit_code = await manager.wait_for_process(process.pid, timeout=120.0)
+    exit_code = await manager.wait(process.pid, timeout=120.0)
 
     # Get statistics
     stats = await manager.get_stats()
@@ -234,7 +242,7 @@ from mcp_fuzzer.fuzz_engine.runtime import ProcessManager, ProcessConfig
 
 async def main():
     # Create manager
-    manager = ProcessManager()
+    manager = ProcessManager.from_config()
 
     try:
         # Start a long-running process
@@ -268,7 +276,7 @@ import asyncio
 from mcp_fuzzer.fuzz_engine.runtime import ProcessManager, ProcessConfig
 
 async def run_multiple_processes():
-    manager = ProcessManager()
+    manager = ProcessManager.from_config()
 
     try:
         # Start multiple processes concurrently
@@ -284,7 +292,7 @@ async def run_multiple_processes():
         processes = await asyncio.gather(*tasks)
 
         # Wait for all to complete
-        wait_tasks = [manager.wait_for_process(process.pid) for process in processes]
+        wait_tasks = [manager.wait(process.pid) for process in processes]
         results = await asyncio.gather(*wait_tasks)
         print(f"All processes completed with exit codes: {results}")
 
@@ -317,7 +325,7 @@ class CustomProcess:
 
 async def main():
     # Create process manager
-    manager = ProcessManager()
+    manager = ProcessManager.from_config()
 
     # Create custom process
     custom_proc = CustomProcess()
@@ -353,7 +361,7 @@ import asyncio
 from mcp_fuzzer.fuzz_engine.runtime import ProcessManager, ProcessConfig
 
 async def main():
-    manager = ProcessManager()
+    manager = ProcessManager.from_config()
 
     try:
         # Start a long-running process
@@ -429,6 +437,6 @@ The Process Management system integrates seamlessly with the MCP Fuzzer architec
 
 For complete API documentation, see the individual module docstrings:
 
-- `mcp_fuzzer.fuzz_engine.runtime.watchdog`
+- `mcp_fuzzer.fuzz_engine.runtime`
 - `mcp_fuzzer.fuzz_engine.runtime.manager`
 - `mcp_fuzzer.fuzz_engine.executor`