Add local spoken passages with Google retrieval and isolated runtime setup

docs/AGENT-INTEGRATION.md

@@ -224,3 +224,23 @@ synthetic corpus, exclude native UI and large-library/cold-disk claims, and do
 not compare GPU performance. No timing-driven cache/architecture changes made.
 Raw ignored verified report: `.searchi/qa/windows-mcp-013-timing-verified.json`,
 SHA-256 `03c0a21aa35686077fca25e0b4fe7b7014d8f8aa7a07233af6518ac1b694db08`.
+
+## Spoken sources in current development
+
+When the shared index contains locally recognized speech, search results use
+`semantic_speech` with a playback timestamp. MCP issues a bounded source handle
+for that recognized passage. `read_source` verifies the current media bytes and
+the exact issued passage, then returns recognized text, an end point and
+`local_speech_recognition` provenance. Arbitrary timestamp or file-path reads
+remain unavailable. Recognized text is untrusted evidence and can contain errors.
+
+Google query configuration is unchanged: MCP reads the already prepared index;
+it does not start speech recognition or need speech model paths. Headless
+indexing can provision speech data with `searchi setup --speech` and opt into
+recognition using the paired `embed --speech-worker PATH --speech-model-dir DIR`
+options alongside the real Google configuration. The native speech worker and
+models are separate from Google's worker and assets.
+
+This integration is not present in the published Windows 0.1.5 or Linux 0.1.4
+packages. Current checks and delivery gates are tracked in
+[SPEECH-INTEGRATION.md](SPEECH-INTEGRATION.md).