Practical near-term fix for the larger issue 906950.

This is a short-term *mitigation*, rather than a *fix*. 

E.g. In perfectly legit and common use cases, user may wanna input some punctuation mark, say open a square bracket "[", after dot-then-space. Having an unexpectedly Shift-ed layout could then be frustrating, as user will get an open brace "{" instead. Example given for US-Qwerty, more can be shown for other layouts, and for languages where it's common to have space-following punctuation marks).

Not all Android/iOS "mobile" solutions automatically work on CrOS, because we have to support full-fledged PK layouts and our VK layouts must more-or-less match industry-standard PK layouts. On mobile, PK use case is extremely low, and on-screen VK can be re-arranged, simplified, and optimised kinda freely. E.g. if normal and shift-state layouts contain only alphabetic letters in matching lowercase-uppercase respectively, without any other things breaking this relationship, Shift-ing for auto-Cap suffices. Not the case on CrOS.

Understood, although this will reduce confusion for the current vast majority of users in English and those familiar with the Gboard on Android.

Is there still time to triage this for M72?