I'm sure everyone has their own idiosyncratic interpretations, but I believe I've got enough experience to tell you that what I'm explaining is pretty standard.

Here are literally the top two Google results for "story points" and they both seem to align entirely with what I said:

https://www.atlassian.com/agile/project-management/estimatio...

https://www.mountaingoatsoftware.com/blog/what-are-story-poi...

I don't doubt that what you're describing as story points is something somebody told you. I'm just telling you that their definition was highly idiosyncratic and extremely non-standard. When discussing these things, using the standard definitions is helpful.

The definition of story points like the one I have mentioned has been provided by a certified scrum master and in a different context,by a certified scrum coach.

I appreciate your effort, but I don't believe there is any formal definition. It's redefined per team, it's redefined by the team too if needed.

So people want an estimate (uncertain) based on a number that's also nebulous. It kills me.

Use time ranges, you get a sense for risk AND have an estimated delivery date.

The adjustment people make with numbers can still be made on a per team basis using time ranges, I don't see why we have to use a proxy