feat(opencode): Enforce Manual Slop MCP tools across all agents

.opencode/commands/conductor-implement.md

@@ -11,25 +11,34 @@ Resume or start implementation of the active track following TDD protocol.
 - Run `/conductor-setup` first to load context
 - Ensure a track is active (has `[~]` tasks)
 
+## CRITICAL: Use MCP Tools Only
+
+All research and file operations must use Manual Slop's MCP tools:
+- `manual-slop_py_get_code_outline` - structure analysis
+- `manual-slop_py_get_skeleton` - signatures + docstrings
+- `manual-slop_py_find_usages` - find references
+- `manual-slop_get_git_diff` - recent changes
+- `manual-slop_run_powershell` - shell commands
+
 ## Implementation Protocol
 
 1. **Identify Current Task:**
-   - Read active track's `plan.md`
+   - Read active track's `plan.md` via `manual-slop_read_file`
    - Find the first `[~]` (in-progress) or `[ ]` (pending) task
    - If phase has no pending tasks, move to next phase
 
 2. **Research Phase (MANDATORY):**
-   Before implementing, use tools to understand context:
-   - `py_get_code_outline` on target files
-   - `py_get_skeleton` on dependencies
-   - `grep` for related patterns
-   - `get_git_diff` for recent changes
+   Before implementing, use MCP tools to understand context:
+   - `manual-slop_py_get_code_outline` on target files
+   - `manual-slop_py_get_skeleton` on dependencies
+   - `manual-slop_py_find_usages` for related patterns
+   - `manual-slop_get_git_diff` for recent changes
    - Audit `__init__` methods for existing state
 
 3. **TDD Cycle:**
 
    ### Red Phase (Write Failing Tests)
-   - Stage current progress: `git add .`
+   - Stage current progress: `manual-slop_run_powershell` with `git add .`
    - Delegate test creation to @tier3-worker:
      ```
      @tier3-worker
@@ -41,13 +50,13 @@ Resume or start implementation of the active track following TDD protocol.
      HOW: Use pytest, assert [expected behavior]
      SAFETY: [thread-safety constraints]
      
-     Use 1-space indentation.
+     Use 1-space indentation. Use MCP tools only.
      ```
-   - Run tests: `uv run pytest tests/test_file.py -v`
+   - Run tests: `manual-slop_run_powershell` with `uv run pytest tests/test_file.py -v`
    - **CONFIRM TESTS FAIL** - this is the Red phase
 
    ### Green Phase (Implement to Pass)
-   - Stage current progress: `git add .`
+   - Stage current progress: `manual-slop_run_powershell` with `git add .`
    - Delegate implementation to @tier3-worker:
      ```
      @tier3-worker
@@ -59,9 +68,9 @@ Resume or start implementation of the active track following TDD protocol.
      HOW: [API calls, patterns to use]
      SAFETY: [thread-safety constraints]
      
-     Use 1-space indentation.
+     Use 1-space indentation. Use MCP tools only.
      ```
-   - Run tests: `uv run pytest tests/test_file.py -v`
+   - Run tests: `manual-slop_run_powershell` with `uv run pytest tests/test_file.py -v`
    - **CONFIRM TESTS PASS** - this is the Green phase
 
    ### Refactor Phase (Optional)
@@ -69,6 +78,7 @@ Resume or start implementation of the active track following TDD protocol.
    - Re-run tests to verify
 
 4. **Commit Protocol (ATOMIC PER-TASK):**
+   Use `manual-slop_run_powershell`:
    ```powershell
    git add .
    git commit -m "feat(scope): description"
@@ -90,7 +100,7 @@ If tests fail after Green phase:
   
   [test output]
   
-  DO NOT fix - provide analysis only.
+  DO NOT fix - provide analysis only. Use MCP tools only.
   ```
 - Maximum 2 fix attempts before escalating to user
 

.opencode/commands/conductor-verify.md

@@ -11,23 +11,31 @@ Execute phase completion verification and create checkpoint.
 - All tasks in the current phase must be marked `[x]`
 - All changes must be committed
 
+## CRITICAL: Use MCP Tools Only
+
+All operations must use Manual Slop's MCP tools:
+- `manual-slop_read_file` - read files
+- `manual-slop_get_git_diff` - check changes
+- `manual-slop_run_powershell` - shell commands
+
 ## Verification Protocol
 
 1. **Announce Protocol Start:**
    Inform user that phase verification has begun.
 
 2. **Determine Phase Scope:**
-   - Find previous phase checkpoint SHA in `plan.md`
+   - Find previous phase checkpoint SHA in `plan.md` via `manual-slop_read_file`
    - If no previous checkpoint, scope is all changes since first commit
 
 3. **List Changed Files:**
+   Use `manual-slop_run_powershell`:
    ```powershell
    git diff --name-only <previous_checkpoint_sha> HEAD
    ```
 
 4. **Verify Test Coverage:**
    For each code file changed (exclude `.json`, `.md`, `.yaml`):
-   - Check if corresponding test file exists
+   - Check if corresponding test file exists via `manual-slop_search_files`
    - If missing, create test file via @tier3-worker
 
 5. **Execute Tests in Batches:**
@@ -38,6 +46,8 @@ Execute phase completion verification and create checkpoint.
    I will now run: uv run pytest tests/test_file1.py tests/test_file2.py -v
    ```
    
+   Use `manual-slop_run_powershell` to execute.
+   
    If tests fail with large output:
    - Pipe to log file
    - Delegate analysis to @tier4-qa
@@ -60,6 +70,7 @@ Execute phase completion verification and create checkpoint.
    **PAUSE** and wait for explicit user approval before proceeding.
 
 8. **Create Checkpoint:**
+   Use `manual-slop_run_powershell`:
    ```powershell
    git add .
    git commit --allow-empty -m "conductor(checkpoint): Phase {N} complete"
@@ -69,6 +80,7 @@ Execute phase completion verification and create checkpoint.
 
 9. **Update Plan:**
    - Add `[checkpoint: {sha}]` to phase heading in `plan.md`
+   - Use `manual-slop_set_file_slice` or `manual-slop_read_file` + write
    - Commit: `git add plan.md && git commit -m "conductor(plan): Mark phase complete"`
 
 10. **Announce Completion:**