{#alt(grave)} / Emily P*BLGTS translates but emits no OS key events on Windows #1870

Describe the bug

Windows + Lapwing with Emily modifiers. Stroke P*BLGTS shows up in strokes.log as {#alt(grave)}, but nothing actually gets sent to the OS. My keyboard noise app (Mechvibes) stays quiet, keyboard testers dont light up, and an app hotkey on Alt+` never fires. Pressing Alt+` on my normal keyboard works fine. Other Emily shortcuts work (Ctrl+C, Alt+A, Alt+P). Typing a backtick with Emily symbols (SKWH-P) also works. So Alt+letter is fine. Alt+grave looks like it translates but never really presses the keys.

To Reproduce

Steps to reproduce the behavior:

1. Use Lapwing with emily-modifiers.py on.
2. Bind something to Alt+` (or open a keyboard tester / key noise app).
3. Stroke P*BLGTS (or anything that outputs {#alt(grave)}).
4. Check strokes.log. You should see something like Translation(('P*BLGTS',) : "{^}{#alt(grave)}{^}").
5. Nothing happens. No noise, tester silent, hotkey doesnt fire.
6. Compare with KR-FLGTS ({#control(c)}) or P-BLGTS ({#alt(p)}). Those do send keys and the noise app hears them.
7. Compare with physical Alt+` on the QWERTY keyboard. That works.

Expected behavior

{#alt(grave)} should do the same thing as pressing Alt+` on the keyboard, same as how {#alt(p)} and {#control(c)} already work.

Screenshots

No screenshots. Log snippet:

Stroke(P*BLGTS : ['P-', '*', '-B', '-L', '-G', '-T', '-S'])
Translation(('P*BLGTS',) : "{^}{#alt(grave)}{^}")

I also tried {#Alt_L(grave)}, {#alt()}, {#Alt_L()}, {#alt(oem_3)}, and {#Alt_L(oem_3)}. Same nothing.

Operating system

• OS: Windows Windows 11 Version 25H2 (0S Build 26200.9457)
• Plover Version: Plover 5.3.0
• Keyboard layout: (US)

Hardware

Gemini PR over serial (COM port), machine type Gemini PR in Plover. Can add a machine config screenshot if needed.