Document installed Windows 0.1.5 and complete Google speech timing improvement

docs/SPEECH-DTW.md

@@ -1,7 +1,8 @@
 # DTW diagnostic: strict UTF-8 failure
 
-Status: internal CPU diagnosis, 2026-10-13. No accepted speech/retrieval score,
-production ASR integration or new media rating follows from this evidence.
+Status: internal CPU diagnosis and completed tiny VAD/DTW comparison, 2026-10-13.
+Production ASR integration and broader independent acceptance remain open;
+no new media rating follows from this evidence.
 Google EmbeddingGemma 2 remains the production semantic model.
 
 The original fifteen-window DTW experiment stopped on strict UTF-8 parsing.
@@ -86,3 +87,61 @@ It lacks remaining piano windows and three other competitors. Neither that
 partial report nor this one-window diagnosis can receive an accepted quality
 score. Packaging, independent bilingual speech, silence/music hallucination,
 resource peaks and actual production hybrid integration remain open.
+
+## Complete frozen VAD + DTW follow-up
+
+A subsequent separately frozen combination used the same original Silero VAD
+source intersections and base DTW point policy. All five sources remained
+explicit: twelve speech windows in NASA, and four no-speech competitors that
+launched no ASR because of the unchanged actual VAD decisions. No label selected
+the gate or removed the malformed piano window. Raw Google audio retrieval stays
+unchanged. This combination finished with zero parsing/alignment failures and
+21 sentence passages. Source/tool hashes were revalidated; the combination
+manifest SHA is `d3bf453f21dac03fd029344af2fe700480cf686d2ba5b5d7fcc79134dda1c563`.
+
+Independent Rust verification reconstructed every VAD window and DTW point from
+raw evidence before actual Google document/query CPU inference. Both models used
+one thread; indexing role retained 2048 tokens and query role 512. The normal
+auto-capable Google worker reported `google/embeddinggemma-2`, 768 dimensions,
+CPU and `b11461-no-logits-v1`. The scorer accepted the complete report with zero
+excluded windows against the unchanged eight queries.
+
+| Fixed metric | Ungated base | Frozen VAD base | Frozen VAD + DTW |
+| --- | ---: | ---: | ---: |
+| Correct top file | 8/8 | 8/8 | 8/8 |
+| Strict timestamp-start hits | 4/8 | 4/8 | **6/8** |
+| Labelled interval overlap | 6/8 | 6/8 | 6/8 |
+
+The two gains against **gated base** are the Mars queries: start changed from
+54.440 seconds, before the labelled 56.539–63.496 interval, to 58.820 seconds.
+Moon starts changed from ungated 0.000 seconds to gated-base 1.700 seconds and
+gated-DTW 1.820 seconds; both gated starts already pass the frozen 1.551–3.603
+interval. Funding queries still pass. Both orange-soil queries still fail;
+their top DTW point spans are 26.690–27.030 seconds, outside the topic. Correct
+file identity alone does not solve this missing recognized passage.
+
+These are four topics in **one English NASA recording**, with eight correlated
+English/German search queries. They do not validate German speech or independent
+accents. VAD produced no recognized passages for the four competitors, so 8/8
+file identity is especially weak evidence; all five source identities remain
+verified, but this is not broad music/no-answer quality. The direct recognized-
+text diagnostic is not production hybrid search. No production default,
+transcription integration or improved media self-rating follows.
+
+ASR process time summed to 88090.51 ms; window decoding summed to 1784.10 ms.
+This excludes probe/hash/checkpoint and the earlier VAD cost. Google indexing
+session initialization plus document encoding took 3086.03 ms, query-session
+startup 919.69 ms. Eight query/ranking measurements had median 96.83 ms and
+nearest-rank p95 128.75 ms; these tiny shared-VM measurements are not desktop
+first-input, clean-room or large-library latency. The already running user app
+retained its warmed CPU model; it received no further coordinated search inputs.
+
+| Retained ignored artifact | SHA-256 |
+| --- | --- |
+| `gated-base-dtw-results-v1.json` | `3b6a791df6503a7a4e91ed708be7b722d1c124a2cf6c5a290cd94296bebc3c41` |
+| `gated-base-dtw-google-ranks-v1.json` | `f743265a53ade09b36fef25fe4e90b70a46cd2610a12aaa976f179ab9835fe91` |
+| `gated-base-dtw-google-score-v1.json` | `4cfbc0f540ed8edcbed6e45f55fac80ee11867597152928d3407dabd7db34502` |
+| Actual Google worker | `c01cb3ec13cfca722ee768e8350e1399a8b9a4d14a24a35adc3473a5cfc82a73` |
+| Actual ranking executable | `58f4b1cf90cbf403220b60579d72ced9dd7bc795bd05a7386820e9ab84b5f519` |
+
+The original failed ungated DTW and ordinary-token reports remain unchanged.