bug(web): autocorrect - typing punctuation in editing is sometimes autocorrected away

[mcdurdin]

From epic/autocorrect (19.0.276-alpha):

1. Type "hello
2. Type ". Banner shows hello highlighted.
3. Type (spacebar). Keyman deletes the previous " character.

Expected:

• Keyman keeps the punctuation that I just typed.

Screen_Recording_20260901_063008_Keep.Notes.mp4

(Low priority secondary - 'h' should really be capital there, but that's a limitation in the Eurolatin capitalization logic)

[jahorton]

I think I've figured out the underlying causes here.

1. Search-term keying for English with MTNT erases ‘ and “ characters from the context for purposes of text-correction.
2. The LexicalModel.predict method takes in a plain Context instance, not a tokenized version of the Context that is aware of all determined word-boundaries.

This thus exposes an interesting interaction where search-term keying characters that have an impact on word-boundaries can cause non-intuitive effects. So, for this case, the actual model seems a predict request without the ” present after the original "hello" and thinks that for purposes of text-correction, the incoming input may as well be empty - unaware that the correction context should now be focused on a different token.