Bug
The interactive Unicode SendInput path accepts all injected events but the terminal never receives or echoes them on the current Windows runner.
Reproduction
pwsh -NoProfile -ExecutionPolicy Bypass -File .\test\windows\interactive-win11-accessibility.ps1 -Rebuild -ResetState -TimeoutSeconds 120 -IdleSoakSeconds 600
Observed on both the GraphCode host-integration tip and unchanged Winghostty baseline dad5599c:
- 44/44 Unicode
SendInput events accepted
- repeated UIA reads remain at
C:\Users>
- no command echo
Control:
interactive-win11-key-input.ps1 -Key unicode-bmp also times out- message-mode
-Key a passes
The accessibility harness/shared library are byte-identical between baseline and integration.
Expected
The Unicode key-input sentinel reaches the terminal or fails during a runner/foreground-desktop preflight with a specific diagnostic.
Suggested fix
Add a Unicode key-input preflight and validate the runner foreground/interactive desktop. If Unicode SendInput is unavailable, use a setup-only fallback transport rather than timing out in the accessibility scenario.
Bug
The interactive Unicode
SendInputpath accepts all injected events but the terminal never receives or echoes them on the current Windows runner.Reproduction
Observed on both the GraphCode host-integration tip and unchanged Winghostty baseline
dad5599c:SendInputevents acceptedC:\Users>Control:
interactive-win11-key-input.ps1 -Key unicode-bmpalso times out-Key apassesThe accessibility harness/shared library are byte-identical between baseline and integration.
Expected
The Unicode key-input sentinel reaches the terminal or fails during a runner/foreground-desktop preflight with a specific diagnostic.
Suggested fix
Add a Unicode key-input preflight and validate the runner foreground/interactive desktop. If Unicode
SendInputis unavailable, use a setup-only fallback transport rather than timing out in the accessibility scenario.