conductor(checkpoint): Checkpoint end of Phase 1: Infrastructure & Core Utilities

conductor/workflow.md

@@ -128,11 +128,21 @@ For features involving the GUI or complex internal state, unit tests are often i
     ```powershell
     uv run python gui.py --enable-test-hooks
     ```
-2.  **Verify via REST Commands:** Use PowerShell or `curl` to send commands to the application and verify the response. For example, to check performance metrics:
-    ```powershell
-    Invoke-RestMethod -Uri "http://localhost:5000/get_ui_performance" -Method Post
+    This starts the hook server on port `8999`.
+
+2.  **Use the pytest `live_gui` Fixture:** For automated tests, use the session-scoped `live_gui` fixture defined in `tests/conftest.py`. This fixture handles the lifecycle (startup/shutdown) of the application with hooks enabled.
+    ```python
+    def test_my_feature(live_gui):
+        # The GUI is now running on port 8999
+        ...
+    ```
+
+3.  **Verify via ApiHookClient:** Use the `ApiHookClient` in `api_hook_client.py` to interact with the running application. It includes robust retry logic and health checks.
+
+4.  **Verify via REST Commands:** Use PowerShell or `curl` to send commands to the application and verify the response. For example, to check health:
+    ```powershell
+    Invoke-RestMethod -Uri "http://127.0.0.1:8999/status" -Method Get
     ```
-3.  **Automate in Tasks:** When a task requires "User Manual Verification" or "API Hook Verification", you should script these REST calls to ensure repeatable, objective results.
 
 ### Quality Gates