Do not infer the root cause from raw pinyin.rc.8 already has three composition guards; verify the artifact and event sequence.
Route the first broken boundary.
Check clean profile, focus, remounts, injected scripts, and stale assets.
Find the first consumed key inside the composition interval.
Resolve the listener PID, CLI version, response asset, and cache.
What rc.8 proves—and does not.
Start and end handlers are attached.
Ref, isComposing, and keyCode 229 block submit.
Synthetic composition Enter does not send.
Real OS candidate-window initiation is not covered.
Acceptance contract.
Commit once; send once.
Candidates must work across pinyin, kana, and Korean IMEs; composition keys must not trigger Harness actions; ordinary Enter must recover after settlement.
Keep the full diagnostic runbook.
The canonical guide includes an isolation matrix, DevTools event fields, safe recovery order, and a real-browser regression contract.
Read the complete guide