d3ro-voice/docs/evidence/2026-11-02-verification.md

29 lines
4.1 KiB
Markdown

# 2026-11-02 Windows GUI verification and typing-race follow-up
All dates below are KST. Runtime artifacts are under `test-results/recovery-2026-11-02/` (ignored). The tested installed application is `C:\Users\encep\AppData\Local\Programs\@d3rodesktop\D3RO Voice.exe`, file version **1.16.0**. No Electron process was launched from the agent shell; the existing installation was restored through its taskbar button.
## Desktop meeting import — PASS
- Restored the existing installation, opened Meetings → **녹음 파일 가져오기**, selected the real 8.498-second `local-speech.wav` through the native file picker, and reached the `local-speech` meeting detail.
- The transcript tab shows `[00:00] Hello. This is a local meeting import test. We will review the project tomorrow.` with the expected timestamp.
- **요약 만들기** used the existing local pipeline and produced a Korean summary plus `내일 프로젝트 검토 진행` as an action item; the Documents tab count is 1. No cloud or paid inference was requested.
- Screenshots: `meeting-list.png`, `meeting-import-transcript.png`, `meeting-summary-progress.png`. The test meeting was left in place; no personal data was deleted or reset.
## Native Korean IME under CPU and model load — PASS with method limits
- `installed-1.16.0-hangul.json`: calibration plus idle/CPU cases at requested 60/30/15 ms pacing, **7/7 exact matches**. All 240/240 injected events per corpus case were accepted. CPU cases used 23 bounded workers and recorded approximately 100% system CPU.
- `installed-1.16.0-hangul-model-load.json`: **7/7 exact matches**, including native IME composition evidence and all 240/240 events per corpus case.
- `/api/ps` was empty before the model test. A direct local `gemma4:e4b` generate request returned HTTP 200 in **9.389 s**, with **9.275 s model-load duration**. Its inferred request interval overlaps the report's `idle-60` and `idle-30` cases, both exact matches. This is direct Ollama cold-load overlap, not a claim about product-triggered warmup.
- The model was explicitly unloaded after the test; final `/api/ps` is empty. Responses: `ollama-cold-generate.json`, `ollama-ps-before.json`, `ollama-ps-after.json`, `ollama-ps-final.json`.
- These are synthetic scan-code tests in the fixture's own WinForms field, not physical-keyboard, Chromium, terminal, or hardware-IME proof. An initial run aborted on the fixture's foreground guard and is not counted as a pass.
## Latin-layout correction control — defect reproduced, source fixed, updated-app GUI still pending
- `installed-1.16.0-latin-control.json` passed only the IME calibration (**1/7**). The six layout-correction cases failed. Examples include `d안녕하세요`, an injected next-word `r` appearing during backspaces, and earlier words remaining unconverted.
- Installed-app logs reported successful `SendInput` replacement counts while the fixture recorded different final text. A single native call therefore does not establish that concurrent input cannot interleave with the replacement.
- Source changes, not yet shipped in the running 1.16.0 installation:
- `InputTelemetryService` waits for a 140 ms gap at a word boundary instead of taking the 40 ms snapshot during a faster burst.
- `TypoCorrectionService` does not partially correct a contiguous trailing chain during the short idle window. At the 650 ms idle checkpoint it corrects the current correction region, up to the existing 120-character core limit, in one replacement. Unrelated earlier text still does not force whole-line rewriting.
- The Win32 comment no longer claims that other processes cannot interleave input.
- Regression coverage: 140 ms rescheduling and deferral of a 120-character burst, followed by one exact Korean replacement. Targeted **48/48**, full desktop **192 files / 2,773 tests**, desktop typecheck, touched-scope lint, `git diff --check`, and production `electron-vite build` all PASS.
- The source fix has **not** been exercised in an updated Electron GUI. Re-run the same Latin control after packaging/installing the change, then expand to physical keyboard and Chromium/terminal surfaces before closing GAP-INPUT-11.