Chrome/Edge randomly stops accepting keyboard & scanner input on Android 11/13 handheld, Gboard session error in logs (Honeywell EDA52)

Device: Honeywell EDA52 (Android 11/13, build TKQ1.230420.001)
Browser: Reproduced on both Chrome (151.0.7922.139) and Microsoft Edge, same symptom on both
Not affected: Honeywell CT32 devices on the same network/site; EDA52 devices in other locations running the same MDM profile
Problem
On a subset of our Android 11/13 handheld scanners, the browser randomly stops accepting any text input, both from the physical/on-screen keyboard and from an attached barcode scanner that injects input as keystrokes. This happens intermittently during normal use of a web-based app (not site-specific, happens on any input field in any website, including a plain Google search box).
Symptoms when it occurs:

• Tapping a key on the on-screen keyboard shows the normal "key press" visual highlight, but no character appears in the field.
• A connected barcode scanner still fires (beep and aiming light activate normally), but again nothing populates the field.
• Copy/paste into the same field still works, so the field itself has focus and isn't disabled; only live keystroke/scan input fails to commit.
• Switching the active input method (tested both Gboard and a manufacturer-supplied keyboard) doesn't fix it, the same freeze persists regardless of which IME is active.
• Non-browser apps (tested: Contacts) are unaffected and accept input normally while the browser is stuck.
• Fully force-closing and reopening the browser is the only reliable fix. Locking/unlocking the screen sometimes helps but is inconsistent.

What we found in logcat
We managed to capture a logcat during an active freeze. Right around the moment of the failed scan/keypress, we see this repeating:
GoogleInputMethodService: SessionManager.beginSession(): Try to begin an already begun session [INPUT_SESSION], end it first SessionManager.endSession(): Child session [INPUT_VIEW_SESSION] is not ended while ending session [...] ending it now. InputBundle.consumeEvent(): Skip consuming an event as keyboard status is 0
That last line appears to be the direct cause. The IME session state machine is in a "begin session while already begun" conflict, and while in that state it explicitly skips/drops the incoming input event rather than passing it through. This seems to get triggered when a text field's focus changes quickly (for example, a page auto-advancing to the next input field right after a keystroke/scan is submitted), faster than the IME's session teardown/restart cycle can keep up with.
Questions for the community

• Has anyone else seen "Try to begin an already begun session [INPUT_SESSION]" in logcat, on this or other Android 13 devices?
• Is this a known Gboard/InputMethodManagerService bug with a tracked fix, or an interaction specific to certain OEM Android builds?
• Any known workaround short of fully closing/reopening the browser each time, for example a way to force the IME session to reset without killing the app?