Verify extracted Windows CLI through actual MCP search and citations

docs/AGENT-INTEGRATION.md

@@ -35,6 +35,26 @@ CLI SHA-256:
 The archive is local only; the Gitea attachment size limit previously rejected
 even the smaller desktop archive. Published installer contents are unchanged.
 
+### Extracted CLI MCP verification
+
+`tools/windows_agent_smoke.py` additionally executes the extracted CLI against
+a new owned three-file corpus. It checks the real stdio handshake, the exact
+three read-only tools, document search and cited passage, rejection of invented
+source handles, and exclusion of an ordinary document containing the same code
+symbol under `code_only`. Each response has a 15-second deadline; only the
+owned MCP subprocess is terminated. The fixture/evidence directory is retained
+and an existing directory is never reused or deleted.
+
+Both normal and optimized Python runs passed on the Windows VM, 2026-10-13,
+using the archive CLI hash above. This validates actual lexical MCP behavior
+from the package, not semantic readiness, media helpers or GPU execution.
+Optimized-run evidence: `.searchi/qa/agent-mcp-smoke-optimized-20261013/report.json`,
+SHA-256 `fd5cf6244410b2373ffac38cf94e9f25b7c711737401ee96d6cb29721a1f8e51`.
+
+```powershell
+python tools/windows_agent_smoke.py --cli C:/path/to/searchi-cli.exe --work-dir .searchi/qa/new-agent-smoke
+```
+
 For names/content only:
 
 ```sh