What's your evidence or supporting research?
> things are easier to scan if the more important part is first
You skipped the step where "most important" is defined.
> "Specifier can be configured when constructing a store"
This is just about the worst type of commit message, in my opinion, only marginally better than an empty commit message.
Ok. Specifier can be configured when constructing a store. Is it supposed to? Is it the state before or after the commit? Is this just context, and maybe this commit changes documentation to reflect that reality?
You even say that reading a bunch of them is uncomfortable.
> It's not about the self. It's about the code.
Actually, it's about the change. When something broke, what changed. When a new release comes out, what changed.
Some people prefer the past form "Added feature X" instead of "Add feature X". On that I just say "be consistent".
Also note that your first batch of examples are inconsistent. "Whitespaces", "We don't use `::` to denote class methods", "Avoid __method__", past/present verb form, etc. The difference isn't just the form, but whether commits actually follow any style at all.
> I eventually recognized the benefit of scannability
Scannability is hugely important. People who disagree with your style of commit message don't disagree with you on that.
> For example, "Widget tests" is preferred over "Widget tests are added".
What about the widget tests?
> When describing a version increase, be explicit about both the old and the new version. E.g., "Package version is increased from 1.1.1 to 1.2.0"
Are version numbers ever decreased?
(1.1.2 can be released after 1.2.0, yes, but that's not a decrease even if something was backported)