Support optional CLI and MCP in Windows source archives

docs/AGENT-INTEGRATION.md

@@ -11,6 +11,30 @@ Build the CLI with `cargo build --release -p searchi-cli --locked`. Create and
 index files through the normal CLI/desktop workflow first. MCP requires an
 explicit existing database; it never creates a new empty database after a typo.
 
+Windows source archives can include the compiled CLI using
+`python tools/package_windows.py --cli target/release/searchi.exe`. In that
+archive, `searchi.exe` opens the desktop and `searchi-cli.exe` runs CLI/MCP
+commands. Keep both beside the bundled runtime helpers. The published v0.1.0
+installer does not include the CLI; this packaging option is for a subsequent
+archive and does not change that release.
+
+Packaging evidence, Windows VM 2026-10-13: 16 package tests passed in normal
+and optimized Python modes, including CLI checksum inventory and rejection of
+a mismatched CLI architecture without replacing the previous archive. The
+locked release CLI built successfully. An actual local archive containing the
+existing desktop release and this CLI passed size/SHA verification for all 40
+files. Its extracted `searchi-cli.exe mcp --help` executed successfully outside
+the build directory. This checks packaging and startup, not a new semantic MCP
+session, GPU behavior or a clean-machine install.
+
+Ignored archive: `.searchi/packages/searchi-windows-agent-preview.zip`,
+152,098,987 bytes, SHA-256
+`9721a657458f140dc9271b508c810ca52b7e4b89ccff8f1cd3edb053dbe591a0`.
+CLI SHA-256:
+`7b40a3959e5bca811f79e0a0da1e0cf77505ede703cf92c8394f79b9a6167ab5`.
+The archive is local only; the Gitea attachment size limit previously rejected
+even the smaller desktop archive. Published installer contents are unchanged.
+
 For names/content only:
 
 ```sh
@@ -105,4 +129,4 @@ cargo test -p searchi-cli --test mcp
 Default tests use genuine SQLite retrieval without downloaded model assets.
 Hybrid mode uses the same real Google service; it has no simulated embeddings.
 Native Linux/macOS MCP execution and cross-platform packaging require their own
-recorded checks; Windows CPU checks do not establish those releases.
+recorded checks; Windows CPU checks do not establish those releases.