chore(conductor): Update workflow with API hook verification guidelines

conductor/workflow.md

@@ -120,6 +120,20 @@ All tasks follow a strict lifecycle:
 
 10.  **Announce Completion:** Inform the user that the phase is complete and the checkpoint has been created, with the detailed verification report attached as a git note.
 
+### Verification via API Hooks
+
+For features involving the GUI or complex internal state, unit tests are often insufficient. You MUST use the application's built-in API hooks for empirical verification:
+
+1.  **Launch the App with Hooks:** Run the application in a separate shell with the `--enable-test-hooks` flag:
+    ```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
+    ```
+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
 
 Before marking any task complete, verify: