Verify genuine Google CPU hybrid MCP from Windows archive

This commit is contained in:
karl committed 2026-10-13 11:59:33 +02:00
1 parent 3a336ca948
commit 3427abfd0f
2 files changed
+72 -6

No files matched your search

+26
View File
@@ -55,6 +55,32 @@ SHA-256 `fd5cf6244410b2373ffac38cf94e9f25b7c711737401ee96d6cb29721a1f8e51`.
python tools/windows_agent_smoke.py --cli C:/path/to/searchi-cli.exe --work-dir .searchi/qa/new-agent-smoke
```
### Genuine Google CPU package check
The same harness optionally accepts `--model-dir` and `--embedding-worker`.
It builds a new text-only semantic generation before starting hybrid MCP, with
one CPU inference thread and `SEARCHI_FORCE_CPU=1`. The meaning query
`ending a vendor relationship` must have no lexical matches, retrieve
`contract.txt` as a semantic top result, and return the original cited passage.
The report requires three actual document inference calls, not reused vectors.
The normal archive worker and all 25 DLLs were extracted alongside its CLI.
The Windows CPU check passed, including the optimized Python confirmation,
2026-10-13. Generation 1 contains three chunks; the result reports hybrid mode
and semantic availability. No test worker remained after completion; the
installed desktop's independent query worker was retained.
Ignored confirmed evidence:
`.searchi/qa/agent-mcp-google-confirmed-20261013/report.json`, SHA-256
`5d4bddbe73fdf9a30e19fece1622d0d3d9aefe4e2c19816d3df928ea78c3fde2`.
This tiny document/code fixture proves real package inference and MCP citation
integration. It does not establish broad relevance, media quality, GPU parity
or native UI latency; semantic neighbours can still include irrelevant files.
```powershell
python tools/windows_agent_smoke.py --cli C:/path/to/searchi-cli.exe --work-dir .searchi/qa/new-google-smoke --model-dir C:/path/to/verified/models --embedding-worker C:/path/to/searchi-gemma-worker.exe
```
For names/content only:
```sh