I’ve just tested this (Big Sur 11.2.1, Scrivener 3.2.2, MacBook Air 2020, British English), and it works fine for me - ‘asked’ is always (correctly) uncapitalised after ?" and I can’t find a way of getting it to misbehave…
I do have ‘Fix Capitalisation’ (in Scrivener) and ‘Capitalise Words’ (System Preferences) both ticked, but it’s rightly not being triggered after ?" – whether I use smart quotes or not.
Have you tried it in TextEdit, which uses the same engine? If it misbehaves there, then it’s likely to be a problem with you overall settings, not with those in Scrivener.
Update: TextEdit gets it wrong for me, too — you have to turn off “Edit > Substitutions > Text Replacement” to get it to behave. But this setting doesn’t affect Scrivener, which continues to work properly either way. This suggests it’s a problem at Apple’s level.
This combination of settings works as expected in Scrivener:
[attachment=0]Screenshot 2021-02-19 at 10.28.43.png[/attachment]
It’s a bug, then … probably related to Big Sur or the m1 silicon chip. I haven’t done a lot of writing since upgrading to both, so I didn’t run into this before. I thought I’d lost my mind for a bit. If you’re on Big Sur, the problem must be the m1 chip somehow.
So it’s because you had the checkmark in system preferences.
While “asked jon” isn’t a sentence per se, the system read it as the beginning of a sentence after a punctuation mark - in this case a question-mark. Uncheck that box in system preferences and it will stop the behavior in Scrivener.
That also means you have to watch your leading words in sentences, but I always hated auto-capitalize anyway. I’m probably showing my age in how I prefer to actually use the keyboard and the buttons to do my typing instead of allowing the system to guess and suggest words.